Check Move Batch
dropbox.move_batch_check
ActionFiles & storageconnection required
Calls the Dropbox API with the connection's credentials.
Check whether a move batch has finished and read its per-entry results.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Dropbox
- Secret shape
- the Dropbox access token
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
async_job_id The job id dropbox.move_batch returned. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
entries One result per submitted move, once the job is complete. | array | — |
{
"entries": []
}Notes
- Paths are absolute and start with a slash ('/Reports/2026/q1.csv'); the account root is the empty string. A Dropbox file id ('id:…') or revision ('rev:…') may be used anywhere a path is asked for.
- Uploads and downloads use content.dropboxapi.com and everything else uses api.dropboxapi.com; the nodes pick the right host for you.
- The connection's access token must carry the scope the call needs — files.content.write to upload, move, delete or restore, files.content.read to download, files.metadata.read to list, search or read metadata, sharing.read to list shared links, sharing.write to create or revoke one, and account_info.read for space usage.
- While the job is still running Dropbox answers {".tag": "in_progress"} with no entries; poll again with a control.delay in between.
See Check Move Batch run in a workflow.
In a technical demo we add the Dropbox connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.