Short answer: Drop the "Resend → Resend Send Email" 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 |
|---|---|---|---|
From from | string | Required | Sender email (must be from a verified domain) |
To to | string | Required | Recipient email (comma-separated for multiple) |
Subject subject | string | Required | Subject. Example: Welcome to our platform! |
HTML Body html | string | Required | HTML content of the email |
Plain Text Body text | string | Optional | Plain text fallback |
CC cc | string | Optional | CC recipients (comma-separated) |
BCC bcc | string | Optional | BCC recipients (comma-separated) |
Reply-To reply_to | string | Optional | Reply-To. e.g. "support@company.com" |
Tag Name tags_name | string | Optional | Tag name for email analytics |
Tag Value tags_value | string | Optional | Tag Value. Example: welcome-email |
{"from": "noreply@yourcompany.com","to": "user@example.com","subject": "e.g. Welcome to our platform!","html": "{{trigger.html}}","text": "{{trigger.text}}"}
{"id": "49a3999c-0ce1-4ea6-ab68-afcd6dc2e794"}
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.