Short answer: Drop the "Gmail → Get Draft" 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 |
|---|---|---|---|
Draft ID draftId | string | Required | Gmail draft ID. Find via List Drafts. |
Format format | options | Optional | Format. Options: Full (headers + body), Metadata (headers only), Minimal (IDs only), Raw (base64 encoded) |
{"draftId": "e.g. r1234567890","format": "{{trigger.format}}"}
{"id": "r1234567890","message": {"id": "msg123","payload": {"headers": [{"name": "To","value": "recipient@example.com"},{"name": "Subject","value": "Follow-up"}]},"snippet": "Hi, just following up on...","labelIds": ["DRAFT"],"threadId": "thread123"}}
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.