Get File/Folder Metadata: 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
Path path	string	Required	Full path starting with /

Sample request

{
  "path": "/Documents/report.pdf"
}

Returns

{
  ".tag": "file",
  "name": "report.pdf",
  "size": 1048576,
  "path_display": "/Documents/report.pdf",
  "server_modified": "2026-04-11T10:00:00Z"
}

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

FAQ

Questions about Get File/Folder Metadata.

What does the Get File/Folder Metadata action do in Dropbox?

Returns metadata for a Dropbox file or folder by path: size, last-modified, content_hash, and is_downloadable flag. Used to verify a path exists before reading.

What inputs does Get File/Folder Metadata require?

Required: 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 Get File/Folder Metadata support batch operations?

Yes. Run Get File/Folder Metadata 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