Email delivery service for sending, receiving, and tracking emails
Mailgun currently provides 7 triggers that can start a workflow and 7 actions a workflow can run. Use those building blocks to connect campaign activity to the records and follow-up it should influence.
New Bounce Event
Triggers when an email permanently fails to deliver (hard bounce) in Mailgun
New Complaint Event
Triggers when a recipient reports an email as spam in Mailgun
New Delivery Event
Triggers when an email is successfully delivered in Mailgun
New Failed Delivery Event
Triggers when an email temporarily fails to deliver in Mailgun (will be retried)
New Open Event
Triggers when a recipient opens an email in Mailgun
New Click Event
Triggers when a recipient clicks a tracked link in an email in Mailgun
New Unsubscribe Event
Triggers when a recipient unsubscribes from emails in Mailgun
Send Email
Send an email using your Mailgun domain
Validate Email
Validate an email address using Mailgun validation service. Requires a Mailgun account with email validation enabled.
Add Mailing List Member
Add a new member to a Mailgun mailing list
Get Events
Retrieve email events from your Mailgun domain (deliveries, failures, opens, clicks, etc.). Useful for monitoring and alerting.
Get Domain Stats
Retrieve aggregated email statistics for a Mailgun domain (delivered, failed, opened, etc.). Useful for monitoring delivery health and detecting anomalies.
List Bounces
Retrieve the list of bounced email addresses for a Mailgun domain. Useful for cleanup after delivery issues or spam attacks.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Mailgun event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Bounce Event
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Mailgun action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Send Email
Combine Mailgun with another integration and Coherence records to connect campaign activity to the records and follow-up it should influence.
Starts with
New Bounce Event
Finishes with
Send Email, then preserve the outcome in Coherence
The exact authentication fields depend on Mailgun. The workflow structure stays straightforward:
Authorize the Mailgun account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Mailgun or provide a complementary trigger or action.
Mailgun currently provides 7 triggers that can start a workflow and 7 actions a workflow can run. Use those building blocks to connect campaign activity to the records and follow-up it should influence.
Mailgun currently lists 7 triggers and 7 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Mailgun triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
