Short answer: Drop the "Google Drive → Create Folder" 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 |
|---|---|---|---|
Folder Name name | string | Required | Folder Name. Example: Project Documents |
Parent Folder ID parent_id | string | Optional | ID of the parent folder. Leave empty for root. |
{"name": "e.g. Project Documents","parent_id": "e.g. folder123abc"}
{"id": "folder456","name": "Project Documents","mimeType": "application/vnd.google-apps.folder","webViewLink": "https://drive.google.com/drive/folders/folder456"}
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.