Resources · Zapier integration

Maileon Zapier integrationAutomate Maileon with Zapier.

The Maileon Zapier integration gives you 3 triggers, 4 actions and 0 searches. All three triggers are instant. Enough to feed contacts into Maileon and to react to bounces, confirmations and unsubscribes elsewhere, if you know what each step costs.

See the 7 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Maileon Zapier integration does for you

The Maileon Zapier integration links your Maileon account with your other apps through Zapier. You build a Zap (the automation you set up on Zapier: one trigger, then one or more actions), and it passes what happens in one tool to the other, every time, without anyone exporting a list.

Three results come out of it. A bounce log your team actually reads: Bounce fires when an email bounces, and the Zap writes the address into a sheet or flags it in your CRM. Contacts that arrive with the right permission: Create Contact adds an address from a form or a shop and can send the double opt-in email on the way. Opt-outs respected everywhere: Unsubscription tells your other tools the moment someone leaves, and Unsubscribe Contact does the reverse when the opt-out is recorded elsewhere first.

Now what Zapier does not do here. There is no search step, so a Zap cannot look up a Maileon contact before acting on it. There is no action to send a campaign or build a mailing: those stay inside Maileon. And Send Transaction only sets a permission level on contacts it creates, never on existing ones.

The same app has its own page for another platform: see our Maileon Make integration page. To weigh the platforms side by side, see Make vs Zapier.

Vocabulary

Zapier vocabulary in one minute

Seven words come back across the page. Here they are once, in plain terms.

Zap
The automation itself: one trigger at the top, then one or more actions that run each time that trigger event happens.
Trigger
The event that starts the Zap, here a bounce, a confirmation or an unsubscribe in Maileon. Once the Zap is on, Zapier waits.
Action
What the Zap does once started: the step that writes, sends or moves something for you, such as creating a contact.
Task
The unit Zapier bills: one action that completes successfully. Your plan's number is a count of those, nothing more.
Polling vs instant
Polling: Zapier asks the app for new items at a fixed interval. Instant: the app tells Zapier the moment the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app so later steps can reuse it. Maileon offers none on Zapier.
Cost

What a Maileon Zap costs you

Maileon is not a premium app, so it runs on the free plan. The bill follows actions, never the trigger.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • BilledEach successful action
  • Triggers3 instant, no waiting interval

The trigger costs nothing. Each action that succeeds counts once, so a Zap with three actions uses three times more than a Zap with one. A failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps, one trigger and one action. A filter or a second action makes it multi-step, and that needs a paid plan. The interval grid below is the general rule for polling triggers; it does not apply to Maileon, whose three triggers are all instant.

Connect

Connect your Maileon account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Maileon account linked once, then reused by every step that needs it.

  2. 02

    Pick Maileon

    Type Maileon in the search box of the dialog, select it, then click Add connection. You need a Maileon account that already exists, in your name, before you begin.

  3. 03

    Sign in and allow access

    A tab opens on Maileon. Sign in, then grant Zapier access to the account. If the Zap will touch contacts you do not own yourself, check that you have read or write access on them first.

First Zap

Your first Zap: log every Maileon bounce in a sheet

GoalEach time an email bounces in Maileon and passes a condition you choose, a row lands in your spreadsheet with the address, so whoever cleans the list sees it.

  1. 01

    Create the Zap

    Create a new Zap. The editor opens with an empty trigger slot at the top and an action slot underneath. Give it a name you will recognise.

  2. 02

    Set the trigger

    Pick Maileon, then the event Bounce, then your Maileon connection. The editor shows a lightning bolt, the sign of an instant trigger.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent bounces of the account, so you map from a real address and not an empty sample.

  4. 04

    Add the filter and the sheet

    Click the plus icon, pick Filter and fill its three boxes: field, rule, value. Then add your spreadsheet's new-row action and map the email. The filter makes the Zap multi-step, so it needs a paid plan.

  5. 05

    Test, then publish

    Test the action, open the sheet to check the row arrived with the right address, then click Publish to switch the Zap on.

Triggers

Maileon triggers on Zapier

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

1

Bounce

Instant trigger

In Zapier“Triggers when an email has bounced.”

Starts the Zap when an email sent from Maileon comes back undelivered. You get the bounce details as fields, starting with the address, ready for the next step.

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 bounced address should be flagged in your CRM or logged in a sheet, so nobody keeps writing to an address that bounced from another tool.
Watch out
bounces that happened before you published the Zap are never sent to it, so an existing backlog needs a separate clean-up.
2

Double Optin Confirmation

Instant trigger

In Zapier“Triggers when a user confirms a double optin email.”

Fires once a person clicks the confirmation link of a Maileon double opt-in email. It marks the moment their consent becomes complete.

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 only confirmed people should reach your CRM or a welcome flow in another tool, and unconfirmed sign-ups should wait.
Watch out
it fires on the confirmation of a double opt-in email; if your contacts come in through Create Contact, tick Send Double-Optin email so there is one to confirm.
3

Unsubscription

Instant trigger

In Zapier“Triggers when a contact is unsubscribed in Maileon.”

Reacts when a contact switches to unsubscribed in Maileon. Your Zap receives who left, ready to pass on to the tools that also write to them.

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 other tools that write to the same people must respect the opt-out, such as your CRM or a second email tool.
Watch out
avoid ending the same Zap with Unsubscribe Contact; the action writes where the trigger watches, and the Zap can set itself off again.
Actions

Maileon actions on Zapier

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

1

Create Contact

Action

In Zapier“Create a contact in Maileon and send a double optin email (optional)”

Adds a new contact to Maileon from data the Zap carries, and can send them the double opt-in email at the same time.

When to use it
when sign-ups collected in a form or a shop should land in Maileon with the right starting permission.
Watch out
Email and the permission level are required; the level you pick is only the starting one, and it changes once the person confirms the double opt-in.
2

Send Transaction

Action

In Zapier“Send a Transaction to Maileon”

Passes a transaction for an email address to Maileon, so your Maileon setup can act on it.

When to use it
when an event recorded in another tool, tied to one person, should reach Maileon right after it happens.
Watch out
Email and Permission level are required, and the permission level only applies to contacts this step creates; existing contacts keep theirs.
3

Unsubscribe Contact

Action

In Zapier“Unsubscribe a contact in Maileon”

Switches a Maileon contact to unsubscribed, using their email address.

When to use it
when the opt-out is recorded somewhere else first, a CRM or a support tool for instance, and Maileon must stop writing to that person.
Watch out
Email is required; inside a Zap started by Unsubscription, this step writes where the trigger watches and can loop.
4

Update Contact Preference

Action

In Zapier“Update contact preference”

Changes the preferences stored on a Maileon contact, found through their email address.

When to use it
when a person picks their preferences in another tool and Maileon should follow without a manual edit.
Watch out
Email is required, so map it from the trigger; a typo in that field means the update reaches nobody.
When it breaks

When a Maileon Zap breaks

Zapier ties no help article to Maileon, so the traps below are the ones every Zap shares. With instant triggers, they show up fast.

Most surprises come from what a Zap does not do rather than from an error message. Keep these three in mind before you publish, and see Zapier troubleshooting when a run goes wrong.

  • Old bounces and opt-outs are not picked up

    A Zap only reacts to what happens after you switch it on. Bounces, confirmations and unsubscribes from before stay out; moving them is a separate job.

  • A Zap that sets itself off

    A Zap that writes where its own trigger watches can restart itself. Unsubscription followed by Unsubscribe Contact is the case to avoid on this app.

  • A big send gets held back

    If a mailing suddenly produces a huge batch of bounces at once, Zapier's flood protection can hold those runs back instead of firing them all.
Need help

Need help automating Maileon with Zapier?

A person reads every message.

FAQ

Maileon and Zapier: frequent questions

01Is the Maileon Zapier integration free?
On the Zapier side, yes: Maileon is not a premium app, so it runs on the free plan. That plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps, one trigger and one action. Add a filter or a second action and it becomes multi-step, which needs a paid plan. Even there, all three Maileon triggers stay instant, so a two-step Zap reacts the moment a bounce, a confirmation or an unsubscribe happens.
02How many tasks does a Maileon Zap use?
One task per action that succeeds, nothing for the trigger. A Zap that logs every bounce in a sheet costs one task per bounce. A Zap with three actions costs three per run. Failed actions are not billed. So the figure to watch is how many events Maileon produces, bounces in particular after a large mailing, multiplied by the number of actions in the Zap. A Zap that logs the bounce in a sheet and also notifies the team costs two.
03Is Maileon on Zapier real time?
Yes, for its three triggers. Bounce, Double Optin Confirmation and Unsubscription are all instant: Maileon tells Zapier the moment the event happens and the Zap starts right away. The plan's checking interval, 15 minutes on Free, does not apply to them. In the editor, a Zap built on one of them shows a lightning bolt. That makes Maileon one of the apps where a free plan loses nothing on speed.
04What does it take to connect Maileon to Zapier?
A Maileon account that already exists and a Zapier account. From the Apps page, click + Add connection, search for Maileon, sign in on the tab that opens and grant access. If the Zap must touch contacts you do not own yourself, you also need read or write access on them. Before you build, decide which permission level new contacts should get, since Create Contact and Send Transaction both require one.
05Why does a Maileon contact's permission change after creation?
Because the level set in Create Contact is only the starting one. When the step also sends the double opt-in email, Maileon switches the contact to DOI or DOI+ once they use the confirmation link. So pick the starting level for the moment before confirmation, not for the final state. To act on the confirmed state, start a separate Zap from Double Optin Confirmation, which fires when that link is used. Send Transaction works differently: its permission level only applies to contacts the step creates.
06What if the Maileon operation you need is not on Zapier?
Then the integration does not cover it. With three triggers and four actions, the gaps are clear: no search, no campaign send, no way to delete a contact or read their data back. Often the step can be done on the other side of the Zap, in the tool that holds the data, before it reaches Maileon. Otherwise, keep that step manual and automate only what the seven operations allow.
07Zapier, Make or n8n for Maileon?
There is no single winner, only criteria. Coverage: on Zapier, Maileon has seven operations, with no search, so check whether Make or n8n covers the steps you need; the Make page linked above lists what Make offers. Speed: all three triggers are instant on every Zapier plan. Cost: Zapier bills each successful action and never the trigger. Free plan: two-step Zaps cost nothing, while a filter or a second action needs a paid plan. Weigh those points against your own volume.
Same platform

Other docs you might need on this stack.

Browse all integrations