Resources · Make integration

Mailkit Make integrationAutomate Mailkit with Make.

Mailkit already sends your campaigns, so why not let it react to what your recipients do? The Mailkit Make integration gives you 18 modules, 2 of them instant triggers, to sync subscribers, send emails or SMS and follow carts without code. This guide takes you to a working first scenario.

Try the Mailkit integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Mailkit Make integration do for you?

The Mailkit Make integration links your Mailkit account to Make, a no-code tool where you build a scenario (the automation itself) out of modules, one brick per step: a trigger, an action or a search. Mailkit can then start a scenario the moment someone subscribes or leaves, and your other apps can add recipients, send emails or SMS and track carts in Mailkit.

Greet every new subscriber. Watch for Subscribes fires as soon as someone joins a list, and Send an Email Message sends them a welcome built on a campaign you already set up in Mailkit. An online shop gets its first contact out without anyone watching the list.

Follow what sits in a cart. Initialize EventAPI opens tracking for a site visitor, then Add Item to Event, Remove Item from Event and Clear all Items of an Event keep the event in step with the shop. List Items from Event reads it back when you want to remind someone about what they left.

Respect opt-outs everywhere. Watch for Unsubscribes tells your other tools the moment a person leaves, so a sales team stops writing to them from the CRM too. Unsubscribe a Recipient works the other way when the request comes in through support.

Mailkit has no scheduled trigger in Make: anything other than a subscribe or an unsubscribe has to start from another app or from the scenario's schedule. The plans and their limits are summed up in Make pricing. Many apps also exist in n8n; n8n vs Make puts the two side by side, and Make training helps if you want to go further on your own.

Connect

How do you connect Mailkit to Make?

  1. 01

    Grab your credentials in Mailkit

    In Mailkit, open Profile, then Integration, and copy the API key and the API token shown on screen. While you are there, check that your IP address is on the list of permitted IPs.

  2. 02

    Add a Mailkit module in Make

    In your scenario, add any Mailkit module and click Create a connection. A connection is your Mailkit account linked to Make once, then reused by every Mailkit module. You can type a label in Connection name if you like.

  3. 03

    Paste the values and save

    Enter the credentials you copied from Mailkit, or follow the instructions Make shows in the window, then save. Once saved, the module fields become available to fill in.

First scenario

Your first scenario: welcome each new Mailkit subscriber

GoalWhen someone subscribes to a Mailkit list, Make sends them a welcome email built on one of your Mailkit campaigns.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to place your first module.

  2. 02

    Pick Watch for Subscribes

    Search for Mailkit, choose Watch for Subscribes, click Create a webhook, then Create a connection and link your account with the credentials from Mailkit.

  3. 03

    Add Send an Email Message

    Click the + on the right of the trigger and add Send an Email Message. Choose the campaign that holds your welcome email, then map the subscriber data coming from the trigger.

  4. 04

    Test with Run once

    Click Run once, then subscribe a test address to your list. Each bundle (one item handed from a module to the next, here one subscriber) appears on the modules so you can check it.

  5. 05

    Switch the scenario on

    When the test email lands, turn the scenario on. The trigger is instant, so Mailkit calls Make through the webhook each time someone subscribes, with no polling on the schedule.

Triggers

What can start a Mailkit scenario?

2 modules start a scenario when something happens in Mailkit. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Mailkit as soon as it happens.

Mailkit1Watch for Subscribes

Watch for Subscribes

Instant trigger

In Make“Triggers your automation when a new recipient subscribes to your list.”

Starts your scenario the moment a new recipient joins one of your Mailkit lists, so the rest of your stack hears about the signup without anyone exporting a file. The new subscriber then flows into the next modules.

How it fires
instant, the app calls Make through a webhook as soon as it happens, so you never wait for a scheduled check.
When to use it
you want to welcome a new contact, copy them into a CRM or alert a teammate right after they sign up.
Watch out
when you add it, click Create a webhook before Create a connection, or the trigger has nothing to receive.
Mailkit2Watch for Unsubscribes

Watch for Unsubscribes

Instant trigger

In Make“Triggers your automation when a recipient unsubcribes.”

Reacts when a recipient leaves your list, which gives your other tools a chance to stop writing to that person too. Nobody has to copy opt-outs from Mailkit into a spreadsheet anymore.

How it fires
instant, the app calls Make through a webhook as soon as it happens, with no interval to wait for.
When to use it
a CRM, a support desk or a text messaging tool must respect the choice of someone who left your emails.
Watch out
never end this scenario on Add/update Recipient for the same list, or you would put back the very person who just left.
Modules

What else can Make do in Mailkit?

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

Mailkit1

Add Item to Event

Action

In Make“Adds a New Item to an Event”

Places a new item inside a Mailkit event, the container that works like a shopping cart for one visitor. Mailkit then knows which product that person picked on your site.

When to use it
your shop app reports a product added to the cart and you want Mailkit to hold that line.
Watch out
if you only get one click at a time for the same product, the increment version counts better.
Mailkit2

Add Item to Event (increment)

Action

In Make“Adds an Item to Event Incrementaly. It Allows you to Increase the Quantity of an Item in the Event by Successive Calls Rather Than Specifying Explicit Quantity.”

Raises the quantity of an item in an event call after call, so you never compute the total yourself. Each run adds a little more to the count already there.

When to use it
a visitor clicks add on the same product several times and your scenario only hears about each click separately.
Watch out
when you already know the exact quantity, the plain Add Item to Event is simpler.
Mailkit3

Add/update Recipient

Action

In Make“Adds an email address and related recipient details to the mailing list”

Writes an email address and the details that go with it into a Mailkit mailing list, creating the recipient or refreshing the existing one. Your lists stay in line with the tool where contacts are born.

When to use it
a lead fills a form or a buyer checks out in another app and should land in the right Mailkit list.
Watch out
map the email field carefully, since it is what ties the record to a recipient.
Mailkit4

Clear all Items of an Event

Action

In Make“Removes all Items from a Event container. This is similar to emptying a shopping cart.”

Empties an event in a single call, much like clearing a shopping cart, whatever items and quantities were inside. The event is ready for a fresh start.

When to use it
an order is confirmed and the products no longer need to sit in the visitor's event.
Watch out
it removes every line at once; to drop a single product, reach for Remove Item from Event instead.
Mailkit5

Create a Campaign

Action

In Make“Creates a new campaign in Mailkit. Campaigns hold the settings and contents for deliveries and can be updated. It's recommended to keep the same campaign for a specific topic rather than creating a new campaign for each send.”

Creates a campaign in your Mailkit account, the object that holds the settings and content of your deliveries. You can prepare it from a scenario instead of the Mailkit interface.

When to use it
a new topic starts, such as a product line or a recurring newsletter, and deserves its own campaign.
Watch out
Mailkit advises keeping one campaign per topic and reusing it, not creating a new one for each send.
Mailkit6

Create New Mailing-list

Action

In Make“Adds a New Mailing List to your Mailkit Account”

Adds a brand new mailing list to your Mailkit account straight from Make, ready to receive recipients. No need to open Mailkit to prepare it by hand.

When to use it
a new store, event or client account opens in another tool and needs its own list before any contact arrives.
Watch out
run it once per new audience, never once per contact, or your account fills with near-empty lists.
Mailkit7

Initialize EventAPI

Action

In Make“Initializes access to EventAPI for a website visitor.”

Opens access to Mailkit's EventAPI for one website visitor, the starting point for tracking what that person puts in or takes out of a cart. The item modules below all work on events.

When to use it
a visitor begins a session on your site and you plan to follow their cart in Mailkit.
Watch out
place it early in the flow, before the modules that add or remove items.
Mailkit8

Make an API call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Mailkit API from your scenario, with the same connection as the other modules. It is your way out when a ready-made module does not cover a need.

When to use it
you need a Mailkit feature that none of the listed modules offers.
Watch out
you work with the raw API here, so keep Mailkit's API documentation open to get the request right.
Mailkit9

Remove Item from Event

Action

In Make“Removes an Item from Event (irrespective of item quantity)”

Takes one item out of an event, whatever quantity it had, so Mailkit stops counting that product for the visitor. The rest of the event stays untouched.

When to use it
a customer deletes a product from the cart in your shop and the reminder email should not mention it.
Watch out
to lower the quantity by one instead of deleting the whole line, choose the decrement version.
Mailkit10

Remove Item from Event (decrement)

Action

In Make“Removes an Item from Event decrementally. It allows you to decrease the quantity of an item in the event by successive calls rather than specifying explicit quantity.”

Lowers the quantity of an item in an event step by step, one call at a time, rather than setting a number. Mailkit follows each small change as it comes.

When to use it
your shop only reports each minus click on a product and you want the count in Mailkit to match.
Watch out
to remove the line completely in one call, Remove Item from Event is the right module.
Mailkit11

Send an Email Message

Action

In Make“Sends an Email message based on a campaign stored in your Mailkit account.”

Sends an email built on a campaign stored in Mailkit: the content and settings come from Mailkit, and the scenario only picks the moment and the recipient. You keep your design where it already lives.

When to use it
a purchase, a signup or a form reply calls for a message right away.
Watch out
the campaign must exist in Mailkit first; Create a Campaign can prepare one if needed.
Mailkit12

Send an SMS Message

Action

In Make“Sends an SMS message to a mobile recipient”

Sends a text message to a mobile recipient straight from the scenario, which lets your automation reach someone away from their inbox. It pairs well with an email when both channels matter.

When to use it
a delivery update or a changed appointment belongs on a phone rather than in an inbox.
Watch out
Mailkit tracks SMS opt-outs apart from email ones, so check the phone channel separately.
Mailkit13

Unsubscribe a Recipient

Action

In Make“Unsubscribes Recipient from all Future Communications. Unsubscribes are Separate for Emails and Phone Numbers as those are Distinct Communication Channels (Email/SMS)”

Stops all future communications from Mailkit to a recipient, so a request made anywhere is honored in your sending tool. The opt-out is recorded on one channel at a time.

When to use it
someone asks your support team to stop hearing from you, or your CRM marks the contact as opted out.
Watch out
email and phone numbers are separate channels, so unsubscribing an address does not stop texts.
Mailkit14

Get Recipient Details

Search

In Make“Retrieves all Available Information about the Recipient. This Could be Used to Identify a Specific Recipient Using ID_send_message Passed in UTM Parameters. The Default Mailkit Tracking Tagset Passes the ID_send_message in Utm_term.”

Returns everything Mailkit holds about one recipient. It can also tell you who clicked, thanks to the ID_send_message Mailkit passes in UTM parameters, by default in utm_term.

When to use it
a visitor lands on your site from an email and you want to know who it is before updating your CRM.
Watch out
as a search, it can come back empty, so plan what the scenario does in that case.
Mailkit15

Get Recipient History

Search

In Make“Retrieves all campaign history and interactions for a recipient”

Pulls the campaign history and the interactions of one recipient, so you see what they received and how they reacted. Handy context before anyone reaches out.

When to use it
a sales rep opens a deal and wants to know which campaigns the contact already got.
Watch out
a search can return several bundles; add an aggregator if you need one summary line.
Mailkit16

List Items from Event

Search

In Make“Lists all Items currently present in the Event”

Reads every item currently sitting in an event, like looking inside a cart before deciding what to send. You get the products the visitor still holds.

When to use it
before a reminder email, you want to check what was left behind.
Watch out
each item comes out as its own bundle, and every following module runs once per bundle, which counts as an operation each time.
Need help

Need help automating Mailkit with Make?

A person reads every message.

FAQ

Questions about Mailkit in Make

01Is the Mailkit Make integration free?
Yes. Mailkit is a standard app in Make, so its modules work on the Free plan. That plan gives you 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. You still need an active Mailkit account; its subscription is described on the Mailkit pricing page.
02What do you need to connect Mailkit to Make?
An active Mailkit account with access to Profile, then Integration. That page holds the values Make asks for: the doc mentions your user ID and MD5 hash, and the screen shows an API key and an API token to copy. Your IP address must also be added to the list of permitted IPs in Mailkit. In Make, add a Mailkit module, click Create a connection, give it a name if you want and paste the values. For the two instant triggers, click Create a webhook before Create a connection.
03Do the Mailkit triggers in Make fire in real time?
Yes. Watch for Subscribes and Watch for Unsubscribes are both instant triggers: Mailkit calls Make through a webhook as soon as someone joins or leaves a list, so the scenario does not wait for the default schedule of every 15 minutes. The app has no scheduled trigger. To start from something else, such as a cart or a new order, open the scenario with a trigger from another app or let the schedule on the first module run it, then chain the Mailkit actions and searches after it.
04What if a Mailkit module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Mailkit API from your scenario with the connection you already set up, so you are not limited to the ready-made modules. The Make doc for Mailkit lists no specific limits. It does warn that its content is generated by AI from Mailkit's own documentation and may contain mistakes, so confirm important details with Mailkit directly. When the need sits in another tool, add that app's modules to the same scenario and pass the data along.
05Make or n8n for Mailkit?
It depends on where your other automations already run. In Make, Mailkit comes with 18 modules: 2 instant triggers, 13 actions including Make an API Call, and 3 searches, all behind one connection. n8n also covers many apps with its own nodes, so check whether a Mailkit node exists and fits your case before choosing. Judge on the modules your flows actually need, and keep your automations on the platform your team already knows, rather than splitting them across two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations