Resources · Zapier integration

MailerLite Classic Zapier integrationAutomate MailerLite Classic with Zapier.

MailerLite Classic Zapier integration: 11 triggers, 4 actions and 0 searches. Every trigger is instant, the app is not premium, and the free plan is enough for a two-step Zap. Here is what each operation does, what it costs and where it breaks.

See the 15 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MailerLite Classic Zapier integration actually does

It links your MailerLite Classic account to Zapier so that something happening on your list (a new subscriber, a bounce, a finished automation) starts a Zap, the automation you build on Zapier: one event, then one or more steps that run each time. It can also add, move or unsubscribe people for you.

A clean record of list problems. Spam Complaint and Subscriber Bounced each start a Zap as soon as MailerLite Classic sees the event, so every complaint and every bounce can land as a row in the sheet your team already reads.

Unsubscribes that follow people everywhere. Subscriber Unsubscribed hands the address to the next step, and your other tools stop writing to someone who left. The reverse works too: Unsubscribe Subscriber applies an opt-out that happened outside MailerLite Classic.

New contacts filed in the right group. Create/Update Subscriber adds a person to a group by email address, or updates them if they already exist, so a sign-up captured in another app does not stay stuck there.

What Zapier does not do here: there is no search step, so a Zap cannot look up an existing subscriber before acting, and no action creates or sends a campaign. Campaign Sent only tells you a send happened. For anything outside the four actions, API Request (Beta) is the escape hatch, and it is a technical one. If you are still weighing tools, see our n8n vs Zapier comparison.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain terms.

Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, adds, moves or unsubscribes something on your behalf.
Task
The unit Zapier bills. One action that completes successfully is one task, and your plan is a count of those.
Instant trigger
A trigger the app reports itself: it calls Zapier the moment the event happens, so nothing waits for a scheduled check.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. MailerLite Classic has none.
Filter
A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it otherwise.
Connection
Your MailerLite Classic account linked to Zapier once, then reused by every step in every Zap that touches the app.
Cost

What it really costs

Zapier bills completed actions, not events. Whatever happens on the trigger side costs nothing until an action runs.

  • Free plan100 tasks per month
  • Premium appNo, available on the free plan
  • Cost of a trigger0 tasks
  • Free plan Zap size2 steps: one trigger, one action

Each action that goes through counts as one task; a failed one is not counted. A three-action Zap uses three times what a one-action Zap uses. MailerLite Classic is not a premium app, so the free plan (100 tasks a month) covers it, but only for two-step Zaps: one trigger, one action. Add a filter or a second action and you are building a multi-step Zap, which needs a paid plan. The interval grid below is the one Zapier publishes for polling triggers; it does not apply to this app, whose 11 triggers are all instant.

Connect

Connect your MailerLite Classic account

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an existing MailerLite Classic account first; Zapier links one, it does not open a new one.

  2. 02

    Pick MailerLite Classic

    Type the app name in the dialog, choose MailerLite Classic in the results, then click Add connection. This button is what opens the sign-in tab used in the next step.

  3. 03

    Sign in and grant access

    A new tab opens. Sign in to MailerLite Classic and allow Zapier to use the account. From then on, every Zap step that uses the app reuses this connection.

First Zap

Your first Zap: act on every spam complaint

GoalWhen a subscriber flags an email as spam, check the condition you care about, unsubscribe the address and log it in a sheet.

  1. 01

    Pick the trigger

    Create a Zap, choose MailerLite Classic as the app and Spam Complaint as the event, then select the connection you added earlier.

  2. 02

    Test it on real data

    Run the trigger test. Zapier brings back the three most recent items of the account, so you map the next steps on a real complaint rather than a blank form.

  3. 03

    Add the filter

    Click the plus icon, add Filter, then fill the field to look at, the rule and the value in Configure & test. Pick a text rule for text and a number rule for numbers.

  4. 04

    Unsubscribe, then log

    Add Unsubscribe Subscriber and map the email from the trigger. Then add your spreadsheet step and map the address into a new row.

  5. 05

    Test and publish

    Test each step and read what came back. Then click Publish. With a filter and two actions this is a multi-step Zap, so it needs a paid plan.

Triggers

MailerLite Classic triggers

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

1

Campaign Sent

Instant trigger

In Zapier“Triggers when a campaign is sent.”

Starts a Zap once a campaign leaves MailerLite Classic, which gives the rest of your stack a reliable signal that a send went out. It reports the send, nothing about opens or clicks.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
post a note in your team channel or add a line to a sending log every time a newsletter goes out.
Watch out
no action on this app creates or sends a campaign, so this trigger is the only campaign-related step you get.
2

New Subscriber

Instant trigger

In Zapier“Triggers when a new subscriber is created.”

Fires whenever a subscriber is created in the account, whatever brought them in. That makes it the broadest entry point of the app, and the noisiest.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
copy every new contact into another tool when you do not care which form or group they came through.
Watch out
a Zap that uses Create/Update Subscriber on the same account creates subscribers too, and can set this trigger off again and again.
3

Spam Complaint

Instant trigger

In Zapier“Triggers when subscriber issues a spam complaint about an email.”

Reacts when someone reports one of your emails as spam. Few events say more about the health of a list, and this one reaches Zapier with the subscriber attached.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
unsubscribe the address everywhere else and keep a written trace of who complained.
Watch out
a complaint is rare by nature, so test the trigger early; with no recent complaint in the account, you have nothing real to map.
4

Subscriber Added Through a Webform

Instant trigger

In Zapier“Triggers when a subscriber is added through a specific webform.”

Narrows things down to one form: the Zap only starts for people who signed up through the webform you pick. Sign-ups from other sources do not count.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
send the leads of one specific landing page form to the person who follows them up.
Watch out
the Webform field is required. The form must already exist in MailerLite Classic, and one Zap listens to one form only.
5

Subscriber Added to Group

Instant trigger

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

Watches a single group and fires each time someone joins it. Groups are how MailerLite Classic segments a list, so this is the trigger to follow a segment rather than the whole account.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
notify a colleague when someone enters a group that needs a personal reply.
Watch out
the Group field is required, and a Zap that adds people to that same group feeds itself.
6

Subscriber Completed Automation

Instant trigger

In Zapier“Triggers when a subscriber completed a selected workflow.”

Waits for a subscriber to reach the end of the automation workflow you select, then hands that person to Zapier. It marks a finish line, not a start.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
once an onboarding sequence is done, move the person out of its group or flag them in another tool.
Watch out
the Automation field is required, so build and name the workflow in MailerLite Classic before you set up the Zap.
7

Subscriber Bounced

Instant trigger

In Zapier“Triggers when an email to a subscriber bounces.”

Catches every email that comes back undelivered to a subscriber. It turns a delivery failure, normally buried in a report, into a step you can act on.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
flag the contact in your other tools so nobody keeps writing to an address that does not answer.
Watch out
a bounced address cannot be added back with Create/Update Subscriber unless the Resubscribe option is used, and that option should be used with care.
8

Subscriber Removed From Group

Instant trigger

In Zapier“Triggers when a subscriber has been removed from a group.”

The mirror of the group trigger: it fires when someone leaves the group you 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
keep another tool in step when a contact drops out of a segment, so both sides show the same membership.
Watch out
the Group field is required. Pair it with Remove Subscriber From a Group on the same group and one Zap can trigger the next.
9

Subscriber Triggered Automation

Instant trigger

In Zapier“Triggers when a subscriber has triggered a specific automation workflow.”

Fires when a subscriber enters a given automation workflow, at the start rather than the end. Useful when the rest of the team needs to know a sequence has begun.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
open a follow-up item in another tool the moment a contact steps into a sequence you care about.
Watch out
the Automation field is required, and one Zap follows one workflow; several workflows mean several Zaps.
10

Subscriber Unsubscribed

Instant trigger

In Zapier“Triggers when a subscriber has unsubscribed from your mailing list.”

Reacts to a subscriber leaving your mailing list. The address arrives in Zapier with the event, ready for the next step to use.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
mark the contact as opted out in your other tools, so an unsubscribe in one place counts everywhere.
Watch out
a Zap only sees unsubscribes that happen after it is switched on; people who left before are not picked up.
11

Subscriber Fields Updated

Instant trigger

In Zapier“Triggers when the subscriber fields have been updated.”

Whenever the fields of a subscriber change, this trigger hands the new values to Zapier. It follows people over time rather than at sign-up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
push the updated values to the record of the same person in another tool so both stay aligned.
Watch out
Create/Update Subscriber updates fields too, so a Zap that writes back to MailerLite Classic can trigger itself.
Actions

MailerLite Classic actions

MailerLite Classic 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/Update Subscriber

Action

In Zapier“Creates a new subscriber or updates the existing by email address.”

Adds a person to a group by email address, or updates them if the address already exists. One step covers both cases, which spares you a search you could not run anyway.

When to use it
file a sign-up captured in another app into the right MailerLite Classic group.
Watch out
an address that previously unsubscribed, bounced or never confirmed makes the step fail unless you switch on Resubscribe, which forces the status back to active.
2

Remove Subscriber From a Group

Action

In Zapier“Removes an existing subscriber from a group by email address.”

Takes an existing subscriber out of one group, found by email address. The person stays on your list; only the group membership goes.

When to use it
move someone out of a segment once a sequence or a deal is over.
Watch out
both the group and the email are required, so the group must already exist in MailerLite Classic before you set up the step.
3

Unsubscribe Subscriber

Action

In Zapier“Sets the contact's status to "unsubscribed".”

Sets the status of a contact to unsubscribed, found by the email you map. It is the strongest move of the four: the person stops receiving your emails.

When to use it
honor an opt-out that someone made in another tool or by replying to you.
Watch out
undoing it later means going through Create/Update Subscriber with Resubscribe on, so map the right email field.
4

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced step that sends a raw HTTP request to MailerLite Classic using the connection you already set up. It covers what the other three actions do not.

When to use it
a developer on your side needs a call that has no ready-made step.
Watch out
requests only go to domains tied to the app, and the Stop on error setting decides whether a failed call halts the Zap or lets it carry on.
When it breaks

When it breaks

Most failures on this integration come from list status, not from Zapier.

Here are the cases worth knowing before you publish. When a Zap stops for a reason you cannot place, see our Zapier troubleshooting guide.

  • A returning address makes the step fail

    Create/Update Subscriber fails on an email that previously unsubscribed, bounced or stayed unconfirmed. The Resubscribe option forces it back to active; use it responsibly.

  • The Zap writes into what it watches

    Adding people to a group watched by Subscriber Added to Group, or updating fields watched by Subscriber Fields Updated, sets the Zap off again and burns tasks fast.

  • Nothing from before is picked up

    A Zap only reacts to events after it is switched on. Subscribers, bounces and complaints that already existed stay where they are; moving them is a separate job.

  • A bulk import floods the trigger

    Importing a large list at once can send a huge batch to a trigger such as New Subscriber, and Zapier's flood protection can hold that batch back.

  • API Request (Beta) only reaches the app's domains

    API Request (Beta) refuses any URL outside the domains tied to MailerLite Classic. A request pointed elsewhere will not go through.

  • Stop on error changes the outcome

    On API Request (Beta), Yes halts the Zap when the app returns an error; No lets the next steps run regardless, possibly on empty data.
Need help

Need help automating MailerLite Classic with Zapier?

A person reads every message.

FAQ

MailerLite Classic and Zapier: questions people ask

01Is the MailerLite Classic Zapier integration free?
Yes, as long as the Zap has two steps. MailerLite Classic is not a premium app, so it works on the free plan, which gives 100 tasks a month. The catch is the size of the Zap: the free plan allows one trigger and one action. A Zap that unsubscribes someone and then logs the address in a sheet has two actions, which makes it a multi-step Zap, and that needs a paid plan. A filter has the same effect. If your idea fits in one trigger and one action, you can run it without paying.
02How many tasks does a MailerLite Classic Zap use?
One task per action that succeeds, and nothing for the trigger. A spam complaint arriving costs zero; unsubscribing that person costs one task; adding a row in a sheet after that costs one more. If an action fails, for example because the address is in a state the app refuses, it is not counted. So a busy list with many bounces only eats tasks when your Zap actually does something with them. Count the actions in your Zap and multiply by how often the trigger fires.
03Does MailerLite Classic trigger Zaps instantly?
Yes, all 11 triggers are instant. MailerLite Classic tells Zapier the moment the event happens, so the Zap starts without waiting for a scheduled check, and that holds on every plan, the free one included. The polling intervals in Zapier's plan grid simply do not apply here. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is a quick way to confirm it before you publish.
04What does it take to connect MailerLite Classic to Zapier?
An existing MailerLite Classic account and access to the things you want the Zap to touch. Zapier links your account, it does not set one up. Open the Apps page in Zapier, click + Add connection, pick MailerLite Classic, sign in in the tab that opens and grant access. Before building, make sure the groups, webforms or automations your triggers and actions need are already created in the app, because those fields are required and only list what exists.
05Why does Create/Update Subscriber fail on some addresses?
Because the address previously unsubscribed, bounced or never confirmed. MailerLite Classic will not quietly put such a contact back on the list, so the step fails. The action has a Resubscribe option that forces the status back to active. It exists for real cases, such as someone who asks to come back, and the app itself warns to use it responsibly. Switching it on by default would undo opt-outs people made on purpose. A failed step costs no task, but the person is not added.
06What if the MailerLite Classic operation you need is missing?
Check the four actions first; Create/Update Subscriber already covers both adding and updating. If what you want is still not there, API Request (Beta) can send a raw HTTP request to MailerLite Classic through your existing connection. It needs someone comfortable with the app's technical documentation, since you set the method and the URL yourself, and it only reaches domains tied to the app. There is no search step on this integration, so looking up a subscriber before acting is not something a standard step can do.
07Zapier, Make or n8n for MailerLite Classic?
Decide on criteria rather than on a name. On Zapier, check that the operations you need are among the 11 triggers and 4 actions listed here, that two steps are enough if you want to stay on the free plan, and that a task budget counted per successful action suits your volume. Instant triggers are a plus here, since every MailerLite Classic event reaches Zapier straight away. If you need a step that looks up a subscriber, note that this integration has none, and compare how each tool handles that.
Same platform

Other docs you might need on this stack.

Browse all integrations