Resources · Zapier integration

Mailrith Zapier integrationAutomate Mailrith with Zapier.

The Mailrith Zapier integration gives you 10 triggers, 8 actions and 1 search. Every trigger is instant, so a sign-up, a bounce or a new tag reaches your other tools without waiting for the next check, even on the free plan.

See the 19 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Mailrith Zapier integration does for your list

It connects your Mailrith list to the rest of your tools. Mailrith tells Zapier when something happens to a subscriber (a sign-up, an unsubscribe, a bounce, a tag), and Zapier runs the steps you chose. The other way round, Zapier can create subscribers, tag them, or move them in and out of sequences in Mailrith.

Three results you can build. A sequence that starts on its own: New Form Subscriber fires when someone fills a given form, and Add Subscriber to Sequence enrolls them in the right follow-up. A clean record elsewhere: New Unsubscribe, New Subscriber Bounce and New Subscriber Complaint each pass the address on, so the spreadsheet or tool that also holds it can be corrected. Tags as switches: New Tag Added to Subscriber watches one tag, and adding that tag by hand in Mailrith becomes the signal that sets off a whole chain.

Now what Zapier does not do here. There is no action that deletes a subscriber. Create Subscriber fails on an address that already exists, so it cannot double as an update. Update Subscriber works from a subscriber picked or found first, not from an email alone. And a Zap never goes back in time: the people already on your list before you switch it on are not processed.

All ten triggers are instant. That matters on the free plan, where polling triggers in other apps wait for the next check. If you are weighing Zapier against the alternatives for this kind of list work, see our Make vs Zapier comparison and our Zapier review page.

Vocabulary

Zapier words, in plain English

Eight terms come back across this page. Read them once and the rest goes faster.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Mailrith offers ten.
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 completed successfully. The count on your plan is a count of those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant one is reported by the app the moment it happens. All of Mailrith's are instant.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it there otherwise.
Search step
A step that looks up something already in an app, so the steps after it can use what it found.
Connection
Your Mailrith account linked to Zapier once, then reused by every step that calls Mailrith.
Cost

What a Mailrith Zap really costs

The trigger never costs a task. Each action that succeeds counts as one; an action that fails is not counted. A Zap that tags then enrolls someone uses two tasks per subscriber.

  • Free plan100 tasks a month, two-step Zaps
  • Paid-only appNo, Mailrith runs on the free plan
  • Triggers10, all instant, never billed
  • Search or filterMakes the Zap multi-step, paid plan

Mailrith works on the free plan: 100 tasks a month, Zaps of two steps only. A filter, a Find Subscriber step 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 interval grid below is the one Zapier applies to polling triggers; it does not apply to Mailrith's triggers, which are all instant and fire straight away whatever the plan.

Connect

Connect your Mailrith account

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. Have your Mailrith login ready, along with access to the forms, sequences and tags the Zap will touch.

  2. 02

    Pick Mailrith

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

  3. 03

    Sign in and grant access

    Log in to Mailrith in that tab and allow Zapier to use the account. The connection then appears in your list and every Mailrith step of every Zap can reuse it.

First Zap

Your first Zap: form sign-ups enrolled in a sequence and logged

GoalEach person who joins through one Mailrith form is added to a welcome sequence and recorded as a row in your spreadsheet.

  1. 01

    Pick the trigger

    Create a Zap, choose Mailrith and New Form Subscriber, then select the form in the list. The editor shows a lightning bolt: this trigger is instant.

  2. 02

    Test it on a real sign-up

    Run the trigger test. Zapier brings back the three most recent sign-ups of that form, so the fields you map next come from a real person.

  3. 03

    Enroll them

    Add Add Subscriber to Sequence, choose the welcome sequence, and map the email that came from the trigger. Test it and check the person in Mailrith.

  4. 04

    Log the row

    Add your spreadsheet's new-row action and map the email and the date of the sign-up. 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. From then on, every new sign-up on that form goes through, but people who joined earlier do not.

Triggers

Mailrith triggers

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

1

New Form Subscriber

Instant trigger

In Zapier“Triggers when a subscription occurs on a specific form.”

Starts the Zap when someone signs up through one particular Mailrith form, the one you select while setting it up. Other forms on the account are ignored, which keeps each flow tied to its own entry point.

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 a form leads to its own offer or welcome path and the follow-up should differ from the other forms.
Watch out
choosing the form is mandatory, so a form that does not exist yet in Mailrith cannot be picked; create it there before building the Zap.
2

New Landing Page Subscriber

Instant trigger

In Zapier“Triggers when someone subscribes through a selected landing page.”

Here the starting point is a landing page rather than a form: the Zap runs each time a visitor subscribes on the Mailrith page you selected, and only on that page.

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 each landing page carries its own campaign and its sign-ups should be routed or labeled separately.
Watch out
the landing page is a required choice, and one Zap watches one page; a second page means a second Zap or a copy of this one.
3

New Sequence Subscriber

Instant trigger

In Zapier“Triggers when a subscriber is added to a sequence.”

Fires once a subscriber enters the sequence you selected. The Zap gets that person's record, ready for the next steps, and other sequences on the account are left aside.

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 mirror enrollment somewhere else, for instance a row or a note that says this person is now in the onboarding series.
Watch out
the sequence is required. As a general precaution, keep this Zap from writing back into Mailrith: a Zap that writes where its own trigger watches can set itself off again.
4

New Subscriber

Instant trigger

In Zapier“Triggers when a new subscriber is confirmed within your account.”

The widest of the ten: it reacts to any new subscriber, whatever the source, once Mailrith counts them as confirmed on your account. No form, page or tag to choose.

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 every new person on the list should land in the same place, such as one master spreadsheet or a shared notification.
Watch out
Mailrith describes it in terms of confirmed subscribers, so run the trigger test to see what your account actually sends.
5

New Unsubscribe

Instant trigger

In Zapier“Triggers when a subscriber unsubscribes from your emails.”

Kicks in when a subscriber opts out of your emails. The Zap receives that person's details, so other tools can stop treating them as a reachable contact.

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 contacts also live in another tool that sends messages, and an opt-out in Mailrith should be reflected there too.
Watch out
only opt-outs that happen after the Zap is published come through; earlier ones stay where they are.
6

New Subscriber Bounce

Instant trigger

In Zapier“Triggers when a subscriber is marked as bounced.”

Reacts when Mailrith marks a subscriber as bounced, meaning mail to that address did not get through. The address and its subscriber record are passed to the next steps.

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 flag a contact in another system so somebody checks the address or asks the person for a new one.
Watch out
only bounces marked after the Zap is published come through, so addresses that bounced earlier have to be handled by hand.
7

New Subscriber Complaint

Instant trigger

In Zapier“Triggers when a subscriber is marked as complained.”

Goes off when a subscriber is marked as having complained about your emails. It is a different signal from an unsubscribe, and it deserves its own Zap.

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 alert whoever looks after the list, or to tag the contact in another tool so no other campaign reaches them.
Watch out
sending that person anything from a later step of the same Zap defeats the purpose; keep the actions internal.
8

Updated Subscriber

Instant trigger

In Zapier“Triggers when a subscriber profile, status, tags, sequences, or custom fields change.”

Watches changes on existing people: their profile, their status, their tags, their sequences or their custom fields. Any of those edits sends the subscriber to Zapier.

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 keep a copy of the list in sync elsewhere, when one record per person needs to follow Mailrith.
Watch out
it is the broadest trigger for changes, so to be safe let this Zap write outside Mailrith; a Zap that writes where its own trigger watches can loop.
9

New Tag Added to Subscriber

Instant trigger

In Zapier“Triggers when a specific tag is added to a subscriber.”

Turns one tag into a starting signal: the Zap runs whenever that tag lands on a subscriber, by hand in Mailrith or through another automation.

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 tagging someone means a job should follow, such as passing them to a colleague or enrolling them somewhere else.
Watch out
the tag is required and must already exist in Mailrith, so create it there before you pick it in the editor.
10

New Tag Removed From Subscriber

Instant trigger

In Zapier“Triggers when a specific tag is removed from a subscriber.”

The mirror image of the previous one: the Zap starts when a chosen tag is taken off a subscriber, so the end of a status can be acted on 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
to undo what the tag set up elsewhere, for example clearing a flag in your spreadsheet when the tag disappears.
Watch out
one tag per Zap, chosen from the list, and it is required, so it has to exist in Mailrith first.
Actions

Mailrith actions

Mailrith 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 Subscriber to Form

Action

In Zapier“Subscribe someone to a specific form.”

Subscribes an email to a chosen Mailrith form, just as if the person had filled it in.

When to use it
when sign-ups collected outside Mailrith should follow the same path as that form's own entries.
Watch out
both the form and the email are required, and the form must exist in Mailrith before you can pick it.
2

Add Subscriber to Sequence

Action

In Zapier“Add an existing subscriber to a specific sequence.”

Enrolls someone already on your list in the sequence you choose.

When to use it
right after a sign-up or a tag, to start the series of emails that matches it.
Watch out
it expects an existing subscriber, so for a new contact run Create Subscriber or a form step before it, in the same Zap.
3

Add Tag to Subscriber

Action

In Zapier“Add a subscriber to a specific tag.”

Puts a chosen tag on a subscriber, identified by email, so you can segment them later in Mailrith.

When to use it
to label people according to what they did in another tool.
Watch out
both the tag and the email are required, and the tag list only shows tags that already exist.
4

API Request (Beta)

Action

In Zapier“Make a raw API request that uses this integration's authentication.”

The advanced option: it sends a raw request to Mailrith using the connection you already set up, for whatever the other actions do not cover.

When to use it
only when you know which Mailrith address and method to call, such as /v1/subscribers.
Watch out
method, relative path and the stop-on-error choice are all required, and it is marked beta.
5

Create Subscriber

Action

In Zapier“Create a subscriber. If the email already exists, this action returns an error.”

Adds a brand new person to your Mailrith list from an email address the Zap carries.

When to use it
when contacts gathered in another tool should join the list.
Watch out
if the address is already on the list, the step returns an error; put Find Subscriber in front and a filter after it when duplicates are likely.
6

Remove Subscriber From Sequence

Action

In Zapier“Remove an existing subscriber from a selected sequence by email.”

Takes a subscriber out of one sequence, found by their email address.

When to use it
when an event elsewhere means the series no longer fits, so the remaining emails should stop.
Watch out
the email has to come from a previous step and belong to an existing subscriber; a typed address that is not on the list will not work.
7

Remove Tag From Subscriber

Action

In Zapier“Remove a specific tag from an existing subscriber by email.”

Strips one tag off an existing subscriber, matched on the email you map.

When to use it
when a status ends elsewhere and the label in Mailrith should end with it.
Watch out
map the email from an earlier step rather than typing it; it has to belong to someone already on the list.
8

Update Subscriber

Action

In Zapier“Update an existing subscriber by subscriber ID.”

Changes the details of a subscriber who is already on the list, picked by their subscriber record rather than by email.

When to use it
when another tool holds fresher information about a person and Mailrith should follow.
Watch out
the subscriber is required, so place Find Subscriber before it and map the subscriber it returns.
Searches

The Mailrith search

1 search step looks for data that already exists in Mailrith, so a later step can use it.

A search step does not change anything: it looks a subscriber up and hands the result to the next steps. In the action list, it sits under the SEARCH heading at the bottom of Action event. Three settings decide what happens next.

1

Find Subscriber

Search

In Zapier“Finds a subscriber by exact email address.”

Looks a person up in Mailrith by email address, and only an exact match counts.

When to use it
in front of Update Subscriber, which needs a subscriber record, or before Create Subscriber to avoid an error on a known address.
Watch out
a stray space or a different spelling of the address returns nothing, and by default the Zap then stops.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nobody stops the Zap there and the dependent steps are skipped. Switched on, the Zap goes on without a result.
  2. Create X if it doesn't exist yet?
    Ticking this box turns a search into a find-or-create. Mailrith offers no such variant on Find Subscriber, so the box does not apply here.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on.
When it breaks

When a Mailrith Zap breaks

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

  • Create Subscriber on a known address

    Create Subscriber stops with an error when the email is already on the list. Run Find Subscriber first and let a filter decide whether to create.

  • A Zap that writes where it watches

    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.

  • A form or tag you cannot pick

    Zapier's lists only show what already exists in Mailrith. A form, landing page, sequence or tag not created yet cannot be selected in the step.

  • Past subscribers are not picked up

    A Zap only reacts to what happens after it is switched on. People already on the list, past bounces or past opt-outs never go through it.

  • A bulk import gets held back

    When a large import suddenly fires many events at once, Zapier's flood protection can hold those runs back instead of passing them all on.

  • Find Subscriber finds nobody

    The search wants the exact address. With the default setting, a miss stops the Zap and every step depending on it is skipped.
Need help

Need help automating Mailrith with Zapier?

A person reads every message.

FAQ

Mailrith Zapier integration: common questions

01Is the Mailrith Zapier integration free?
Yes. Mailrith 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. New Form Subscriber followed by Add Subscriber to Sequence fits that limit. Add a filter, Find Subscriber or a second action and the Zap becomes multi-step, which needs a paid plan. The trigger itself never uses a task, however often it fires.
02How many tasks does a Mailrith Zap use?
One per action that succeeds, and none for the trigger. A Zap that fires on a new subscriber, tags them and enrolls them in a sequence uses two tasks per person. An action that fails is not counted. Looking up new data costs nothing either, though a few apps and actions take more than one task, so check your history after the first runs. The real risk is a loop: a Zap that writes where its own trigger watches can keep restarting itself, and every turn spends tasks.
03Are Mailrith triggers real time in Zapier?
Yes, all ten are instant. Mailrith calls Zapier as soon as the event happens, whether that is a sign-up, a bounce or a tag change, and the Zap starts at once. The interval grid of the plans (15 minutes on Free, 2 on Professional, 1 on Team and Enterprise) concerns polling triggers only, so it does not slow these down. In the editor, a lightning bolt on the trigger confirms it.
04What does it take to connect Mailrith to Zapier?
A Mailrith account, and the forms, landing pages, sequences and tags you plan to use already created in it. In Zapier, open Apps, click + Add connection, search for Mailrith, confirm with Add connection, then sign in in the tab that opens and grant access. Many steps ask you to pick one of those items from a list, and Zapier can only show what already exists in your account. The connection is then reused by every Mailrith step.
05Why does Create Subscriber fail on some contacts?
Because those addresses are already on your Mailrith list: Create Subscriber returns an error when the email exists. The step is not counted as a task, but the rest of the Zap does not run for that person. Put Find Subscriber in front, add a filter that lets the creation go on only when nobody was found, and switch on the setting that lets the search succeed with no result. That makes the Zap multi-step.
06What if the Mailrith operation you need is not listed?
First check the advanced action, API Request (Beta). It reuses your Mailrith connection to send a request the other actions do not cover, provided you know the path to call. Outside that, the integration covers creating, tagging, updating and moving subscribers between forms and sequences, plus one search by email. It offers no action that deletes a subscriber, and a Zap never processes what happened before it was published, so older records need another route.
07Zapier, Make or n8n for Mailrith?
Compare on three criteria. Coverage: on Zapier, Mailrith brings 10 instant triggers, 8 actions and 1 search, with an advanced request action for the rest. Cost: Zapier bills each successful action, so a Zap with a search, a filter and two actions is multi-step and paid. Logic: a flow that needs many branches or loops grows complex in any tool. Check how the other platforms count runs for the same flow before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations