- Home
- Resources
- Integrations
- MailWizz
MailWizz Zapier integrationAutomate MailWizz with Zapier.
The MailWizz Zapier integration gives you 2 triggers, 2 actions and 2 searches. Both triggers are polling and watch one list each, the actions add or unsubscribe a subscriber, and the searches find lists and subscribers. Here is what each does and where it trips.
Verified Trustpilot reviews · AI, automation & growth agency
What the MailWizz Zapier integration actually does
MailWizz is email marketing software built around lists of subscribers. Connecting it to Zapier lets new subscribers and unsubscribes on a list start work in other tools, and lets those tools add a subscriber, unsubscribe one, or look up a list or a person in MailWizz before acting.
One unsubscribe, honored everywhere. New Unubscriber spots someone leaving a list. Follow it with Find Subscriber by Email on a second list and Unsubscribe Subscriber, and the person leaves that list too, without anyone checking two lists by hand.
A new subscriber copied out. New Subscriber picks up each person added to a list, and a spreadsheet step keeps a running record your team can read without logging in to MailWizz.
A subscriber added from elsewhere. Create Subscriber puts a new person into the list you name, so sign-ups gathered in another tool reach MailWizz on their own, one subscriber per run.
What Zapier does not do here: no trigger is instant, so every event waits for Zapier's next check. Nothing deletes a subscriber or edits a list, and the unsubscribe action needs the subscriber's own ID: if the step before does not carry it, you need a search first. To weigh this setup against other tools, read Zapier alternatives.
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 subscriber joining or leaving a list.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like adding a subscriber.
- 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 MailWizz for new items at a fixed interval and keeps only what it has not seen.
- Instant trigger
- A trigger the app reports itself, the moment the event happens. MailWizz has none on Zapier.
- Filter
- A step that lets the Zap go on only when what arrived meets a condition you set, and stops it quietly otherwise.
- Search step
- A step that looks up something already in MailWizz, like a subscriber, so the steps after it can use what it found.
What a MailWizz Zap costs you
MailWizz 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
- Search, filter or second actionMulti-step Zap, paid plan
The trigger never costs a task, and neither do Zapier's checks on your lists. 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. Add a search, a filter or a second action and you have a multi-step Zap, which needs a paid plan. That matters here: unsubscribing someone whose ID you do not have takes a search first. Both MailWizz triggers are polling, so the interval grid below sets how long a new subscriber waits before your Zap sees it.
Connect your MailWizz account
- 01
Open your apps
In Zapier, go to the Apps page of your account. You need a MailWizz account first, plus access to any list you did not create yourself but want the Zap to read or change.
- 02
Add the connection
Click + Add connection, type MailWizz in the dialog and pick it. Then click Add connection in that same dialog, which opens MailWizz in a separate browser tab.
- 03
Sign in and allow access
In the new tab, sign in to MailWizz and grant Zapier access to the account. The connection now shows in your list, and every MailWizz trigger, action and search can reuse it.
Your first MailWizz Zap: unsubscribe from a second list
GoalWhen someone unsubscribes from one MailWizz list, find the same email address on a second list and unsubscribe them there too.
- 01
Pick the trigger
Create a Zap, choose MailWizz and New Unubscriber as the event, then select your connection and the List Unique ID of the list to watch.
- 02
Test the trigger
Click test. Zapier brings back the three most recent unsubscribes from that list, so you map fields on a real subscriber rather than a placeholder.
- 03
Add the search
Add MailWizz, pick Find Subscriber by Email, give the ID of the second list and map the email from the trigger. Test it to see the subscriber it finds.
- 04
Add the action
Add Unsubscribe Subscriber, give the second list's ID again and fill the Subscriber Unique ID from what the search returned in its test.
- 05
Test, then publish
Run the action test on a test address, check the list in MailWizz, then hit Publish. With a search, this is a multi-step Zap on a paid plan.
MailWizz triggers
2 events start a Zap when something happens in MailWizz. Zapier checks for them at the interval your plan allows.
New Subscriber
Polling triggerIn Zapier“Triggers when new subscriber added to list.”
Starts the Zap each time a subscriber is added to the list you pick. Only additions to that one list set it off.
New Unubscriber
Polling triggerIn Zapier“Triggers when a subscriber unsubscribes from the list.”
Fires when a subscriber leaves the list you watch. In the editor, look for it under its exact name, New Unubscriber.
MailWizz actions
MailWizz gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Subscriber
ActionIn Zapier“Creates a new Subscriber”
Adds a new subscriber to the MailWizz list whose unique ID you give. It is the way in for people collected in another tool.
Unsubscribe Subscriber
ActionIn Zapier“Unsubscribe a Subscriber from a list.”
Unsubscribes one subscriber from one list. It needs both the List Unique ID and the Subscriber Unique ID, not just an email address.
MailWizz searches
2 search steps look for data that already exists in MailWizz, so a later step can use it.
A search step looks something up in MailWizz and passes it to the next steps. You find the two searches at the bottom of the action event list, under SEARCH. Whether a search wants the exact value or something close is decided by MailWizz, not by Zapier. Each search comes with three settings that decide what happens next.
Find Lists
SearchIn Zapier“Find Lists in your account.”
Looks up the lists in your MailWizz account and hands what it finds to the next steps of the Zap.
Find Subscriber by Email
SearchIn Zapier“Find a subscriber by email.”
Finds a subscriber on a given list from their email address, and hands what it found to the next steps. Both the list ID and the email are required.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this box turns a search into a find-or-create step. MailWizz exposes no such variant on Zapier, so this box does not apply here.
- 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 hand all of them on at once.
When a MailWizz Zap breaks
Zapier attaches no help article to MailWizz, so the traps below are the general ones, applied to an app with two polling triggers and two searches.
Most failures here are not error messages but Zaps that loop, stop on an empty search 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. People who joined or left a list before that 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 through tasks fast.A bulk import gets held back
After a bulk import into a list, a trigger can suddenly return a huge batch. Zapier's flood protection may hold that batch back.No double runs
Zapier remembers what it has already seen on each polling trigger, so the same subscriber does not start the Zap twice.
Need help automating MailWizz with Zapier?
A person reads every message.



