Resources · Zapier integration

Mailshake Zapier integrationAutomate Mailshake with Zapier.

The Mailshake Zapier integration gives you 6 triggers, 8 actions and 0 searches. The triggers are all polling ones, so a reply or a click reaches Zapier at the next check of your plan, and several actions can send campaign emails as soon as they run.

See the 14 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Mailshake Zapier integration does for your outreach

It links your Mailshake campaigns to the rest of your sales stack. Zapier checks Mailshake on a timer for new replies, clicks, opens, leads and sent messages, then runs the steps you chose. In the other direction, it can add recipients to a campaign, turn them into leads, pause them, or unsubscribe them.

Three results you can build. A reply that stops the follow-ups: New Reply picks up the answer, and Pause/Unpause Recipient holds that person's pending emails in the campaign while someone handles the conversation. Clicks that become leads: New Click flags interest, and Create Leads turns that recipient into a lead in the same campaign, ready for your sales follow-up. A form that feeds a campaign: a new entry in your form tool runs Add Recipient by Email Address, and the person joins the sequence without a manual import.

Now what Zapier does not do here. None of the triggers is instant: each one waits for Zapier's next check, at an interval set by your plan. There is no search, so a Zap cannot look up a recipient or a lead. Pausing a campaign does not stop the emails already on their way. And a Zap never replays the past: replies, opens and leads from before you switched it on stay where they are.

The same app also has a Mailshake Make integration page, handy if you want to compare. For the criteria behind that choice, see Make vs Zapier.

Vocabulary

Zapier words, in plain English

Seven terms come back across this page. Here they are once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
Trigger
The event in an app that starts the Zap; once the Zap is on, Zapier waits for it. Mailshake offers six.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of these.
Polling vs instant
A polling trigger is checked by Zapier at a fixed interval. An instant one is pushed by the app. All six Mailshake triggers poll.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it there otherwise.
Connection
Your Mailshake account linked to Zapier once, then reused by every Mailshake step of your Zaps.
Cost

What a Mailshake Zap really costs

Checking Mailshake for new replies or clicks costs nothing, however often Zapier looks. Each action that succeeds counts as one task; one that fails is not counted. A reply that pauses the recipient and updates your CRM uses two tasks.

  • Free plan100 tasks a month, two-step Zaps
  • Paid-only appNo, Mailshake runs on the free plan
  • Triggers6, all polling, never billed
  • Filter or second actionMulti-step Zap, paid plan

Mailshake works on the free plan: 100 tasks a month, Zaps of two steps, and a check every 15 minutes. A filter or a second action makes the Zap multi-step, which needs a paid plan. A few apps and actions take more than one task, so read your task history after the first runs. The grid below sets how often Zapier checks Mailshake's six polling triggers on each plan, and on the paid plans a check can also be run by hand from the editor.

Connect

Connect your Mailshake account

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. Have your Mailshake login ready, with access to the campaigns the Zap will read or change.

  2. 02

    Pick Mailshake

    Type Mailshake in the dialog's search box, select it in the results, then click Add connection. A new tab opens on Mailshake's side so you can sign in there.

  3. 03

    Sign in and grant access

    Log in to Mailshake in that tab and allow Zapier to use the account. The connection is saved, and every Mailshake step in every Zap can reuse it afterwards.

First Zap

Your first Zap: a reply pauses the recipient and updates your CRM

GoalWhen a recipient replies, the Zap pauses their pending emails in that campaign and marks the reply on their record in your CRM.

  1. 01

    Pick the trigger

    Create a Zap, choose Mailshake, then New Reply. It is a polling trigger, so Zapier will check for replies at your plan's interval.

  2. 02

    Test on a real reply

    Run the trigger test. Zapier brings back the three most recent replies from your account, so the fields you map next come from an actual recipient.

  3. 03

    Pause the recipient

    Add Pause/Unpause Recipient, pick the campaign, map the email from the reply and choose to pause. Test it and check the recipient in Mailshake.

  4. 04

    Update the CRM

    Add your CRM's update action, find the contact by email and set the field that records the reply. With two actions, this Zap is multi-step and needs a paid plan.

  5. 05

    Publish

    Review each test result, then click Publish. Replies that come in from now on go through; the ones received earlier are not picked up.

Triggers

Mailshake triggers

6 events start a Zap when something happens in Mailshake. Zapier checks for them at the interval your plan allows.

1

New Click

Polling trigger

In Zapier“Triggers when a recipient clicks on a link.”

Starts the Zap when a recipient clicks a link in one of your campaign emails. It is one of the triggers Zapier highlights for Mailshake, and a useful sign of interest.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to turn a clicker into a lead with Create Leads, or to alert the person who owns the account.
Watch out
without the Exclude Duplicates? option, every click can start the Zap; switch it on to react only to a recipient's first click on a given link.
2

New Lead

Polling trigger

In Zapier“Triggers when a lead is created.”

Goes off when a new lead appears in Mailshake. The Zap receives the lead and the recipient behind it, ready for the steps that follow.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to push each new lead into your CRM as a contact or a deal, so sales picks it up there.
Watch out
only leads created after the Zap is published come through; the ones that already existed have to be moved by hand.
3

New Lead Status

Polling trigger

In Zapier“Triggers when the status of a lead changes.”

Reacts when a lead's status changes, for example when it is marked won or lost in Mailshake. The Zap gets the lead with its new status.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to mirror the outcome in your CRM, or to log closed leads in a spreadsheet for reporting.
Watch out
as a general precaution, let this Zap write outside Mailshake; a Zap that writes where its own trigger watches can set itself off again.
4

New Message Sent

Polling trigger

In Zapier“Triggers when an email is sent to a recipient from one of the campaign sequence messages.”

Fires each time one of your campaign's sequence messages goes out to a recipient. It tracks what Mailshake sends, not what recipients do.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to keep a sending log outside Mailshake, or to note on a CRM record that a given step of the sequence went out.
Watch out
a large campaign sends many messages, and an action behind each one spends a task every time.
5

New Open

Polling trigger

In Zapier“Triggers when a recipient opens an email.”

Runs each time a recipient opens one of your campaign emails. On its own it is a light signal, more telling as a trend.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to log engagement in a spreadsheet or a CRM field, where the overall trend matters more than any single row.
Watch out
turn on Exclude Duplicates? so only the first open of a given email counts; otherwise repeat opens can each run your action and spend a task.
6

New Reply

Polling trigger

In Zapier“Triggers when a recipient replies to one of your messages.”

Fires when a recipient answers one of your messages. For outreach, this is usually the event that matters most, since a conversation has begun.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to pause the recipient's next emails with Pause/Unpause Recipient and hand the thread to a person.
Watch out
the reply only reaches the Zap at Zapier's next check, not the moment it lands in Mailshake.
Actions

Mailshake actions

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

1

Add Recipient by Email Address

Action

In Zapier“Adds a single recipient to a campaign. NOTE: This can cause emails to immediately be sent.”

Puts one person into a chosen campaign from a single email address.

When to use it
when each new contact from a form or a CRM should join a sequence on their own.
Watch out
adding a recipient can make Mailshake send the first email straight away, so test on a campaign you are ready to run.
2

Add Recipients by Email Addresses

Action

In Zapier“Adds multiple recipients to a campaign. NOTE: this can cause emails to be immediately sent.”

Adds several people to a campaign in one go, from a list separated by commas or new lines; names can come along with each address.

When to use it
when an earlier step hands over a batch of addresses at once.
Watch out
as with the single version, emails may go out right away.
3

Add Recipients From CSV

Action

In Zapier“Adds a list of recipients to a campaign via a CSV file. Each column can be used as a text replacement. NOTE: This can cause emails to immediately be sent.”

Loads a whole list into a campaign from a CSV file, and every extra column becomes a field you can use in your email text.

When to use it
when the list lives in a file with personalization data per recipient.
Watch out
the file must sit at a publicly reachable link with a header row, and you must name the email column; sending may start at once.
4

Create Leads

Action

In Zapier“Creates leads from existing recipients that match the given email addresses.”

Turns existing recipients into leads, matched on the email addresses you pass in.

When to use it
after a click or a reply, to mark the people sales should now follow up.
Watch out
only recipients already in the campaign you pick can become leads; an address outside it produces nothing.
5

Pause/Unpause Campaign

Action

In Zapier“Pauses or unpauses all sending for a campaign. When pausing, emails currently being sent will not be stopped. When unpausing, the sending calendar will be rescheduled to account for any pending emails.”

Stops or restarts all sending for a whole campaign.

When to use it
when an event elsewhere means the campaign should go quiet, then resume.
Watch out
pausing does not halt emails already being sent, and unpausing reschedules the sending calendar to fit everything still pending.
6

Pause/Unpause Recipient

Action

In Zapier“Pauses or unpauses a recipient from receiving pending emails. WARNING: When unpausing, this may cause emails to be sent immediately.”

Holds or releases one recipient's pending emails within a campaign, depending on the choice you set.

When to use it
to pause someone who replied or booked a call, and resume them later if needed.
Watch out
unpausing can send the waiting emails immediately, so check what is queued before you release.
7

Unsubscribe Recipients

Action

In Zapier“Unsubscribes one or more recipients from all current and future campaigns for your team.”

Removes one or more addresses from every current and future campaign of your team, not just one.

When to use it
when someone opts out in another tool and must never be contacted from Mailshake again.
Watch out
it is team-wide and covers future campaigns, so use Pause/Unpause Recipient if you only meant one campaign.
8

Update Lead Status

Action

In Zapier“Updates lead status to Won, Lost, Ignored, or Reopened.”

Sets a lead's status to Won, Lost, Ignored or Reopened, for a given email within a given campaign.

When to use it
when the deal is decided in your CRM and Mailshake should reflect the outcome.
Watch out
campaign and email are both required, and the lead has to exist in the campaign you name.
When it breaks

When a Mailshake Zap breaks

Zapier attaches no help article to Mailshake, and no limit specific to the app is documented. What breaks comes from Zapier's general rules and from how Mailshake's own actions behave.

  • Emails go out sooner than planned

    Adding recipients, or unpausing one, can make Mailshake send right away. Test with a campaign you are ready to launch, never a draft you are still editing.

  • A reply is seen at the next check

    All six triggers poll, so a reply waits for Zapier's next check, every 15 minutes on the free plan. Do not build a Zap that needs to react within seconds.

  • Pausing does not recall emails

    Pause/Unpause Campaign stops future sending for the whole campaign, but emails that are already being sent at that moment are not halted.

  • A Zap that restarts itself

    A Zap that writes into the very place its own trigger watches can set itself off again and again, and burn through your task count fast. Point it somewhere else.

  • The past is not picked up

    A Zap only reacts to what happens after it is switched on. Older replies, opens and leads never go through it.

  • A big batch held back

    When a check suddenly returns a huge batch, after a bulk import for instance, Zapier's flood protection can hold those items back.
Need help

Need help automating Mailshake with Zapier?

A person reads every message.

FAQ

Mailshake Zapier integration: common questions

01Is the Mailshake Zapier integration free?
Yes. Mailshake is not reserved to paid plans, so it runs on Zapier's free plan, which gives 100 tasks a month, Zaps of two steps and a check every 15 minutes. New Reply followed by Update Lead Status fits within that. Add a filter or a second action, such as a CRM update after the pause, and the Zap becomes multi-step, which needs a paid plan. Zapier's checks for new data cost nothing, however often they run.
02How many tasks does a Mailshake Zap use?
One per action that succeeds, none for the trigger or for Zapier's checks. A reply that pauses the recipient and updates your CRM uses two tasks. An action that fails is not counted. The volume to watch sits on New Open and New Message Sent, which can fire often on a busy campaign. Turning on Exclude Duplicates? on New Open, or picking a rarer event like New Reply, keeps the count down.
03Are Mailshake triggers real time in Zapier?
No. All six Mailshake triggers are polling ones: Zapier checks Mailshake at a fixed interval and picks up what is new. The interval depends on the plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans you can also run a check by hand from the editor. Zapier remembers what it has already seen, so the same reply does not start the Zap twice.
04What does it take to connect Mailshake to Zapier?
A Mailshake account and the campaigns you plan to use, already set up in it. In Zapier, open Apps, click + Add connection, search for Mailshake and confirm with Add connection, then sign in in the tab that opens and grant access. Most actions ask you to pick a campaign from a list, and Zapier can only show campaigns that exist in your Mailshake account at that point. The connection is then reused by every Mailshake step.
05Why did Mailshake send emails as soon as the Zap ran?
Because adding recipients can start sending right away. Add Recipient by Email Address, Add Recipients by Email Addresses and Add Recipients From CSV all carry that behavior, and Pause/Unpause Recipient can do the same when it unpauses someone with emails waiting. The fix is to test on a campaign you are ready to run, or on a test address, and to check what is queued before you release a paused recipient.
06What if the Mailshake operation you need is missing?
The integration covers six events (clicks, opens, replies, new leads, lead status changes, sent messages) and eight actions to add recipients, create and update leads, pause and unpause, and unsubscribe. There is no search, so a Zap cannot look up a recipient or a lead, and no action creates or edits a campaign. If the job needs one of those, it sits outside what Zapier offers for Mailshake today, and the work stays in Mailshake itself.
07Zapier, Make or n8n for Mailshake?
Compare on three criteria. Coverage: on Zapier, Mailshake brings 6 triggers and 8 actions, with no search. Speed: the triggers poll, so the plan's interval decides how soon a reply reaches the Zap. Cost: Zapier bills each successful action, and a flow with a filter or two actions is multi-step and paid. Set those against how Make and n8n handle the same app and count runs, then decide on your volume.
Same platform

Other docs you might need on this stack.

Browse all integrations