Mailgun
Send transactional email with Mailgun and read events, domains, tags, suppressions and stats; manage templates, mailing lists and list members.
Send notifications from business events, keep mailing list membership aligned with CRM records and feed delivery and bounce data back to source systems.
Source actions
14
Destination actions
8
Data types
12
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
bounces
- List bouncesSource
Addresses suppressed after a bounce.
complaints
- List complaintsSource
Addresses that reported mail as spam.
domains
- Get domainSource
One domain with its sending and receiving DNS records and verification state.
- List domainsSource
Sending domains on the account with their state.
events
- List eventsSourceIncremental
Accepted, delivered, failed, opened, clicked, unsubscribed and complained events for the domain.
list members
- Get mailing list memberSource
One member with subscription status and variables.
- List mailing list membersSource
Members of one mailing list, optionally only subscribed or unsubscribed.
- Update mailing list memberDestinationDuplicate protected
Updates a member's name, variables or address. Subscription changes only when subscribed is given.
- Add or update mailing list memberDestinationDuplicate protected
Adds a member or updates an existing one (upsert=yes). The subscribed value must be given explicitly.
mailing lists
- Create mailing listDestinationDuplicate protected
Creates a mailing list with a unique list address.
- Get mailing listSource
One mailing list.
- List mailing listsSource
Mailing lists on the account with member counts.
- Update mailing listDestinationDuplicate protected
Changes a list's name, description, access level, reply preference or address.
messages
- Send emailDestinationNot retried automatically
Sends one transactional email (up to 50 recipients) from the configured domain, with raw content or a stored template.
stats
- Get domain statisticsSource
Totals for one event type over a period, by hour, day or month.
tags
- List tagsSource
Message tags used on the domain.
template versions
- Create template versionDestinationDuplicate protected
Adds a new version to a template and optionally makes it active.
templates
- Create templateDestinationDuplicate protected
Creates a template, optionally with its first version content.
- Get templateSource
One template with its active version content.
- List templatesSource
Stored templates on the domain.
- Update template descriptionDestinationDuplicate protected
Changes a template's description.
unsubscribes
- List unsubscribesSource
Addresses that unsubscribed from the domain, all mail or specific tags (consent withdrawn).
Authentication
Private API key
Plans and access
All Mailgun plans. Free and trial accounts can only send to authorised recipients on the sandbox domain. Domain sending keys can only send; use a primary account API key (or a key with the needed role) for lists, templates, events and suppressions.
Test environment
Every account has a sandbox domain; o:testmode accepts messages without delivering them.
Rate limits
Account-level limits that depend on plan; HTTP 429 when exceeded. Events and logs are retained for at least 3 days (longer on paid plans).
Provider events
Domain webhooks for delivered, opened, clicked, unsubscribed, complained and failed events. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Mailgun marks the Events and Stats APIs as deprecated in favour of the Logs and Metrics APIs; they still operate and are used here because their request and response fields are fully documented.
- Messages are limited to 50 recipients in Nexra, and sending to a mailing list address is refused, so this operation cannot broadcast to audiences.
- Sends have no idempotency key; uncertain sends are not repeated automatically.
- Mailing list member upserts require an explicit subscribed value so Nexra never changes consent implicitly.
- Suppression changes, bulk member uploads, attachments, template version edits and all deletes are not implemented.