Move File or Folder: Dropbox action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Source Path from_path	string	Required	Source Path. e.g. "/Documents/file.pdf"
Destination Path to_path	string	Required	Destination Path. e.g. "/Archive/file.pdf"

Sample request

{
  "from_path": "/Documents/file.pdf",
  "to_path": "/Archive/file.pdf"
}

Returns

{
  "metadata": {
    ".tag": "file",
    "name": "file.pdf",
    "path_display": "/Archive/file.pdf"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Move File or Folder.

What does the Move File or Folder action do in Dropbox?

Moves a file or folder to a new Dropbox path. Used for organizing intake files into year/quarter folders or for stage-based document workflows.

What inputs does Move File or Folder require?

Required: Source Path, Destination Path. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Dropbox returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Move File or Folder support batch operations?

Yes. Run Move File or Folder inside a Loop node to process arrays. Tiny Command handles Dropbox's rate limits automatically so you don't have to throttle manually.

More actions