Resources · Zapier integration

MailRush.io Zapier integrationAutomate MailRush.io with Zapier.

The MailRush.io Zapier integration gives you 4 triggers, 2 actions and 0 searches. The four triggers are instant: when a prospect opens, clicks, replies or unsubscribes, your other tools hear about it straight away, even on the free plan.

See the 6 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MailRush.io Zapier integration does for your outreach

It ties your MailRush.io campaigns to the rest of your sales tools. MailRush.io reports each prospect event (an open, a click, a reply, an unsubscribe) to Zapier, which runs the steps you set. In the other direction, Zapier can add a contact to a campaign or take one out of it.

Three results you can build. Replies that stop the sequence: Prospect Replies Email fires as soon as someone answers, and Unsubscribe a Contact From a Campaign takes them out of that campaign, so the person now in conversation leaves the sequence. Interest that opens a second track: Prospect Clicks Email spots a click, and Add Contact to Campaign ID puts that prospect in a campaign built for warmer leads. A CRM that knows what happened: any of the four triggers can feed a note or a status into your CRM, so the sales team sees the event without opening MailRush.io.

Now what Zapier does not do here. There is no search step, so a Zap cannot look up a prospect or a campaign in MailRush.io. Both actions want the campaign's numeric ID, not its name. There is no action to create or edit a campaign. And a Zap never reaches back: the opens, clicks and replies from before it was switched on are not replayed.

Because all four triggers are instant, the free plan's polling interval does not slow them down. To weigh Zapier against the alternatives for this kind of sales flow, see our Make vs Zapier comparison, and if you would rather hand the build over, our Zapier agency page.

Vocabulary

Zapier words, in plain English

Seven terms come back on 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. MailRush.io has four.
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 on a timer. An instant trigger is reported by the app as it happens. All four of MailRush.io's are instant.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it there otherwise.
Connection
Your MailRush.io account linked to Zapier once, then reused by every MailRush.io step of your Zaps.
Cost

What a MailRush.io Zap really costs

The trigger never costs a task, however many opens and clicks come in. Each action that succeeds counts as one task; an action that fails is not counted. A reply that unsubscribes the prospect and updates your CRM uses two.

  • Free plan100 tasks a month, two-step Zaps
  • Paid-only appNo, MailRush.io runs on the free plan
  • Triggers4, all instant, never billed
  • Filter or second actionMulti-step Zap, paid plan

MailRush.io works on the free plan: 100 tasks a month and Zaps of two steps, one trigger and one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. Opens can come in large numbers, so a Zap on Prospect Opens Email with an action behind it can eat the allowance faster than you expect. The interval grid below is the one Zapier applies to polling triggers; it does not apply to MailRush.io's four triggers, which are instant whatever the plan.

Connect

Connect your MailRush.io account

  1. 01

    Open the Apps page

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

  2. 02

    Pick MailRush.io

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

  3. 03

    Sign in and grant access

    Log in to MailRush.io in that tab and allow Zapier to use the account. The connection is saved, and every MailRush.io step of every Zap can reuse it from then on.

First Zap

Your first Zap: a reply takes the prospect out and updates your CRM

GoalWhen a prospect replies to a campaign email, the Zap unsubscribes them from that campaign and marks the reply on their record in your CRM.

  1. 01

    Pick the trigger

    Create a Zap, choose MailRush.io, then Prospect Replies Email. The editor shows a lightning bolt next to it: this trigger is instant.

  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 belong to a real prospect.

  3. 03

    Unsubscribe the prospect

    Add Unsubscribe a Contact From a Campaign, map the prospect's email from the trigger and type or map the campaign's numeric ID. Test the step.

  4. 04

    Update the CRM

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

  5. 05

    Publish

    Read each test result once more, then click Publish. Replies that arrive from now on go through; the ones received earlier do not.

Triggers

MailRush.io triggers

4 events start a Zap when something happens in MailRush.io, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Prospect Clicks Email

Instant trigger

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

Starts the Zap when a prospect clicks a link in one of your campaign emails. Among the four, it is the clearest sign of active interest short of a reply.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to move a clicker into a warmer campaign with Add Contact to Campaign ID, or to alert the salesperson who owns that lead.
Watch out
one prospect can click several links, or the same one twice, and each click can start the Zap; add a filter if one action per person is enough.
2

Prospect Opens Email

Instant trigger

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

Fires whenever a prospect opens one of your campaign emails. On its own, it is the lightest signal of the four.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to log engagement in a spreadsheet or a CRM field, where the volume of rows matters less than the overall picture.
Watch out
every open can run your action, and every successful action is a task; on the free plan, 100 tasks go quickly on a busy campaign.
3

Prospect Replies Email

Instant trigger

In Zapier“Triggers when a prospect replies an email.”

Goes off as soon as a prospect answers one of your campaign emails. For outreach, this is usually the event that matters most, because a human conversation has started.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to pull the prospect out of the campaign with Unsubscribe a Contact From a Campaign, then flag them in your CRM so someone picks up the thread.
Watch out
replies received before the Zap was published never come through, so check your inbox for those by hand.
4

Prospect Unsubscribes Campaign

Instant trigger

In Zapier“Triggers when a prospect unsubscribes a campaign”

Reacts when a prospect opts out of a campaign. The Zap receives that person's details, which lets other tools respect the decision as well.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when the same prospects also sit in a CRM or another sending tool, and an opt-out in MailRush.io should be reflected there.
Watch out
the trigger is about one campaign; if that prospect is in other MailRush.io campaigns, nothing here says so, so decide in the next steps how far the opt-out should go.
Actions

MailRush.io actions

MailRush.io gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Contact to Campaign ID

Action

In Zapier“Add contact to a campaign based on its campaign ID”

Puts a contact into a MailRush.io campaign, identified by the campaign's numeric ID, from an email the Zap carries.

When to use it
when a prospect who showed interest in one campaign, or who came from another tool, should start a different one.
Watch out
the email and the campaign ID are both required, and the ID is a number, not the campaign's name.
2

Unsubscribe a Contact From a Campaign

Action

In Zapier“Unsubscribe a contact using from a capaign”

Takes a contact out of one campaign, matched by email address and the campaign's numeric ID.

When to use it
after a reply, or when a deal moves on in your CRM and that prospect should leave the campaign.
Watch out
it acts on one campaign at a time; a prospect enrolled in several needs one step per campaign ID.
When it breaks

When a MailRush.io Zap breaks

Zapier attaches no help article to MailRush.io, and no limit specific to the app is documented. What breaks comes from Zapier's general rules and from the way the two actions are built.

  • Past events are not replayed

    A Zap only reacts to what happens after it is switched on. Opens, clicks and replies recorded before publishing never go through it.

  • Opens burn through tasks

    Prospect Opens Email can fire many times on a busy campaign, and each run with an action costs a task. Put a filter in front or pick a rarer event.

  • A wrong campaign ID

    Both actions need the campaign's numeric ID. A name, a typo or an ID from another account leaves the step with nothing it can match.

  • A sudden wave held back

    When a large send produces a huge batch of events at once, Zapier's flood protection can hold those runs back instead of passing them all on.
Need help

Need help automating MailRush.io with Zapier?

A person reads every message.

FAQ

MailRush.io Zapier integration: common questions

01Is the MailRush.io Zapier integration free?
Yes. MailRush.io is not reserved to paid plans, so it works on Zapier's free plan, which gives 100 tasks a month and Zaps of two steps: one trigger and one action. Prospect Clicks Email followed by Add Contact to Campaign ID fits that. Add a filter or a second action, such as a CRM update after the unsubscribe, and the Zap becomes multi-step and needs a paid plan. The triggers themselves never cost a task.
02How many tasks does a MailRush.io Zap use?
One per action that succeeds, and nothing for the trigger. A reply that unsubscribes the prospect and then updates your CRM uses two tasks. An action that fails is not counted. The volume to watch is on Prospect Opens Email: a busy campaign produces many opens, and if each one runs an action, the 100 tasks of the free plan go quickly. A filter in front of the action keeps that under control, though it makes the Zap multi-step.
03Are MailRush.io triggers real time in Zapier?
Yes, all four are instant. MailRush.io calls Zapier as soon as a prospect opens, clicks, replies or unsubscribes, and the Zap starts at once. The interval grid of the plans (15 minutes on Free, 2 on Professional, 1 on Team and Enterprise) applies to polling triggers only, so it does not slow these down. A lightning bolt next to the trigger in the editor confirms it, which is useful if you are on the free plan.
04What does it take to connect MailRush.io to Zapier?
A MailRush.io account with the campaigns you plan to use. In Zapier, open Apps, click + Add connection, search for MailRush.io and confirm with Add connection, then sign in in the tab that opens and grant access. For the actions, keep each campaign's numeric ID nearby: both Add Contact to Campaign ID and Unsubscribe a Contact From a Campaign require it, together with the contact's email address. The triggers need nothing beyond the connection.
05Why does Add Contact to Campaign ID fail?
Most often because of the campaign field. The action expects the campaign's numeric ID, so a campaign name, a stray character or an ID copied from another account leaves it unable to match anything. Check the number in MailRush.io and paste it, or map it from an earlier step that carries it. The email is required too: if the trigger or the previous step sends an empty value, there is no contact to add.
06What if the MailRush.io operation you need is missing?
The integration covers four prospect events (open, click, reply, unsubscribe) and two actions: add a contact to a campaign, or unsubscribe one from it. There is no search, so a Zap cannot look up a prospect or a campaign, and no action that creates or edits a campaign. If the job needs any of that, it falls outside what Zapier offers for MailRush.io, and the work stays in the MailRush.io interface.
07Zapier, Make or n8n for MailRush.io?
Compare on three criteria. Coverage: on Zapier, MailRush.io brings 4 instant triggers and 2 actions, enough to react to prospect events and move contacts between campaigns. Cost: Zapier bills each successful action, and open events can be numerous, so volume drives the bill. Shape: a reply that unsubscribes and updates a CRM is already multi-step, on a paid plan. Check how the other platforms count runs for that same flow before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations