ActionMailgunUpdated June 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.

Mailgun Send Email in Mailgun — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
From
from
stringRequiredSender email (must be from a verified domain)
To
to
stringRequiredRecipient email (comma-separated for multiple)
Subject
subject
stringRequiredSubject. Example: Your order is confirmed
HTML Body
html
stringRequiredHTML Body
Plain Text Body
text
stringOptionalPlain Text Body
CC
cc
stringOptionalCC. e.g. "cc@example.com"
BCC
bcc
stringOptionalBCC. e.g. "bcc@example.com"
Tags
tags
stringOptionalComma-separated tags for tracking
Reply-To
reply_to
stringOptionalReply-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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Mailgun Send Email support batch operations?
Yes. Run Mailgun Send Email inside a Loop node to process arrays. TinyCommand handles Mailgun's rate limits automatically so you don't have to throttle manually.
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.
Action
Mailgun Validate Email
SMTP-handshake + DNS + Mailgun-heuristic validation. Returns deliverable/undeliverable/risky/unknown. Useful for in-flow validation before adding to sequences.
Mailgun Send Email in Mailgun — start free