Delete Batch
dropbox.delete_batch
ActionFiles & storageconnection required
Calls the Dropbox API with the connection's credentials.
Delete many files or folders in one call, which Dropbox may finish immediately or run as a background job.
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 |
|---|---|---|---|---|---|
entries The absolute paths to delete, one per entry. | array | Yes | — | ≥ 1 characters; array of string | ["/Reports/2026/q1.csv","/Reports/2026/q2.csv"] |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"entries": [
"/Reports/2026/q1.csv",
"/Reports/2026/q2.csv"
]
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
async_job_id Set when Dropbox ran the batch in the background — poll it with the matching check node. | string | — |
entries Set instead when Dropbox finished the batch synchronously: one result per submitted entry, in the order they were sent. | array | — |
{
"async_job_id": "",
"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.
- The answer is either an 'async_job_id' to poll with dropbox.delete_batch_check, or 'entries' when Dropbox finished the batch there and then — handle both.
See Delete 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.