Resources · Make integration

Mailtrap Make integrationAutomate Mailtrap with Make.

Can Make keep your Mailtrap contacts and emails in step with the rest of your stack? The Mailtrap Make integration gives you 6 modules: 5 actions and 1 search. This guide shows how to link your API token, build a first scenario and pick the right module.

Try the Mailtrap integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Mailtrap Make integration do for you?

The Mailtrap Make integration links your Mailtrap account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single step such as creating a contact or sending an email. Mailtrap has no trigger in Make, so another app or a schedule starts the flow, and Mailtrap does the work.

A contact list that fills itself. A SaaS team collects signups in a form tool. Each new entry goes through Create a Contact, and nobody copies addresses by hand again.

A welcome email that leaves on its own. Right after that contact exists, Send an Email sends the first message. The same pair works for an order confirmation from a shop app.

Clean lists when people leave. When a customer closes an account elsewhere, Update a Contact or Delete a Contact keeps Mailtrap in line, and Get Lists gives you the list IDs you need along the way.

Mailtrap has no trigger in Make: it cannot start a scenario by itself when something happens inside Mailtrap. For anything the six modules do not cover, Make an API Call reaches the rest of the Mailtrap API with the same connection. To weigh the tool itself, read our Make review, and if you are deciding between two platforms, the n8n vs Make comparison lays out the criteria.

Connect

How do you connect Mailtrap to Make?

  1. 01

    Copy your API token in Mailtrap

    In Mailtrap, open Settings in the left menu, then API Tokens. Copy the token shown for the domain or integration you want Make to use. You need an active Mailtrap account for this.

  2. 02

    Open the connection window in Make

    In your scenario, add any Mailtrap module and click Create a connection. A connection is your Mailtrap account linked to Make once, then reused by every Mailtrap module you add later.

  3. 03

    Name it and paste the token

    The Connection name field is optional, but a clear name helps once you run several accounts. Paste the token you copied, confirm, and the module is ready to be filled in.

First scenario

Your first scenario: a new signup becomes a Mailtrap contact and gets a welcome email

GoalWhen a new signup arrives in another app, Make creates the contact in Mailtrap and sends a welcome email.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your signups land, such as your form tool, as the first module.

  2. 02

    Add Create a Contact

    Click the + to the right of that first module, search for Mailtrap and choose Create a Contact. Click Create a connection and paste your API token.

  3. 03

    Map the signup data

    Fill the module fields with the data of the previous module: the email address and name from the form go straight into the new contact. Each signup travels as one bundle, one item passed between modules.

  4. 04

    Add Send an Email

    Add Send an Email after the contact module and map the recipient from the same bundle. Write the welcome message once; Make reuses it for every new signup.

  5. 05

    Test with Run once

    Submit a test signup, then click Run once. Open the bubble of each module to read the bundles it received and check that the contact and the email look right.

  6. 06

    Schedule and switch on

    On the first module, set the Scheduling: every 15 minutes by default, 15 minutes at the shortest on the Free plan. Then switch the scenario on so it runs without you.

Modules

What each Mailtrap module does in Make

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

Mailtrap1

Create a Contact

Action

In Make“Create a contant in Mailtrap”

Adds a new person to your Mailtrap contacts from data that comes out of another app, so your audience grows without any copy and paste.

When to use it
a lead fills a form on your landing page or a customer buys for the first time, and you want that person reachable from Mailtrap right away.
Watch out
if the person may already exist, check first or route to Update a Contact instead, to avoid creating the same contact twice.
Mailtrap2

Delete a Contact

Action

In Make“Delets a contact in Mailtrap”

Removes a contact from Mailtrap, which keeps your lists honest when someone should no longer hear from you.

When to use it
a customer closes an account in your app or asks to be erased, and the removal must follow in Mailtrap without anyone thinking about it.
Watch out
treat the deletion as final. Test it with Run once on a dummy contact, and put a filter before the module so only the right bundles reach it.
Mailtrap3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call”

Opens the rest of the Mailtrap API to your scenario, with the connection you already set up, so you are not stuck when the five other modules stop short.

When to use it
you need a Mailtrap endpoint that has no dedicated module in Make, and you have the Mailtrap API documentation at hand to build the request.
Watch out
this module asks you to write the request yourself, so it suits someone at ease with an API; for everyday contact work, the ready-made modules are simpler.
Mailtrap4

Send an Email

Action

In Make“Send an email to a recipient”

Sends a message through Mailtrap to one recipient, filled with data from earlier steps, so every email leaves at the right moment with the right details.

When to use it
an order is paid, an account is created or a booking is confirmed in another app, and the person should get a message sent through Mailtrap.
Watch out
it acts on one recipient per bundle. If a search returns many people, each one triggers its own email and its own operation, the unit Make counts on your plan.
Mailtrap5

Update a Contact

Action

In Make“Update a contact in Mailtrap”

Changes the details of a contact who is already in Mailtrap, so the information your emails rely on stays current.

When to use it
a customer edits a profile in your CRM, changes a plan or moves to another segment, and Mailtrap should reflect it without a manual edit.
Watch out
the module works on an existing contact. For a person Mailtrap has never seen, Create a Contact is the one to reach for, so plan both paths when you are not sure.
Mailtrap6

Get Lists

Search

In Make“Fetch all Mailtrap contact lists with their IDs.”

Brings back all your Mailtrap contact lists along with their IDs, which saves you from hunting for the right identifier in the Mailtrap interface.

When to use it
a later module needs a list ID, or you want to review which lists exist before adding contacts to one of them.
Watch out
as a search, it can return zero, one or several bundles, one per list. Every module placed after it runs once per list unless you filter the result first.
Need help

Need help automating Mailtrap with Make?

A person reads every message.

FAQ

Mailtrap and Make: common questions

01Is the Mailtrap Make integration free?
Yes, Mailtrap is a standard app in Make, so you can use it from the Free plan. That plan allows 2 active scenarios, runs a scheduled scenario at most every 15 minutes, stops an execution after 5 minutes, and caps files at 5 MB with 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the limit on active scenarios. Your Mailtrap account and its own subscription are separate from Make, so check the Mailtrap pricing page for that side.
02What do you need to connect Mailtrap to Make?
You need an active Mailtrap account and an API token. In Mailtrap, open Settings in the left menu, click API Tokens and copy the token shown for the domain or integration you want to use. In Make, add a Mailtrap module, click Create a connection, give it a name if you like and paste the token. That single connection then serves every Mailtrap module in your scenarios, including Make an API Call.
03Can Mailtrap start a Make scenario in real time?
No, Mailtrap has no trigger module in Make, so it cannot start a scenario on its own. The flow begins elsewhere: with a trigger from another app, such as a form or a shop, or with a schedule set on the first module, every 15 minutes by default. Mailtrap modules then run as actions or as a search further down the chain. Whether that start is instant depends on the trigger of the other app, not on Mailtrap.
04What if the Mailtrap module you need does not exist in Make?
Use Make an API Call. It is part of the Mailtrap app in Make and lets the scenario call any endpoint of the Mailtrap API with the connection you already created, so there is nothing new to authorize. You write the request yourself from the Mailtrap API documentation. For contacts, lists and single emails, the five other modules are quicker to set up, so keep the API call for what they do not cover.
05Should you use Make or n8n for Mailtrap?
It depends on how you like to work, and this page only documents the Make side. In Make, Mailtrap offers 6 modules: 5 actions and 1 search, with no trigger, plus Make an API Call for everything else. Many apps also have an n8n node, so check that Mailtrap has one before you compare. Weigh both tools on your own criteria, such as the editor you prefer and how your team already builds automations; the n8n vs Make comparison on this site walks through them.
Same platform

Other docs you might need on this stack.

Browse all integrations