Short answer: Drop the "Google Drive → Copy 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 |
|---|---|---|---|
Source File ID file_id | string | Required | The unique identifier of the file to copy |
New File Name name | string | Optional | Name for the copied file (defaults to 'Copy of [original name]') |
Destination Folder ID parent_id | string | Optional | ID of the folder to copy the file into. Leave empty for same location. |
{"file_id": "e.g. 1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms","name": "e.g. Q1 Report - Copy","parent_id": "e.g. folder456abc"}
{"id": "file789copy","name": "Q1 Report - Copy","parents": ["folder456abc"],"mimeType": "application/vnd.google-apps.spreadsheet","createdTime": "2025-01-18T16:00:00.000Z","webViewLink": "https://docs.google.com/spreadsheets/d/file789copy/edit"}
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.