Short answer: Drop the "Google Drive → List Files" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Search Query q | string | Optional | Drive search query (e.g. name contains 'report' and mimeType='application/pdf') |
Page Size pageSize | string | Optional | Page Size. e.g. "20" |
Order By orderBy | string | Optional | Order By. Example: modifiedTime desc |
Fields fields | string | Optional | Fields to include in response |
{"q": "e.g. name contains 'report'","pageSize": "20","orderBy": "e.g. modifiedTime desc","fields": "files(id,name,mimeType,webViewLink,modifiedTime)"}
{"files": [{"id": "file123","name": "Q1 Report.pdf","mimeType": "application/pdf","webViewLink": "https://drive.google.com/file/d/file123/view","modifiedTime": "2025-01-15T12:00:00.000Z"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.