Short answer: Drop the "Gmail → Create 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 |
|---|---|---|---|
To to | Optional | To. e.g. "recipient@example.com" | |
Subject subject | string | Required | Email subject line. |
Body body | html | Required | Body. e.g. "<p>Draft content...</p>" |
CC cc | string | Optional | CC. e.g. "cc@example.com" |
BCC bcc | string | Optional | BCC. e.g. "bcc@example.com" |
{"to": "recipient@example.com","subject": "e.g. Meeting follow-up","body": "<p>Draft content...</p>","cc": "cc@example.com","bcc": "bcc@example.com"}
{"id": "draft123","message": {"id": "msg123","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.