Search Files: Google Drive 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	Optional	Search by file name
Limit limit	number	Optional	Maximum results (max 50)

Sample request

{
  "query": "{{trigger.query}}",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "files": [
    {
      "id": "1abc",
      "name": "My Document",
      "mimeType": "application/vnd.google-apps.document",
      "modifiedTime": "2026-04-19T10:00:00Z"
    }
  ]
}

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 Google Drive?

Searches files and folders in Google Drive by name (uses a contains-match on the name field). For advanced queries, use List Files with a custom Drive q parameter.

What inputs does Search Files require?

Search Files has no required inputs. Sensible defaults are applied if you leave fields blank.

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 Google Drive 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 Google Drive's rate limits automatically so you don't have to throttle manually.

More actions