Search Files: 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
Search Query query	string	Required	Search Query. Example: quarterly report
Search Path path	string	Optional	Narrow search to a specific folder (optional)

Sample request

{
  "query": "e.g. quarterly report",
  "path": "/Documents"
}

Returns

{
  "matches": [
    {
      "metadata": {
        "metadata": {
          ".tag": "file",
          "name": "Q1 Report.pdf",
          "path_display": "/Documents/Q1 Report.pdf"
        }
      }
    }
  ],
  "has_more": false
}

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

FAQ

Questions about Search Files.

What does the Search Files action do in Dropbox?

Searches Dropbox files and folders by name or content (Dropbox indexes the text in many file types). Scope with a path prefix to narrow the search.

What inputs does Search Files require?

Required: Search Query. 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 Search Files support batch operations?

Yes. Run Search Files 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