Resources · Zapier integration

Mailtrap Zapier integrationAutomate Mailtrap with Zapier.

The Mailtrap Zapier integration lets other apps send email and keep contacts in sync. Zapier lists 0 triggers, 5 actions and 0 searches for Mailtrap, so an event in another tool starts each Zap and Mailtrap carries out the work.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Mailtrap Zapier integration does for you

Zapier links apps without code. For Mailtrap, it is a one-way street: something happens in another tool, and Zapier asks Mailtrap to send an email or to add, change or remove a contact. Mailtrap never starts a Zap, because Zapier exposes no event coming out of it.

Three outcomes worth building. A clean contact base: every signup on your product form becomes a Mailtrap contact through Create Contact, with no CSV export to do by hand. A welcome email that leaves on its own: the same signup fires Send Email with your HTML, from a sender on your own domain. Unsubscribes that stick: when a customer opts out in your billing or support tool, Update Contact flips their subscription status in Mailtrap.

Now the limits. Zapier cannot watch Mailtrap: no new contact, no opened email, no bounce can start a Zap here. There is no search step either, so a Zap cannot look up a contact before acting on it. And every contact action needs your Mailtrap Account ID, which you copy from the Mailtrap interface once.

For the same app on another platform, the Mailtrap Make integration lists what Make offers. If you are still choosing a sending tool, the Postmark Zapier integration covers a close neighbor.

Vocabulary

Zapier words in one minute

Seven words come back on this page. Here they are in plain English, once each.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Mailtrap offers none on Zapier, so the trigger always comes from another app.
Action
What the Zap does once started: the step that writes or sends something for you, such as creating a contact in Mailtrap.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
Polling vs instant
Zapier checks a polling trigger on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it there otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
Cost

What a Mailtrap Zap really costs

Mailtrap is not a premium app, so it runs on the free plan. Zapier bills in tasks, and only the Mailtrap steps count.

  • Free plan100 tasks per month
  • Free plan limit2 steps per Zap
  • Premium appNo
  • Contact plus welcome email2 tasks per run

The trigger in the other app is free, and so is every check Zapier makes for new data. Each Mailtrap action that succeeds is one task; one that fails is not counted. The free plan gives you 100 tasks a month and two-step Zaps only. That matters here: creating the contact and sending the welcome email are two actions, so that Zap is multi-step, needs a paid plan, and costs two tasks per signup. Plan for that before you wire a busy form.

Connect

Connect Mailtrap to Zapier in 3 steps

  1. 01

    Start from the Apps page

    In your Zapier account, open Apps and click + Add connection. In the dialog, search for Mailtrap and pick it from the results that appear. Check the name before you confirm.

  2. 02

    Sign in to Mailtrap

    Click Add connection. A new tab opens on Mailtrap: sign in with the account that owns the sending domain and the contacts you want the Zap to handle.

  3. 03

    Grant access

    Approve the access Zapier requests. The connection is saved under Apps, and every Mailtrap step in every Zap reuses it, so you only do this once per account.

First Zap

Your first Mailtrap Zap: product signups into your contacts

GoalTurn every new signup on your product form into a Mailtrap contact.

  1. 01

    Pick the trigger

    Create a Zap and choose your signup form as the starting app, with its new submission event. Test it: Zapier pulls the three most recent submissions so you map a real one.

  2. 02

    Add a filter

    Click the plus icon, choose Filter, then set the field (email), the rule and the value. Empty or test submissions stop here. This makes the Zap multi-step.

  3. 03

    Add Create Contact

    Pick Mailtrap as the action app and the Create Contact event. Paste your Account ID, then map the email field coming from the form step.

  4. 04

    Test the action

    Run the test once and check that the contact shows up in Mailtrap. If the step fails, the Account ID and the email mapping are the first two things to check.

  5. 05

    Publish

    Click Publish to switch the Zap on. From now on, each new signup becomes a contact. Signups from before that click are not picked up.

Actions

Mailtrap actions on Zapier

Mailtrap gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Contact

Action

In Zapier“Creates a new contact”

Adds a new contact to your Mailtrap account from an email address that another app hands over. You map the address, add your Account ID, and the contact exists.

When to use it
every trial signup on your SaaS should land in Mailtrap before the onboarding sequence starts.
Watch out
the Account ID field is required, and it comes from the Mailtrap interface, not from Zapier.
2

Delete Contact

Action

In Zapier“Allows you do delete Contact by his email”

Removes a contact from Mailtrap, targeted by its email address. Handy to keep the base aligned with what your other tools consider gone.

When to use it
a customer asks for account deletion in your helpdesk and the contact must disappear from Mailtrap as well.
Watch out
the email you map decides who goes, so test with a dummy contact before publishing.
3

Get Lists

Action

In Zapier“Allows you to get the list of your Lists and their IDs”

Returns the lists of your Mailtrap account with their IDs, so a later step can use a list ID without you copying it by hand. It needs only your Account ID.

When to use it
you are building a Zap and need to see which list IDs exist before wiring them in.
Watch out
it counts as an action, so each run costs a task.
4

Send Email

Action

In Zapier“Sends an email via Mailtrap”

Sends one email through Mailtrap, with a sender, a recipient, a subject and an HTML body you build from earlier steps. It is the step that turns an event into a message in an inbox.

When to use it
a receipt or a welcome note that should leave as soon as an order or signup happens.
Watch out
the sender address must sit on a domain tied to your Mailtrap account.
5

Update Contact

Action

In Zapier“Allows you to update Contact in Mailtrap”

Changes an existing contact, found by its email address. Its most useful switch is the Unsubscribed setting, which turns the contact's subscription status on or off.

When to use it
a customer opts out from your billing portal and you want Mailtrap to stop mailing them too.
Watch out
this step also asks for the Account ID, so keep it handy.
When it breaks

When a Mailtrap Zap breaks

Zapier attaches no help article to Mailtrap and documents no rate limit specific to it. Failures come from required fields and from rules that apply to every Zap.

Most of them show up on the first test. These are the ones to rule out before you publish; the Zapier troubleshooting page covers broader cases.

  • Missing or wrong Account ID

    Four of the five actions require the Account ID. A blank or mistyped value stops the step, and the contact never gets created, changed or removed.

  • Sender on the wrong domain

    Send Email expects a From address on a domain associated with your Mailtrap account. Any other sender address is the first thing to check when sending fails.

  • Nothing from before publishing

    A Zap only reacts to what happens after it is switched on. Signups that existed before are never sent to Mailtrap; importing them is a separate job.

  • Flood after a bulk import

    If the starting app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold it back instead of running every item.
Need help

Need help automating Mailtrap with Zapier?

A person reads every message.

FAQ

Mailtrap Zapier integration: common questions

01Is the Mailtrap Zapier integration free?
Yes. Mailtrap is not a premium app, so it works on Zapier's free plan. That plan gives 100 tasks a month and Zaps of two steps: a trigger from another app and one Mailtrap action. Creating a contact and then sending an email is two actions, which makes the Zap multi-step and requires a paid plan. A single action, such as creating the contact alone, stays within the free plan, and you can run as many of those Zaps as you like.
02How many tasks does Mailtrap use on Zapier?
One task per Mailtrap action that succeeds. The trigger in the other app costs nothing, and so do Zapier's checks for new data. A Zap that creates a contact and sends a welcome email burns two tasks per signup. A step that fails, for instance because the Account ID is wrong, is not counted. Get Lists is an action too, so it also costs a task each time it runs. On the free plan, 100 tasks a month is the budget to divide across all these Zaps.
03Is Mailtrap on Zapier real time?
That depends on the app that starts the Zap, since Mailtrap has no trigger. If that app offers an instant trigger, it reports the event to Zapier straight away and the Mailtrap action runs right after, whatever your plan. If it relies on a polling trigger, Zapier checks on a timer: every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. A lightning bolt in the editor marks a Zap built on an instant trigger.
04What does it take to connect Mailtrap?
A Mailtrap account that you sign in to from Zapier, plus access to the contacts and domain you want the Zap to use. You open Apps, click + Add connection, pick Mailtrap and grant access. Then keep your Account ID nearby: Create Contact, Update Contact, Delete Contact and Get Lists all require it. For Send Email, the sender address has to belong to a domain associated with your Mailtrap account. One connection then serves every Zap you build.
05Where is the Mailtrap Account ID for Zapier?
In the Mailtrap interface, not in Zapier. The field help for every contact action says the Account ID is found in the Mailtrap UI, so you copy it once and paste it into each step that asks for it. Without it, contact steps cannot run. If a test fails on Create Contact or Update Contact, check this value before anything else, then the email mapping from the trigger step. Store it somewhere your team can find it.
06What if the Mailtrap operation you need is not available?
Then Zapier does not offer it for Mailtrap today. The five visible operations are Create Contact, Update Contact, Delete Contact, Send Email and Get Lists. There is no trigger and no search, so a Zap cannot react to a Mailtrap event or look up a contact first. Check the Make page for Mailtrap before you design a workaround, since another platform may list operations Zapier does not. Plan around the five that exist.
07Zapier, Make or n8n for Mailtrap?
Pick on the criterion that matters for your case. Zapier gives five Mailtrap actions and runs a single-action Zap on the free plan, which suits pushing contacts and emails from many apps. If you need to start from Mailtrap events, or to chain many steps, where per-action billing adds up, compare what Make offers for the same app. Pricing model, hosting and how many steps the job needs all shift the answer. No tool wins every criterion.
Same platform

Other docs you might need on this stack.

Browse all integrations