Mailgun Make integrationAutomate Mailgun with Make.
Your Mailgun events can drive the rest of your stack. The Mailgun Make integration gives you 16 modules, including 7 instant triggers on clicks, opens, bounces and complaints. This guide connects your account and walks you through a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Mailgun Make integration do for you?
The Mailgun Make integration links your Mailgun account to Make, a visual tool where you build a scenario (an automation made of modules, one brick per step) without code. Mailgun tells Make when a message is delivered, opened, clicked or rejected, and Make can send email, manage mailing lists and check addresses in return.
A cleaner list after every hard bounce. New Event: Permanent Failure fires when an address rejects a message for good, and Delete a Mailing List Member takes it off the list so the next campaign skips it.
A follow-up for people who clicked. A SaaS team can pair New Event: Clicks with Add a Mailing List Member to build a list of engaged readers, then reach them later with Send an Email.
Fewer bad addresses at the door. Run Validate an Email Address on each sign-up before it lands in a list, and only add the ones that pass.
What the listed modules do not cover (other parts of the Mailgun API) goes through Make an API Call, with the same connection. The documentation gives no numeric limit for this app. Mailgun also has an n8n node: see the Mailgun n8n integration and the n8n vs Make comparison. New to the editor? The Make training starts from zero.
How do you connect Mailgun to Make?
- 01
Copy your private key
Log in to Mailgun, open Settings then API Security, and reveal the Private API Key. Copy it: this key is what lets Make act on your account.
- 02
Open the connection window
In Make, add any Mailgun module to a scenario and click Create a connection. A connection is your Mailgun account linked to Make once, then reused by every Mailgun module.
- 03
Paste the key and save
Paste the key into the API Key field and save. Before that, click Show advanced settings and check the Base URL: it has to be the right one for your Mailgun account.
Your first scenario: drop hard bounces from a list
GoalWhen Mailgun reports a permanent failure, Make removes that address from your mailing list.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the big +. That empty canvas is where each module will sit, one after the other.
- 02
Add the trigger
Search for Mailgun, pick New Event: Permanent Failure, and choose your connection or click Create a connection. This instant trigger waits for Mailgun to call Make.
- 03
Add the removal step
Click the + on the right of the trigger and pick Delete a Mailing List Member. Select the list from the menu Make fills in, then map the address from the trigger's data.
- 04
Test with Run once
Click Run once. Make runs the scenario one time and shows the bundles each module received, a bundle being one item passed along, here one failed delivery.
- 05
Switch it on
Happy with the result? Turn the scenario on. From then on, every permanent failure Mailgun reports goes through the same two modules without anyone opening the dashboard.
Mailgun triggers in Make
7 modules start a scenario when something happens in Mailgun. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Mailgun as soon as it happens.
New Event: Clicks
Instant triggerIn Make“Triggers when the 'Clicks' event occurred.”
This trigger hands your scenario every click a recipient makes on a link in your Mailgun email, so interest turns into an action somewhere else the moment it shows.
New Event: Delivery Messages
Instant triggerIn Make“Triggers when the 'Delivery Messages' event occurred.”
You get confirmation, message by message, that Mailgun handed your email to the recipient's server, which is the proof an ops team usually wants logged next to an order or a ticket.
New Event: Opens
Instant triggerIn Make“Triggers when the 'Opens' event occurred.”
Here your scenario learns that someone opened one of your messages, which lets you react to attention instead of sending blind follow-ups to everyone on the list.
New Event: Permanent Failure
Instant triggerIn Make“Triggers when the 'Permanent Failure' event occurred.”
Your scenario hears about every address that rejected a message for good, which is the cue to stop sending to it and protect the rest of your list.
New Event: Spam Complaints
Instant triggerIn Make“Triggers when the 'Spam Complaints' event occurred.”
When a recipient flags your email as spam, this trigger passes the complaint to your scenario so the address can leave every list before the next send.
New Event: Temporary Failure
Instant triggerIn Make“Triggers when the 'Temporary Failure' event occurred.”
This trigger tells your scenario that a message could not get through this time, without the address being dead, so you can keep an eye on it instead of dropping it.
New Event: Unsubscribed
Instant triggerIn Make“Triggers when the 'Unsubscribe' event occurred.”
Every unsubscribe from a Mailgun email lands in your scenario, which keeps your other tools in line with the choice the person just made.
Mailgun modules in Make
Mailgun gives you 9 modules in 4 groups. For each one: what it does for you, when to reach for it, and what to watch out for.
Send an Email
ActionIn Make“Sends an email to specified email addresses or to all mailing list members.”
Send an Email lets any scenario send a message through Mailgun, either to addresses you map or to every member of a mailing list, so a new order or a form entry can trigger its own email.
Mailing Lists
4 modulesAdd a Mailing List Member
ActionIn Make“Adds or updates an email address in a selected mailing list.”
This module puts an address into the mailing list you choose, and updates it if it is already there, so the same contact coming back twice does not create a duplicate.
Delete a Mailing List Member
ActionIn Make“Removes an email address from a selected mailing list.”
Delete a Mailing List Member takes an address off a selected list, which is how bounces, complaints or a churned customer stop receiving the wrong emails.
Get a Mailing List Member
ActionIn Make“Retrieves a mailing list member.”
You get back one member of a list, which lets the scenario check an address before deciding what to do next, instead of acting on guesswork.
List Mailing List Members
SearchIn Make“Paginate over list members in the given mailing list.”
This search walks through the members of a list and returns each one as a separate bundle, which is the starting point for syncing or auditing a list from Make.
Other
3 modulesList Domains
SearchIn Make“Returns a list of domains.”
List Domains returns the sending domains of your Mailgun account, handy when the scenario has to know which domain to use or to report on them.
Validate an Email Address
ActionIn Make“Validate the given address based on mailbox detection, syntax checks, DNS validation, spell checks etc.”
Before an address enters your lists, this module checks it: syntax, spelling, the domain's DNS and whether a mailbox seems to exist behind it. You keep typos and dead addresses out from the start.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
When none of the listed modules does what you need, Make an API Call reaches any endpoint of the Mailgun API from your scenario, with the connection you already set up.
Other modules
1 moduleCreate a Route
ActionIn Make“Creates a new route.”
Create a Route adds a new route to your Mailgun account straight from a scenario, so that setup follows an event in another tool instead of a trip to the dashboard.
Need help automating Mailgun with Make?
A person reads every message.
