MailPion Zapier integrationAutomate MailPion with Zapier.
The MailPion Zapier integration gives you 2 triggers, 3 actions and 0 searches. Both triggers are checked by Zapier on a timer, so how fast a new subscriber or an unsubscribe shows up elsewhere depends on your plan: every 15 minutes on Free.
Verified Trustpilot reviews · AI, automation & growth agency
What the MailPion Zapier integration does for your lists
MailPion is an email marketing platform for sending targeted campaigns and managing contacts in one place. Linking it to Zapier means building a Zap: an automation with one starting event, the trigger, then one or more actions that run each time that event happens. MailPion can start the Zap or act on what another app sends.
Sign-ups from anywhere, in one list. Create Subscriber adds a person to a MailPion list chosen in the step. A form or another app can feed your audience without anyone retyping addresses.
Opt-outs respected everywhere. Unsubscribe Subscriber takes an email address off every MailPion list at once, while Unsubscribe Subscriber from List removes someone from a single list. When a person opts out in another tool, MailPion follows.
Your other tools kept informed. New Subscriber and New Unsubscriber pass each change on a list to a spreadsheet, a contact tool or a team channel, so nobody exports the list by hand.
What Zapier does not do here. There is no search step, so a Zap cannot look up a subscriber, or the subscriber UID that one of the actions needs. Nothing sends a campaign or edits a contact's details from Zapier. And neither trigger is instant: both wait for your plan's check. If you are comparing tools, see n8n vs Zapier and Make vs Zapier.
Zapier vocabulary, in plain words
Seven words come back on every Zapier screen. Here they are once, so the rest of the page reads easily.
- Zap
- The automation you build: one event that starts it, then the steps it carries out every single time that event happens.
- Trigger
- The event that starts the Zap, such as a new MailPion subscriber. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or updates something for you in an app.
- Task
- The unit Zapier bills. One task is one action that completed successfully, and your plan counts those.
- Polling vs instant
- Zapier checks a polling trigger on a timer set by your plan. An instant trigger is reported by the app itself. Both MailPion triggers are polling.
- Filter
- A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it otherwise.
- Connection
- Your MailPion account linked to Zapier once, then reused by every step of every Zap that touches MailPion.
What a MailPion Zap really costs
MailPion is not a premium app, so it runs on the free plan. The trigger never costs anything, and neither do Zapier's checks for new subscribers, however often they run.
- Premium appNo, available on Free
- Tasks on Free100 per month
- Cost of a trigger0 tasks
- Steps on Free2 (one trigger, one action)
Each action that goes through counts as one task, and a failed one is not counted. A Zap with two actions uses two tasks per run. The free plan gives 100 tasks a month and Zaps of two steps only: one trigger, one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The grid below sets how often Zapier checks both MailPion triggers on each plan. On paid plans the frequency can be changed, and a check can be run by hand from the editor.
Connect your MailPion account
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box: type MailPion and pick it from the results that appear.
- 02
Start the connection
Click Add connection. A new tab opens on MailPion. You need a MailPion account, plus access to any list you do not own yourself but want the Zap to touch.
- 03
Sign in and allow access
Sign in to MailPion in that tab, then grant Zapier access to the account. The connection now shows on your Apps page, and every MailPion step can reuse it.
Your first Zap: log every new subscriber
GoalEach new subscriber on a MailPion list gets a row in your spreadsheet when Zapier checks the list, only when the data meets your condition.
- 01
Create the Zap
Start a new Zap and pick MailPion as the app that starts it. Choose New Subscriber as the event, then select your MailPion connection.
- 02
Pick the list
Set the required List field to the list you want to follow. Only new subscribers on that list will start this Zap, so choose the one your forms feed.
- 03
Test the trigger
Run the test. Zapier brings back the three most recent items of the account, so you map columns on a real subscriber rather than a blank sample.
- 04
Add a filter if needed
Add a Filter from the plus icon and set its three boxes: field, rule, value. Only matching subscribers go on. A filter makes the Zap multi-step, so it needs a paid plan.
- 05
Add the action, test, publish
Add your spreadsheet and the step that adds a row, then map the subscriber's details. Test once, check the row, and click Publish to switch the Zap on.
MailPion triggers
2 events start a Zap when something happens in MailPion. Zapier checks for them at the interval your plan allows.
New Subscriber
Polling triggerIn Zapier“Triggers when a new subscriber created.”
Starts your Zap when a new subscriber appears on the MailPion list you picked, and passes their details to the following steps. Zapier spots the newcomer at its next check and keeps track of who it has already seen, so the same person never starts the Zap twice.
New Unsubscriber
Polling triggerIn Zapier“Triggers when a subscriber unsubscribe.”
Fires when a subscriber leaves the MailPion list you selected, and hands their details to the next steps. It is how your other tools learn that someone no longer wants your emails, so a spreadsheet or another sending tool can stop treating them as a subscriber.
MailPion actions
MailPion gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Subscriber
ActionIn Zapier“Create a new subscriber in a specific list.”
Adds a new subscriber to a specific MailPion list, so a person collected by another app joins your audience straight away.
Unsubscribe Subscriber from List
ActionIn Zapier“Unsubscribe a subscriber from a specific list.”
Removes one subscriber from one MailPion list and leaves them on any other list they belong to.
Unsubscribe Subscriber
ActionIn Zapier“Unsubscribe a subscriber from all lists in the system.”
Unsubscribes an email address from every list in your MailPion account in a single step, so the person stops hearing from you entirely.
When a MailPion Zap breaks
Zapier publishes no help article for MailPion and no app-specific limit. What goes wrong comes from how Zaps behave in general.
Four cases cover most surprises. When a Zap stops for a reason you cannot spot, Zapier troubleshooting is the place to start.
Old subscribers are not picked up
A Zap only reacts to what happens after you switch it on. People already on the list stay out of it; moving that backlog is a separate job.A Zap that feeds itself
New Subscriber on a list plus Create Subscriber on that same list makes the Zap fire again and again, burning through tasks.A bulk import held back
Import many contacts at once and the next check returns a huge batch. Zapier's flood protection can hold it back rather than run every item.No duplicates from polling
Zapier remembers which subscribers it has already seen on each check, so the same person never starts the Zap twice.
Need help automating MailPion with Zapier?
A person reads every message.
