Resources · Zapier integration

MailUp Zapier integrationAutomate MailUp with Zapier.

The MailUp Zapier integration gives you 7 triggers and 7 actions, with 0 searches. All seven triggers are polling, every one of them watches a single list, and the actions cover recipients, groups, messages and sends. Here is what each does and where it trips.

See the 14 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MailUp Zapier integration actually does

MailUp is an email delivery tool built around lists: each list holds its own recipients, groups, messages and templates. Connecting it to Zapier lets changes on a list start work in other tools, and lets other tools add people, build groups, write messages and fire sends inside MailUp.

An unsubscribe becomes a row. New Recipient Unsubscribed picks up people who left a list. Send them to a spreadsheet and the rest of your team stops contacting someone who asked to be left alone.

A new subscriber lands in a group. New Recipient Subscribed followed by Add Recipient to Group sorts fresh sign-ups into the group you mail to first, without anyone opening the console.

A sent message leaves a trace. New Email Sent watches one message on one list and reports when it has gone out, which is handy when another tool waits for the send before doing its part.

What Zapier does not do here: no trigger is instant, so every event waits for Zapier's next check. There is no search, so a Zap cannot look up a recipient or a group by itself. And nothing edits or deletes a message, a template or a group once it exists. If your Zaps start piling up, the Zapier agency can take them over and keep them running.

Vocabulary

Zapier words, in plain English

Eight words carry the whole page. Each one in a sentence.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, here a change on one MailUp list.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like adding a recipient.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling trigger
A trigger Zapier checks on a timer. It asks MailUp for new items at a fixed interval and keeps only what it has not seen yet.
Instant trigger
A trigger the app reports itself, the moment the event happens. MailUp has none on Zapier, which shapes the whole page.
Filter
A step that lets the Zap go on only when what arrived meets a condition you set, and stops it quietly otherwise.
Connection
Your MailUp account linked to Zapier once, then reused by every MailUp step in every Zap you build.
Cost

What a MailUp Zap costs you

MailUp is not a premium app, so it works on the free plan. The bill is counted in tasks, and only on actions.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • Trigger cost0 tasks
  • Instant triggersNone, all 7 are polling

The trigger never costs a task, and neither do Zapier's checks on your lists, however often they run. Each action that succeeds counts once, so a Zap with three actions burns three times what a one-action Zap does. An action that fails is not counted. The free plan gives you 100 tasks a month and Zaps of two steps only: one trigger, one action. A filter or a second action turns it into a multi-step Zap, which needs a paid plan. Since all seven MailUp triggers are polling, the interval grid below sets how long a new subscriber or an unsubscribe waits before your Zap sees it.

Connect

Connect your MailUp account

  1. 01

    Open your apps

    In Zapier, go to the Apps page of your account. You need a MailUp account first, plus access to any list you did not create yourself but want the Zap to read or write.

  2. 02

    Add the connection

    Click + Add connection, type MailUp in the dialog and pick it. Then click Add connection in that same dialog, which opens MailUp in a separate browser tab for the sign-in.

  3. 03

    Sign in and allow access

    In the new tab, sign in to MailUp and grant Zapier access to the account. The connection now appears in your list, and every MailUp trigger and action can reuse it.

First Zap

Your first MailUp Zap: log every unsubscribe

GoalEach time a recipient unsubscribes from your MailUp list and matches the condition you choose, add a row to your spreadsheet so nobody contacts them by mistake.

  1. 01

    Pick the trigger

    Create a Zap, choose MailUp and New Recipient Unsubscribed as the event, then select your MailUp connection and the list to watch.

  2. 02

    Test the trigger

    Click test. Zapier brings back the three most recent unsubscribes on that list, so you map fields on a real recipient rather than a placeholder.

  3. 03

    Add the filter

    From the plus icon, add a Filter step and set the field to look at, the rule and the value. A text rule only works on text, so match the rule to the field.

  4. 04

    Add the spreadsheet

    Add your spreadsheet as the next step with the event that adds a row, then drag the MailUp fields into the columns you want filled.

  5. 05

    Test, then publish

    Run the action test, check the row, then hit Publish. With its filter this Zap has three steps, so it needs a paid plan.

Triggers

MailUp triggers

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

1

New Email Sent

Polling trigger

In Zapier“The specified email message on the list has been sent.”

Watches one specific message on one list and starts the Zap once that message has been sent. You point it at the message in advance, so it reports on a send you are expecting.

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
when another tool should only act after a particular newsletter has gone out, such as logging the send in a shared sheet.
Watch out
both the list and the message are required, so the message must already exist in MailUp before you set the trigger.
2

New Email Message Template

Polling trigger

In Zapier“A new email message template was created in the list. MailUp is a multi-list environment and templates are list-specific.”

Fires when someone creates a new message template in the list you choose. Templates belong to one list in MailUp, so a template made elsewhere never shows up here.

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
when a new template should be announced to whoever reviews layouts before they go into use.
Watch out
one Zap watches one list; if you keep templates on several lists, each list needs its own Zap.
3

New Email Message in List

Polling trigger

In Zapier“A new email message was created in the list. MailUp is a multi-list environment and messages are list-specific.”

Runs each time a new email message is created in the list you pick. It reacts to the message being created, not to it being sent.

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
when a fresh message should land in a review tracker so someone checks it before it is scheduled.
Watch out
a Zap that writes where its own trigger watches can loop, so be careful before adding Create New Email Message on that same list.
4

New Group

Polling trigger

In Zapier“New group added to the specified list. MailUp is a multi-list environment and groups are list-specific.”

Kicks in when a new group is added to the list you watch. Groups in MailUp live inside a list, so the trigger only sees groups of that one list.

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
when a new group should be recorded somewhere your team can see it, for instance a sheet that maps groups to their purpose.
Watch out
if the same Zap also creates groups on that list with Create New Group, it may set itself off in a loop.
5

New Recipient Pending

Polling trigger

In Zapier“There is a new pending recipient in the specified list. MailUp is a multi-list environment. Pending recipients are those that have not confirmed their subscription to the specified list.”

Picks up people who signed up to a list but have not confirmed their subscription yet. MailUp calls them pending, and they sit apart from your confirmed subscribers.

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
when you want to follow up on unconfirmed sign-ups, for example by sending them a message you prepared in MailUp.
Watch out
the list is required, and the trigger only sees pending sign-ups on that one list.
6

New Recipient Subscribed

Polling trigger

In Zapier“There is a new subscriber in the specified list. MailUp is a multi-list environment.”

Goes off when a new subscriber joins the list you choose. Only subscribers of that one list set it off.

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
when each new subscriber should be copied into another tool, or sorted into a group of the same list.
Watch out
if the same Zap writes into the list it watches, with Add Recipient to List for instance, it risks setting itself off in a loop.
7

New Recipient Unsubscribed

Polling trigger

In Zapier“A recipient unsubscribed from the specified list. MailUp is a multi-list environment.”

Reacts when a recipient leaves the list you are watching. It is the signal other tools need so they stop writing to someone who opted out.

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
when an unsubscribe in MailUp should be mirrored in your sheet or your contact tool.
Watch out
people who left before the Zap was published are not picked up, so clean the history separately.
Actions

MailUp actions

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

1

Create New Email Message

Action

In Zapier“Create a new email message on the specified list.”

Writes a new email message into a list, with its subject and content, ready to be sent later from MailUp or by another step.

When to use it
when the text of a message is prepared in another tool and should arrive in MailUp without copy and paste.
Watch out
the target list is an integer, the list number from the console, not its name.
2

Add Recipient to Group

Action

In Zapier“Add recipient to the specified group on the list.”

Places a recipient in a given group of a list, using their email address. The list and the group are both required.

When to use it
when a new subscriber should be sorted into a segment right after joining, so the right messages reach them.
Watch out
the group has to exist already, so create it first if needed.
3

Create New Group

Action

In Zapier“Add a new group to the specified list. MailUp is a multi-list environment.”

Adds a group to a list under the name you give it. A setting decides whether the group can be deleted later from the console; it is on by default.

When to use it
when a new segment appears elsewhere and needs a matching group in MailUp.
Watch out
turn deletable off for a group nobody should remove by accident.
4

Add Recipient to List

Action

In Zapier“Adds a new recipient to the specified list as a subscriber.”

Puts an email address into a list as a subscriber. It needs only the list number and the address, which makes it the simplest way to feed MailUp from another tool.

When to use it
when someone signs up through a tool outside MailUp and should start receiving your list's emails.
Watch out
the list is identified by its number, found in the Codes Table of the console.
5

New Send Email

Action

In Zapier“Sends the specified message (previously created in MailUp in the specified List) to the email address specified.”

Sends one message, already created in MailUp on a given list, to a single email address. The Zap picks the source list, the message and the recipient.

When to use it
when one person should get a prepared message as soon as the Zap runs, like a reminder to a pending sign-up.
Watch out
the action sends, it does not write; build the message in MailUp first.
6

Send Message to Group

Action

In Zapier“Send a message to a predefined group in the specified list.”

Fires an existing message at a whole group defined in a list. You choose the message, the list and the group.

When to use it
when an event elsewhere should trigger a send to a full segment instead of one address.
Watch out
every run sends the message to everyone in the group, so a misfiring trigger means repeated sends.
7

Remove Recipient From List

Action

In Zapier“This method unsubscribe the given recipient from the specified list.”

Unsubscribes a recipient from the list you name. Both the recipient and the source list are required.

When to use it
when someone opts out in another tool and MailUp should stop mailing them too.
Watch out
it unsubscribes from one list only, so a person on several lists needs one step per list.
When it breaks

When a MailUp Zap breaks

Zapier attaches no help article to MailUp, so the traps below are the general ones. They weigh more on an app where every trigger works by polling.

Most failures here are not errors on screen but Zaps that loop, wait or miss history. When one misbehaves, the Zapier troubleshooting guide is the first place to look.

  • History is never picked up

    A Zap only reacts to what happens after you switch it on. Subscribers and unsubscribes from before stay put, and moving that backlog is a separate job.

  • The Zap that restarts itself

    A Zap that writes into the place its own trigger watches, such as the list it monitors, can set itself off again and again and burn tasks fast.

  • A big import gets held back

    After a bulk import of recipients, a trigger can suddenly return a huge batch. Zapier's flood protection may hold that batch back instead of running it.

  • No double runs

    Zapier remembers what it has already seen on each polling trigger, so the same subscriber or message does not start the Zap twice.
Need help

Need help automating MailUp with Zapier?

A person reads every message.

FAQ

MailUp Zapier integration: questions people ask

01Is the MailUp Zapier integration free?
Yes, it runs on the free Zapier plan, because MailUp is not a premium app. The free plan gives you 100 tasks a month and as many Zaps as you like, each limited to two steps: one trigger and one action. A Zap that logs every unsubscribe in a sheet fits. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. You also need your own MailUp account; Zapier only links the two.
02How many Zapier tasks does a MailUp Zap use?
One task per action that succeeds, nothing for the trigger. A Zap that copies each new subscriber into a group costs one task per subscriber. A Zap with two actions, say adding the person to a group and sending them a message, costs two each run. Zapier checking your lists costs nothing, and an action that fails is not counted. Watch Send Message to Group: it is one task, but a trigger that fires too often means many sends.
03Do MailUp triggers work in real time?
No. All seven MailUp triggers are polling: Zapier asks MailUp for new items at a fixed interval. That interval depends on your plan, every 15 minutes on Free, 2 on Professional and 1 on Team or Enterprise. So on the free plan, a new subscriber can wait up to that interval before your Zap reacts. On paid plans you can also change how often a trigger checks, and run a check by hand from the editor when you are testing.
04What does it take to connect MailUp to Zapier?
A MailUp account and a Zapier account. From the Apps page in Zapier, click + Add connection, search for MailUp, click Add connection, sign in on the tab that opens and grant access. Every MailUp step then reuses that connection. You also need access to the lists the Zap will touch. Keep the list number at hand: triggers and actions ask for it, and MailUp shows it in the Codes Table of the Developer's Corner.
05Why does a MailUp Zap ask for a number instead of a list name?
Because MailUp identifies lists by a number. Several fields, such as the target list of Create New Email Message or Add Recipient to List, expect that integer rather than the name you see on screen. You find it in several places of the MailUp admin console, including the Codes Table in the Developer's Corner. Groups appear in that same Codes Table. Note both numbers before you build, so each field gets what it expects.
06What if the MailUp operation you want is not there?
Short answer: Zapier cannot add it for you. MailUp publishes fourteen ready operations, seven triggers and seven actions, and none of them looks up a recipient, edits a message or deletes a group. So a Zap can watch lists and write into them, not search or tidy up. Open the event dropdown in the editor to confirm, since it shows what is live today. When a project depends on the missing step, plan it by hand in the MailUp console, or price it on another automation tool.
07Zapier, Make or n8n for MailUp?
Choose on criteria, not on a ranking. Speed: every MailUp trigger on Zapier is polling, so on the free plan an event can wait up to 15 minutes. Coverage: fourteen ready operations on lists, groups and sends, with nothing to build. Cost: each successful action is billed, so a Zap that both adds and mails a person counts double. Make and n8n bill and build their own way, and whether each ships a MailUp module is worth checking first. A team that needs minute-level reaction should look closely at the plan grid.
Same platform

Other docs you might need on this stack.

Browse all integrations