- Home
- Resources
- Integrations
- MailSlurp Email Plugin
MailSlurp Email Plugin Zapier integrationAutomate MailSlurp Email Plugin with Zapier.
MailSlurp Email Plugin Zapier integration: 4 triggers, 3 actions and 0 searches to put your MailSlurp test inboxes to work. Catch a received email, a file or a fresh inbox, then create inboxes and contacts or send a message from one.
Verified Trustpilot reviews · AI, automation & growth agency
What the MailSlurp Email Plugin Zapier integration does for you
It plugs MailSlurp, a service that gives you disposable email addresses for testing, into Zapier. What happens in those test inboxes (a message arrives, a file comes in, a new address appears) can then start an automation on its own, and Zapier can create inboxes or send emails without you opening MailSlurp.
A running log of test emails. New Email picks up each message that lands in a MailSlurp inbox and passes it on, for example to a row in your spreadsheet, so nobody has to scroll through the inbox after a test run.
Addresses created from somewhere else. Create Inbox hands you a new address whenever another app gives the signal, and New Inbox lets a second Zap react once that address exists.
Outgoing messages without the dashboard. Send Email writes from an inbox you already own to the recipients you list, which is handy to check what a real reader would receive.
What it will not do: none of the four triggers is instant, so every one of them waits for Zapier's next check. There is no search step either, which means a Zap cannot look up an existing inbox by itself, and nothing here deletes or edits an inbox. If you are still choosing a tool, read n8n vs Zapier or Make vs Zapier before you build.
The Zapier words you need, in plain English
Eight terms come back on every line of this page. Here they are once, so the rest reads easily.
- Zap
- The automation you build on Zapier: one starting event, then one or more steps that run every time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier sits and waits for it to happen.
- Action
- What the Zap does after it starts: the step that creates, sends or moves something on your behalf.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only the ones it has not seen.
- Instant trigger
- A trigger the app reports itself, the moment the event happens, so nothing waits for the next check. MailSlurp has none.
- Filter
- A step that lets the Zap carry on only when the incoming item meets a condition you set, and stops it otherwise.
- Connection
- Your MailSlurp account linked to Zapier once, then offered again in every step that uses MailSlurp.
What a MailSlurp Zap really costs
The trigger never costs anything, however often Zapier checks the inbox. You pay in tasks, and only for actions that succeed.
- Trigger checksFree, never a task
- Each successful action1 task
- Free plan100 tasks a month, Zaps of two steps
- Premium appNo, works on the free plan
A Zap that creates a contact and then sends an email burns two tasks per run; an action that fails is not counted. MailSlurp is not a premium app, so the free plan is enough to start, as long as the Zap stays at two steps. A filter or a second action makes it multi-step, and that needs a paid plan. All four triggers are polling, so the interval below applies to each of them, and a paid plan shortens the wait.
Connect your MailSlurp account in three steps
- 01
Open Apps and start a connection
In your Zapier account, go to the Apps page and click + Add connection. In the dialog, type MailSlurp Email Plugin in the search box and pick it from the results.
- 02
Sign in to MailSlurp
Click Add connection. A new tab opens on MailSlurp: sign in with the account that holds the inboxes your Zaps will read from or send with. You need that MailSlurp account before this step.
- 03
Grant access and reuse it
Allow Zapier to reach the account. From now on the connection shows up in every MailSlurp step. If the Zap touches inboxes you do not own, the account needs read or write rights on them.
Your first Zap: log every test email in a spreadsheet
GoalEach email that reaches a MailSlurp test inbox and passes your condition becomes a new row in your spreadsheet.
- 01
Create the Zap and pick the trigger
In the editor, choose MailSlurp Email Plugin, then New Email as the event that starts the Zap, and select the connection you just made.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent emails of the connected account; pick one, and it becomes the sample every later field is mapped from.
- 03
Add a filter
Click the plus icon, add Filter, then fill its three boxes: the field to look at, the rule, the value. Pick a text rule for a text field, or the filter never lets anything through.
- 04
Add the spreadsheet step
Add your spreadsheet app and its add-a-row action, then map the parts of the sample email into the columns you want to keep.
- 05
Test and publish
Run each step once and read what came back, then click Publish. The filter makes this a multi-step Zap, so it needs a paid plan to stay on.
MailSlurp triggers: what can start a Zap
4 events start a Zap when something happens in MailSlurp Email Plugin. Zapier checks for them at the interval your plan allows.
New Attachment
Polling triggerIn Zapier“Triggers when a new email attachment is received.”
Each time a file comes in attached to an email on your MailSlurp account, this trigger hands that file to the rest of the Zap, so it can be stored or passed along without anyone opening the inbox.
New Contact
Polling triggerIn Zapier“Triggers when a new contact is send in received emails.”
Zapier only describes this one as a new contact spotted in received emails, without saying what it carries. When it sees one, whatever MailSlurp returns for it moves on to the next step.
New Email
Polling triggerIn Zapier“Triggers when a new email is received.”
The trigger Zapier puts forward for this app. A message lands. Whatever the sample shows for it, from one of your MailSlurp inboxes, then feeds every step that follows.
New Inbox
Polling triggerIn Zapier“Triggers when a new inbox is created.”
Fires on a fresh address: as soon as Zapier spots a newly created inbox on your account, the Zap starts with that inbox and its details in hand.
MailSlurp actions: what a Zap can do there
MailSlurp Email Plugin gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Contact
ActionIn Zapier“Create a new email address”
Adds a contact to your MailSlurp account from an email address that an earlier step provides, such as the sender of a received message.
Send Email
ActionIn Zapier“Send a new email from a MailSlurp inbox. Create an inbox first if one does not exist.”
Sends a message from one of your MailSlurp inboxes to the recipients you list, with the content mapped from earlier steps.
Create Inbox
ActionIn Zapier“Create a new email address”
Opens a brand-new MailSlurp address each time the Zap runs. Zapier lists it among the featured actions of the app, and the address it returns can feed the steps after it.
When a MailSlurp Zap breaks
Zapier ties no help article to this app, so the traps below are the ones every Zap shares, applied to MailSlurp.
Most of them come from the trigger side: what it sees, what it skips, and what happens when the Zap writes into the inbox it is watching.
Emails from before the Zap are ignored
A Zap reacts only to what happens after it is switched on. Messages and files already in the inbox are never picked up; moving them is a separate job.The Zap that triggers itself
Send Email aimed at an inbox that New Email watches, or Create Inbox inside a New Inbox Zap, restarts the Zap on every run and burns through tasks fast.A sudden flood held back
When a trigger suddenly returns a huge batch, after a bulk import for example, Zapier's flood protection can hold the runs back instead of firing them all.The same email never fires twice
Zapier remembers what it has already seen on a polling trigger. Resending an identical test does not restart the Zap for an item it already processed.
Need help automating MailSlurp Email Plugin with Zapier?
A person reads every message.



