ActionMailgunUpdated September 2026
How do I send email via Mailgun?
Short answer: You can mailgun send email in Mailgun by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Mailgun Mailgun Send Email action to a workflow, map its 9 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
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" |
Sample request
{"from": "noreply@yourdomain.com","to": "user@example.com","subject": "e.g. Your order is confirmed","html": "{{trigger.html}}","text": "{{trigger.text}}"}
Returns
{"id": "<20250115120000.abc123@yourdomain.com>","message": "Queued. Thank you."}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Mailgun Send Email.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Mailgun Send Email.
What does the Mailgun Send Email action do in Mailgun?
Sends transactional or bulk email with HTML/text body, attachments, per-recipient variables for batched personalised sends. The standard hook for "external event → transactional email" patterns.
What inputs does Mailgun Send Email require?
Required: From, To, Subject, HTML Body. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Mailgun returns an error?
The run history shows the failed step with its input and the error message Mailgun returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Mailgun Send Email support batch operations?
Run Mailgun Send Email inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Mailgun's rate limits.
More actions
Other Mailgun actions.
Action
Get Mailgun Events
Paginated event log (delivered, opened, clicked, bounced, failed, complained) with filters by date, message-id, recipient. For "did this email actually deliver?" forensics or bulk-export to warehouse.
ActionMailgun Validate Email
SMTP-handshake + DNS + Mailgun-heuristic validation. Returns deliverable/undeliverable/risky/unknown. Useful for in-flow validation before adding to sequences.