Short answer: Drop the "Google Drive → Share 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 share |
Share With type | options | Required | Who to share the file with |
Permission role | options | Required | Level of access to grant |
Email Address emailAddress | string | Optional | Email address of the user or group (required for user/group type) |
Domain domain | string | Optional | Domain to share with (required for domain type) |
Send Notification sendNotificationEmail | options | Optional | Send an email notification to the user |
Email Message emailMessage | string | Optional | Custom message to include in the notification email |
{"file_id": "e.g. 1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms","type": "{{trigger.type}}","role": "{{trigger.role}}","emailAddress": "e.g. john@example.com","domain": "e.g. example.com"}
{"id": "perm123","role": "writer","type": "user","displayName": "John Doe","emailAddress": "john@example.com"}
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.