Short answer: Drop the "Google Drive → Move File" 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 |
|---|---|---|---|
File ID file_id | string | Required | The unique identifier of the file or folder to move |
Destination Folder ID new_parent_id | string | Required | ID of the folder to move the file into |
Current Parent Folder ID old_parent_id | string | Required | ID of the current parent folder to remove from |
{"file_id": "e.g. 1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms","new_parent_id": "e.g. folder456abc","old_parent_id": "e.g. folder123abc"}
{"id": "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms","name": "Q1 Sales Report.pdf","parents": ["folder456abc"],"mimeType": "application/pdf","webViewLink": "https://drive.google.com/file/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms/view"}
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.