Resources · Make integration

Mailshake Make integrationAutomate Mailshake with Make.

What if new prospects landed in the right Mailshake campaign without a CSV import? The Mailshake Make integration gives you 9 modules: 5 actions and 4 searches. This guide is for sales and growth teams, and it walks you from the API key to a working first scenario.

Try the Mailshake integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Mailshake Make integration do for your outreach?

The Mailshake Make integration links your Mailshake account to Make so that other tools can feed your cold email campaigns and read their results. You build a scenario, which is the automation itself, out of modules: each module is one brick that adds recipients, pauses a campaign or looks up leads.

Prospects enrolled once they qualify. A lead fills a form or reaches a stage in your CRM, and Add Recipients to the Campaign drops that person into the sequence you picked. Each person travels through the scenario as a bundle, one item passed from module to module.

Replies pushed back to your sales tools. List Recent Activity returns what happened in Mailshake: emails sent, opened, clicked, replied, and leads created. Map those bundles into a spreadsheet or a CRM record and your reps stop checking two dashboards.

A campaign stopped when the context changes. Pause/Unpause Campaign puts a sequence on hold when another tool signals a problem, then restarts it later. Keep in mind that a send already underway is not interrupted.

Mailshake has no trigger module in Make, so nothing starts on its own from the Mailshake side: a scenario runs on a schedule or begins with another app. When a listed module falls short, Make an API Call reaches the rest of the Mailshake API with the same connection. To weigh the platform itself, read our Make review, and if you also look at n8n, the n8n vs Make comparison lays out the criteria.

Connect

How do you connect Mailshake to Make?

  1. 01

    Create an API key in Mailshake

    You need an active Mailshake account. In Mailshake, open Extensions > API, click the button that creates a new API key, and copy the key shown on screen. Keep that tab open, you will paste it in a moment.

  2. 02

    Add a Mailshake module in Make

    In your scenario, click the + and search for Mailshake. Pick any module, then click Create a connection. A connection is your Mailshake account linked to Make once, then reused by every Mailshake module you add later.

  3. 03

    Paste the key and name the connection

    The Connection name field is optional, yet a clear label such as the name of the sending mailbox helps once you manage several accounts. Paste the API key you copied from Mailshake and follow the on-screen instructions to finish.

First scenario

Your first scenario: send new leads straight into a Mailshake campaign

GoalWhen a new lead arrives in the tool where your prospects land, Make adds that person to a chosen Mailshake campaign.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Mailshake has no trigger, so this first bubble belongs to the app where new leads show up, such as your form tool or CRM.

  2. 02

    Add Mailshake after it

    Click the + on the right of that first module, search for Mailshake and choose Add Recipients to the Campaign. Connect your account with the API key if you have not done it yet.

  3. 03

    Pick the campaign and map the lead

    Once the connection exists, Make lists the campaigns it can read, so you select the right one from the list. Then map the lead's details coming from the first module into the fields Make shows for the recipient.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time, then open the bubbles to read the bundles each module received. The import runs asynchronously, so the recipient may show up in Mailshake a little later.

  5. 05

    Schedule it and switch it on

    Set the schedule on the first module with the clock icon (every 15 minutes by default, 15 minutes at minimum on the Free plan), then switch the scenario on. Each module run counts as one operation on your plan.

Modules

What the Mailshake modules do in Make

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

Mailshake1

Add Recipients to the Campaign

Action

In Make“Adds new recipients to the selected campaign. This action is asynchronous and can take some time before all recipients are imported.”

Enrolls new people into the Mailshake campaign you select, so a fresh lead starts receiving your sequence without a manual import.

When to use it
right after a prospect qualifies in another tool, for example a demo request or a lead moved to the outbound stage of your CRM.
Watch out
the import is asynchronous and can take some time, so a module placed right after it may not find the new recipient yet.
Mailshake2

Get a Campaign

Action

In Make“Retrieves campaign by its ID.”

Fetches one Mailshake campaign from its ID and returns its details as a single bundle you can map further down the scenario.

When to use it
you already hold the campaign ID, passed on by an earlier module or stored in a spreadsheet, and you only need that one campaign.
Watch out
it needs the exact ID; when all you know is a name or a rough criterion, start with Search Campaigns instead.
Mailshake3

Get a Recipient

Action

In Make“Retrieves recipient by their ID.”

Pulls a single recipient from its ID, which gives the rest of the scenario the full record of one person already enrolled in a campaign.

When to use it
an activity bundle points to a recipient and you want that person's details before updating your CRM or alerting a rep.
Watch out
without the ID this module cannot help; Search Recipients is the one that finds people from criteria.
Mailshake4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Mailshake API from your scenario, reusing the same connection, so you are not limited to the eight ready-made modules.

When to use it
the action you need has no dedicated module in the list, yet the Mailshake API offers it.
Watch out
you write the request yourself, so keep the Mailshake API documentation open and check the response with Run once before you switch the scenario on.
Mailshake5

Pause/Unpause Campaign

Action

In Make“Pauses or resumes the campaign. If the campaign is currently being sent, it will not be stopped.”

Puts a Mailshake campaign on hold or resumes it, which lets another tool decide when your sequence should stop talking to prospects.

When to use it
a signal elsewhere says the timing is wrong, such as a product incident logged in your helpdesk, and outreach should wait.
Watch out
a campaign that is sending at that moment is not stopped by the pause, so the emails already on their way still go out.
Mailshake6

List Recent Activity

Search

In Make“Lists recent activity: sent, opened, clicked, replied or leads created.”

Returns what just happened in Mailshake: emails sent, opened, clicked, replied, and leads created, each as its own bundle for the next module.

When to use it
you want replies and clicks to reach your CRM or a team channel so reps react without opening Mailshake.
Watch out
as a search it can return zero, one or many bundles, and every bundle then costs an operation in each module that follows.
Mailshake7

Search Campaigns

Search

In Make“Lists campaigns by search criteria.”

Finds the Mailshake campaigns that match your search criteria and hands them over one by one, which is handy when you do not know an ID yet.

When to use it
a scenario must work on several campaigns, for instance to report on them in a spreadsheet or pause a group of them.
Watch out
each campaign found becomes a bundle, so a loose criterion can multiply the operations of the modules placed after it.
Mailshake8

Search Leads

Search

In Make“Lists all leads by search criteria.”

Lists the leads your Mailshake campaigns created that fit your criteria, ready to be copied into the tool your reps follow up in.

When to use it
your sales team works from a CRM and needs every new Mailshake lead there, with the details your reps follow up on.
Watch out
leads and recipients are separate lists; to check who is enrolled in a campaign, reach for Search Recipients.
Mailshake9

Search Recipients

Search

In Make“Lists recipients by search criteria.”

Looks through campaign recipients by your criteria and returns the matching people, which tells you whether someone is already in a sequence.

When to use it
before Add Recipients to the Campaign, to avoid enrolling a prospect twice when the same person fills your form again.
Watch out
the search can come back empty; add a filter after it so the scenario only continues when the result matches what you expect.
Need help

Need help automating Mailshake with Make?

A person reads every message.

FAQ

Questions about the Mailshake Make integration

01Is the Mailshake Make integration free?
Yes, on the Make side. Mailshake is a standard app, available from the Free plan onward. The Free plan allows 2 active scenarios, runs them at most every 15 minutes, caps each run at 5 minutes and includes 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. You still need your own active Mailshake account, whose subscription is handled by Mailshake.
02What do you need to connect Mailshake to Make?
An active Mailshake account and an API key. In Mailshake, go to Extensions > API, create a new key and copy it. In Make, add any Mailshake module, click Create a connection, give it a name if you like, and paste the key. That connection then serves every Mailshake module in all your scenarios, so the key is entered only once per account. The name is optional, but a clear label, such as the sending mailbox, saves you from mixing up accounts once you link more than one.
03Can a Mailshake scenario in Make start in real time?
Not from Mailshake itself. The app has no trigger module in Make, neither scheduled nor instant, so Mailshake cannot start a scenario when an email gets a reply. You have two ways in. Put another app first, for example the form or CRM where leads arrive, and let its trigger launch the scenario. Or start with a Mailshake search such as List Recent Activity and let the schedule run it, every 15 minutes by default.
04What if the Mailshake module you need is missing in Make?
Use Make an API Call. This module reaches any endpoint of the Mailshake API with the connection you already set up, so an action that none of the listed modules covers stays within reach. It asks you to build the request yourself, so test it with Run once and read the returned bundle. Also note that the Make documentation for Mailshake is flagged as AI-generated, so verify important details with Mailshake directly.
05Should you use Make or n8n with Mailshake?
It depends on the tool your team already runs. In Make, Mailshake comes with 9 modules, 5 actions and 4 searches, plus Make an API Call to reach the rest of the API, and every step described on this page happens in the visual editor. If your automations live in n8n, check whether a Mailshake node exists there before moving anything. Pick the platform that already holds your other workflows so everything stays in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations