Delete Folder
dropbox.delete_folder
ActionFiles & storageconnection required
Calls the Dropbox API with the connection's credentials.
Move a folder and everything inside it to the Dropbox trash.
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 |
|---|---|---|---|---|---|
path The folder to delete, as an absolute path. | string | Yes | — | — | /Reports/2026 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"path": "/Reports/2026"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
metadata.id The Dropbox id of the file or folder. | string | id:a4ayc_80_OEAAAAA |
metadata.name The last component of the path, including any extension. | string | — |
metadata.path_display The full path, cased for display. | string | — |
metadata.path_lower The full path, lowercased — what Dropbox matches on. | string | — |
metadata.size File size in bytes. Files only. | number | — |
metadata.rev The revision id of the current content. Files only. | string | — |
metadata.content_hash Dropbox's content hash, for integrity checks. Files only. | string | — |
metadata.client_modified When the client says the file changed (RFC 3339). | string | — |
metadata.server_modified When Dropbox stored the change (RFC 3339). | string | — |
{
"metadata": {
"client_modified": "",
"content_hash": "",
"id": "id:a4ayc_80_OEAAAAA",
"name": "",
"path_display": "",
"path_lower": "",
"rev": "",
"server_modified": "",
"size": 0
}
}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.
- Dropbox deletes a file and a folder through the same files/delete_v2 call; this node exists so the graph says which one you meant. Everything inside the folder goes with it.
See Delete Folder 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.