Short answer: Drop the "Mailgun → Mailgun 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: Your order is confirmed |
HTML Body html | string | Required | HTML Body |
Plain Text Body text | string | Optional | Plain Text Body |
CC cc | string | Optional | CC. e.g. "cc@example.com" |
BCC bcc | string | Optional | BCC. e.g. "bcc@example.com" |
Tags tags | string | Optional | Comma-separated tags for tracking |
Reply-To reply_to | string | Optional | Reply-To. e.g. "support@yourdomain.com" |
{"from": "noreply@yourdomain.com","to": "user@example.com","subject": "e.g. Your order is confirmed","html": "{{trigger.html}}","text": "{{trigger.text}}"}
{"id": "<20250115120000.abc123@yourdomain.com>","message": "Queued. Thank you."}
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.