Dropbox

The Dropbox node lets you manage files and folders in Dropbox. A single node supports multiple operations — select the operation you need and the relevant fields appear.

All operations require a Dropbox connection configured with your access token.

Operations

List Folder

List files and folders in a Dropbox directory.

Field	Description	Notes
Path	Folder path (e.g., /Documents)	Empty string for root
Limit	Maximum results (1–2000)	Default: 100

Get Metadata

Get metadata for a file or folder.

Field	Description	Notes
Path	File or folder path	Required. Supports templates

Read File

Read a file from Dropbox with optional CSV/JSON/JSONL/TSV/XML parsing.

Field	Description	Notes
Path	File path to read	Required. Supports templates
Parse Format	How to parse the body	raw (default), json, jsonl, csv, tsv, or xml

Returns {path, name, size, content_type, modified_at, parse_format, content} where content is the parsed value (string for raw; map/array for parsed formats).

Write File

Write a single file to Dropbox from either upstream items or a literal content string.

Field	Description	Notes
Path	Destination path (e.g., /reports/output.csv)	Required. Supports templates
Write Mode	Overwrite or Add (auto-rename if exists)	Default: Overwrite
Source	Where the file body comes from	From upstream data (default) or Custom content
Format	How input items are serialized	Visible when Source = data. CSV, TSV, JSON (default), JSON Lines, XML, or Raw
CSV Column Order	Comma-separated columns for CSV/TSV	Visible when Format ∈ {csv, tsv}. Leave empty for union of keys
File Content	Literal body to upload	Visible when Source = content. Supports templates

The MIME Content-Type is set automatically: from Format when Source = data, or application/octet-stream when Source = content.

Source modes:

• From upstream data — serialize every input item into the file using the chosen Format. Use this when you have rows/records from a database query, API response, etc.
• Custom content — write the File Content field verbatim. Use this when you've already composed the bytes yourself.

Note: unlike older versions of this node, streaming over upstream items produces one Dropbox file (not one per item). If you need per-item file fan-out, do the loop explicitly with a sub-workflow.

Delete

Delete a file or folder.

Field	Description	Notes
Path	File or folder path to delete	Required. Supports templates

Move / Rename

Move or rename a file or folder.

Field	Description	Notes
From Path	Current path	Required. Supports templates
To Path	New path	Required. Supports templates

Create Folder

Create a new folder.

Field	Description	Notes
Path	Folder path to create	Required. Supports templates

Search Files

Search for files by name.

Field	Description	Notes
Search Query	Text to search for	Required. Supports templates
Limit	Maximum results (1–2000)	Default: 100

Streaming

List Folder and Search operations support streaming — each item is emitted individually to downstream nodes.

Common Patterns

Backup DataStore to Dropbox

1. Cron — run daily
2. DataStore Query — export table data
3. Transform — convert to CSV
4. Dropbox (Upload) — save to /backups/export.csv

Process Uploaded Files

1. Dropbox (List Folder) — list files in /inbox
2. Dropbox (Download) — download each file
3. Transform — process content
4. Dropbox (Move) — move to /processed