Resources · Make integration

MailerLite Classic Make integrationAutomate MailerLite Classic with Make.

Can Make keep your MailerLite Classic lists tidy without manual work? This MailerLite Classic Make integration gives you 26 modules: 2 triggers, 15 actions and 9 searches. This guide shows marketers how to link the account, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the MailerLite Classic Make integration do?

The MailerLite Classic Make integration links your email marketing account to Make, a visual tool where you chain apps together without code. Each chain is a scenario: the automation you build, made of modules, one brick per step. Your scenario can add subscribers, sort them into groups, read their clicks and opens, and prepare or send campaigns.

Signups that land in the right group. A webinar tool or a form app collects an email. Your scenario passes it to Create/Update a Subscriber, so an existing contact gets refreshed instead of duplicated, then Add Subscriber to a Group files it where your welcome sequence lives.

Engagement data that leaves MailerLite. A sales rep wants to know whether a prospect opened the last newsletter. Search Subscribers By Email finds the contact and List Subscriber Activity By Type returns only the clicks, ready to write into your CRM.

Campaigns built from somewhere else. Your HTML lives in another tool? Create Campaign, Upload Campaign Content and Execute Campaign Action take it from draft to sent, or to scheduled.

One limit to know: the app only talks to version 1 of the MailerLite API, which is the Classic one. If a need falls outside the listed modules, Make an API Call reaches any v1 endpoint with the same account. The same app also has an n8n node, described on the MailerLite Classic n8n integration page, and the n8n vs Make comparison lays out both tools side by side. New to the editor? The Make training starts from zero.

Connect

How do you connect MailerLite Classic to Make?

  1. 01

    Generate an API token in MailerLite

    Log in to MailerLite, click your account name in the left side panel and open Integrations. In the list, pick Developer API and click Use, then New. Give the token a name you will recognize and click Create token.

  2. 02

    Copy the key somewhere safe

    MailerLite now shows the API key. Copy it into a password manager or a private note right away, because Make will ask for it in the next step. This key is what lets Make act on your lists, so keep it out of shared documents.

  3. 03

    Paste it into Make

    In Make, add any MailerLite Classic module and click Add next to the Connection field. Name the connection if you like, paste the key into API Key and hit Save. Every other MailerLite Classic module reuses this connection.

First scenario

Your first scenario: see a subscriber's groups the moment they change

GoalWhen MailerLite Classic reports an event on a subscriber, Make lists every group that person belongs to.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big +. That empty circle becomes your first module, the one that starts everything.

  2. 02

    Add Watch Subscribers

    Search for MailerLite Classic, pick Watch Subscribers and select the connection you made earlier. It is an instant trigger: MailerLite calls Make through a webhook the moment something happens to a subscriber.

  3. 03

    Add List Subscriber Groups

    Click the + on the right of the trigger and choose List Subscriber Groups. Map the subscriber coming from the trigger. This step only reads, so it never changes your list or fires the trigger again.

  4. 04

    Test with Run once

    Click Run once, then trigger a real subscriber event in MailerLite. Open the bubble above each module to read its bundle, the data passed along: one bundle per group the person is in.

  5. 05

    Switch it on

    Happy with the test? Turn the scenario on. Because the first module is instant, there is no interval to wait for: each subscriber event reaches Make as it occurs and runs the chain once.

Triggers

What can start a MailerLite Classic scenario?

2 modules start a scenario when something happens in MailerLite Classic. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by MailerLite Classic as soon as it happens.

MailerLite Classic1Watch Campaigns

Watch Campaigns

Scheduled trigger

In MakeRuns when a new campaign is added to your account.

This trigger notices each campaign newly added to your MailerLite Classic account and hands it to the rest of your scenario as a bundle, one per campaign. Handy for keeping a record of every campaign your team drafts.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and the Free plan cannot go below 15 minutes between checks.
When to use it
a new campaign should appear in a shared planning sheet or ping a reviewer in your team chat.
Watch out
it reacts to campaigns being added, not to sends, so pair it with List Campaigns if you need a status.
MailerLite Classic2Watch Subscribers

Watch Subscribers

Instant trigger

In MakeTriggers when an event occurs to subscribers.

Watch Subscribers wakes your scenario whenever an event touches a subscriber in MailerLite Classic. It is the natural entry point for anything that should follow a contact's life in your list.

How it fires
instant. MailerLite calls Make through a webhook as soon as it happens, so no schedule is involved.
When to use it
a contact changes in MailerLite and your CRM or support tool needs to know without anyone copying data by hand.
Watch out
each event costs at least one operation, meaning one run of one module, so a busy list spends operations on every single event it sends.
Modules

What can MailerLite Classic do inside Make?

MailerLite Classic gives you 24 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

MailerLite Classic1

Add Subscriber to a Group

Action

In MakeAdds new single subscriber to specified group.

Drops one new contact straight into the group you pick, which is where most MailerLite sequences start. The subscriber appears in that group and any automation tied to it can kick in.

When to use it
a lead signs up on a landing page built elsewhere and belongs to one precise list.
Watch out
it handles a single subscriber per run; a list of emails needs one bundle each, so one operation each.
MailerLite Classic2

Create Campaign

Action

In MakeCreates campaign where you will use your custom HTML template.

Opens a fresh campaign in MailerLite Classic designed to receive your own custom HTML template. Think of it as the empty envelope before the letter goes in.

When to use it
your newsletter is written in a CMS or a design tool and you want MailerLite to hold it without manual copy and paste.
Watch out
the campaign stays empty until Upload Campaign Content fills it, so place that module right after.
MailerLite Classic3

Create Group

Action

In MakeCreates new group.

Makes a brand new group in your account, ready to receive subscribers. Groups are how MailerLite Classic splits your audience, so creating them on the fly keeps the structure in step with your business.

When to use it
each new event, product launch or client cohort deserves its own list the moment it is created in another tool.
Watch out
call it only when the group is truly new; List Groups shows what already exists before you add another one.
MailerLite Classic4

Create/Update a Subscriber

Action

In MakeCreates a new subscriber or updates an existing one.

Checks whether the contact already exists: if not, it creates it; if so, it refreshes it. One module replaces a search followed by a branch, which keeps a beginner's scenario short.

When to use it
data arrives from a form or a shop where the same person may come back several times.
Watch out
map only the data you trust, because whatever reaches this module lands on the subscriber's record.
MailerLite Classic5

Execute Campaign Action

Action

In MakeSends, schedules or cancels campaign.

Gives the final order on a campaign: send it now, schedule it, or cancel it. This is the button your team would otherwise click inside MailerLite, now pressed by the scenario.

When to use it
a campaign should leave only after an approval recorded in another app.
Watch out
a send cannot be pulled back; test the chain with Run once on a campaign aimed at an internal group first.
MailerLite Classic6

Get Group

Action

In MakeGets single group by ID.

Fetches the details of a single group when you already know its ID. The result travels on as a bundle, so later modules can reuse the group's information without another lookup.

When to use it
an earlier step stored the group ID and you need its current details before writing a report or a message.
Watch out
it needs the ID, not the name; List Groups is the way to find that ID first.
MailerLite Classic7

Get Group Subscriber

Action

In MakeGets a single subscriber by ID in specified group.

Reads one subscriber inside one specific group, using the subscriber's ID. It answers a narrow question: what does this person look like from the point of view of this list?

When to use it
a branch of your scenario only matters for members of a VIP or trial group.
Watch out
you must provide both the group and the subscriber ID; with only an email in hand, Get Subscriber fits better.
MailerLite Classic8

Get Subscriber

Action

In MakeGets single subscriber by ID or Email.

Pulls one subscriber's record from the whole account, found either by ID or by email address. Email is usually what other apps send you, which makes this the friendliest lookup of the set.

When to use it
a support ticket arrives and the agent wants the requester's MailerLite status next to it.
Watch out
it returns one record; when an address may match nothing, Search Subscribers By Email handles that case more gracefully as a search.
MailerLite Classic9

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Sends your own authorized request to the MailerLite API, reusing the connection you already set up. It covers whatever the listed modules leave aside, without a second login.

When to use it
you found an endpoint in the MailerLite Classic API documentation and no ready-made module does that job.
Watch out
only v1 endpoints apply here, since the app supports that version alone; reading the API docs is part of the job.
MailerLite Classic10

Remove Campaign

Action

In MakeRemoves a campaign.

Deletes a campaign from your account. Useful for tidying the drafts a scenario may generate while you experiment, or for cleaning up after a cancelled project.

When to use it
a test run created campaigns you no longer want cluttering the dashboard.
Watch out
treat the deletion as final; add a filter so only campaigns you clearly identified reach this module.
MailerLite Classic11

Remove Group

Action

In MakeRemoves group by ID.

Erases a whole group, found by its ID. Your list structure gets lighter when a segment has served its purpose, such as the attendees of a past event.

When to use it
a project closes in your project tool and its dedicated MailerLite group should go with it.
Watch out
there is no undo, so check the ID with Get Group in the step just before.
MailerLite Classic12

Remove Subscriber From Group

Action

In MakeRemoves single subscriber from specified group.

Takes one subscriber out of one group while leaving the contact in your account. It moves people between stages of a journey without losing their history.

When to use it
a trial user pays, so they leave the trial group before joining the customer one.
Watch out
this is not an unsubscribe; the person still receives mail sent to their other groups.
MailerLite Classic13

Update Group

Action

In MakeUpdates existing group.

Edits an existing group so its details match what changed elsewhere. The subscribers inside stay exactly where they are.

When to use it
a client renames a program in your CRM and the matching MailerLite group should follow without anyone logging in.
Watch out
it needs the group ID, so keep that ID stored alongside the record it mirrors in your other tool.
MailerLite Classic14

Update Subscriber

Action

In MakeUpdates single subscriber by ID or Email.

Changes the record of a subscriber you already know, found by ID or email. Unlike Create/Update a Subscriber, it never creates a new contact.

When to use it
a customer edits their profile in your app and MailerLite should hold the same information.
Watch out
if the contact may not exist yet, the create-or-update module covers both cases in one step.
MailerLite Classic15

Upload Campaign Content

Action

In MakeUploads your HTML template to created campaign.

Pours your HTML template into a campaign that already exists. Paired with Create Campaign, it lets a newsletter go from your editor to MailerLite without a copy and paste in between.

When to use it
your HTML is generated by another tool, a CMS export for instance, and you want it inside the right campaign.
Watch out
the campaign must be created first; map its ID from the previous module.
MailerLite Classic16

List Campaigns

Search

In MakeLists all campaigns by status.

Returns your campaigns filtered by status, each one as a separate bundle. As a search, it can send back zero, one or many results.

When to use it
a dashboard needs the campaigns of one status, or a cleanup step must find the ones to remove.
Watch out
every returned campaign flows into the next modules and costs operations there, so filter before acting on them.
MailerLite Classic17

List Groups

Search

In MakeLists all groups for this account.

Brings back every group in the account, one bundle per group. It is the quickest way to discover the IDs that the Get, Update and Remove modules ask for.

When to use it
you are building a report of your lists or syncing their names into a spreadsheet.
Watch out
the modules placed after it run once per group; add an aggregator if you want a single summary instead.
MailerLite Classic18

List Group Subscribers

Search

In MakeLists all subscribers in a specified group.

Outputs all the subscribers of one chosen group. Each person becomes a bundle, which suits exports and bulk syncing toward another tool.

When to use it
the members of a webinar group should land in a sales team's CRM as prospects.
Watch out
a large group means many bundles and as many operations downstream; test with Run once on a small group.
MailerLite Classic19

List Group Subscribers By Type

Search

In MakeLists all subscribers in a specified group by type.

Same idea as List Group Subscribers, with one extra filter: only the subscribers of the type you choose come back. Fewer bundles, fewer operations spent on people you would skip anyway.

When to use it
you only care about one category of members in a group and want the search to do the sorting.
Watch out
check the type options in the module itself, since the choice decides who is left out.
MailerLite Classic20

List Segments

Search

In MakeLists all stored segments for this account.

Lists the segments saved in your account. Segments are stored audience definitions, a different thing from groups, and this search lets a scenario see them.

When to use it
you want an inventory of your segments, for documentation or to spot the ones nobody uses anymore.
Watch out
no other module here edits segments; for that, look at Make an API Call.
MailerLite Classic21

List Subscriber Activity

Search

In MakeLists activity (clicks, opens, etc) of selected subscriber.

Shows what one subscriber did with your emails, clicks and opens included. Each activity comes out as a bundle you can count, filter or send elsewhere.

When to use it
before a sales call, your rep wants the full engagement history of the lead in one message.
Watch out
an active reader produces many bundles; add an aggregator to turn them into one summary.
MailerLite Classic22

List Subscriber Activity By Type

Search

In MakeLists activity of selected subscriber by specified type (opens, clicks, etc).

Narrows a subscriber's history to a single kind of activity, opens or clicks for example. The answer is shorter and straight to the point.

When to use it
only clicks count as buying intent for your team, so a scoring rule should ignore opens.
Watch out
pick the type carefully; a scenario reading opens when it meant clicks will look fine in a test and still mislead.
MailerLite Classic23

List Subscriber Groups

Search

In MakeLists groups subscriber belongs to.

Tells you every group a given subscriber belongs to. It answers the reverse question of List Group Subscribers: not who is in this list, but which lists hold this person.

When to use it
a customer writes to support and the agent needs to see their memberships at a glance.
Watch out
the result arrives one group per bundle; gather them with an aggregator before writing a single note.
MailerLite Classic24

Search Subscribers By Email

Search

In MakeSearches for subscribers by email.

Looks up subscribers from an email address and returns what it finds, possibly nothing. It works well as a gate before deciding what the scenario should do next.

When to use it
you want to check whether a buyer is already on your list before sending a welcome series.
Watch out
an empty result is normal for a search, so add a filter that handles the no-match case.
Need help

Need help automating MailerLite Classic with Make?

A person reads every message.

FAQ

Questions people ask about MailerLite Classic and Make

01Is the MailerLite Classic Make integration free?
Yes, MailerLite Classic is a standard app, so it works from the Make Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans remove the cap on active scenarios and let a scheduled trigger check every minute. Your MailerLite subscription is a separate matter that this page does not cover.
02What do you need to connect MailerLite Classic to Make?
You need a MailerLite account and an API key generated inside it. Go to your account name, then Integrations, then Developer API, click Use and New, name the token and create it. In Make, click Add next to the Connection field, paste the key into API Key and save. The Make doc lists no other prerequisite. Keep in mind that the app supports API v1 only, which corresponds to MailerLite Classic.
03Does the MailerLite Classic trigger react in real time?
It depends on which one you choose. Watch Subscribers is instant: MailerLite calls Make through a webhook as soon as a subscriber event occurs. Watch Campaigns is scheduled: Make checks your account on the scenario's schedule, every 15 minutes by default. On the Free plan that interval cannot drop under 15 minutes, while paid plans go down to one minute. Pick the instant trigger when speed matters for contacts. Both badges show on the module in the editor.
04What if a MailerLite Classic module is missing?
Use Make an API Call. It sends any authorized request to the MailerLite API with the connection you already have, so an endpoint without a dedicated module is still reachable. Read the MailerLite Classic API documentation to find the path you need. The one hard limit is the version: the app supports API v1 only, so features that exist only in the newer MailerLite API stay out of reach from this app.
05Should you use Make or n8n for MailerLite Classic?
Both options exist, so the choice depends on your setup rather than on the app. On Make you get 26 ready modules, 2 of them triggers, plus Make an API Call for the rest, all driven from a visual editor. MailerLite also has an n8n node, documented on the dedicated n8n page. If your team already builds its automations in one of the two tools, staying there keeps every workflow in a single place.