Resources · n8n integration

MailerLite n8n integrationAutomate MailerLite with n8n.

Your list should react on its own, not wait for a copy and paste. The MailerLite n8n integration gives you one node with 4 subscriber operations, plus a trigger that listens to 10 events spread across 2 families. Enough to keep contacts and alerts in step with the rest of your tools.

Try the MailerLite integration on n8nSee the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the MailerLite n8n integration actually cover?

Two nodes, two directions. The MailerLite node calls the API and works on the Subscriber resource: create one, read one, list many, update one. The MailerLite Trigger waits instead, and starts a workflow the moment MailerLite reports something on a subscriber or a campaign. Put together, an email list stops being a separate tab and becomes a step inside a process that runs without anyone watching it.

First scenario, the signup that lands everywhere at once. A checkout, a webinar form or a landing page drops a row somewhere, and the same run creates the contact with subscriber.create. The address goes in through the Email field, the rest of the row can fill Custom Fields, and a copy of the record lands in Google Sheets so the sales side has the same view as the marketing side.

Second scenario, the bad news you want to hear early. A bounce or a spam report arrives as subscriber.bounced or subscriber.spam_reported, and the workflow posts the address into a Slack channel before anyone notices the pattern by reading a report. The same branch can call subscriber.update to write a matching Status back, so the record in MailerLite tells the same story as the alert.

Third scenario, the follow-up that depends on behavior. When subscriber.automation_completed fires, the person has reached the end of a sequence. That is the moment to hand them over: a personal message through Gmail, a task for the account owner, or a read with subscriber.get to check the current custom fields before deciding what to send.

When the node has no operation for what you need, the HTTP Request node calls any endpoint of the MailerLite API and reuses the same credential through predefined authentication. Nothing to re-enter, no second key to store. It is the normal path for anything outside the four subscriber operations the node exposes.

Two things are worth knowing before you build. The node covers 1 resource and 4 operations, so the catalogue is small and the boundary is clear. And the trigger has no catch-all option: each of the 10 events you care about gets ticked by name in the Events parameter. If the wider picture matters to you, the n8n review goes through the platform itself, and n8n training covers the building part.

Connect

How do you connect MailerLite to n8n?

  1. 01

    Generate the API key in MailerLite

    Open your MailerLite account and head to the Integrations menu, which is where the API key is generated. That key is the only authentication method the node and the trigger accept, so there is no OAuth screen to go through and no app to install on the MailerLite side. Copy the value once it appears, and keep the tab open: you will want to know which MailerLite experience the account runs on before the next step.

  2. 02

    Create the credential in n8n

    In n8n, go to the Credentials menu and add a MailerLite credential, which is the stored login n8n reuses everywhere. Paste the value into API Key. Then decide on the Classic API toggle: enable it only when the key belongs to a MailerLite Classic account. Most new accounts, and all free ones, should leave that toggle off. A credential created once shows up in the dropdown of every workflow you build afterward.

  3. 03

    Attach it to the node and the trigger

    Drop the MailerLite node onto the canvas, pick the credential from its list, choose the Subscriber resource and the operation you want. The MailerLite Trigger takes the same credential, with no separate setup. Tick the events in Events, then activate the workflow: that is when n8n registers its webhook with MailerLite, a webhook being a URL the tool calls on its own as soon as something happens.

Triggers

What starts a workflow from MailerLite ?

MailerLite Trigger is the node that starts a workflow when something happens in MailerLite. It listens to 10 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your MailerLite account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

subscriber.*9
  • subscriber.
    • added_to_group
    • automation_completed
    • automation_triggered
    • bounced
    • created
    • removed_from_group
    • spam_reported
    • unsubscribed
    • updated
campaign.*1
  • campaign.
    • sent

Configuration notes

01Set Up the MailerLite TriggerThe MailerLite Trigger sits first on the canvas and gives the workflow its starting item. It runs on the same API key credential as the node, so there is nothing extra to configure once the credential exists.

The MailerLite Trigger sits first on the canvas and gives the workflow its starting item. It runs on the same API key credential as the node, so there is nothing extra to configure once the credential exists.

Key parameters

  • Events: the list of MailerLite events this workflow answers to. Tick one, tick several, but tick them by name: there is no wildcard option that would catch everything at once, so an event nobody selected never reaches n8n.
When to use it
whenever MailerLite is the side that knows first. The mechanism is a webhook, meaning MailerLite calls an n8n URL on its own, and n8n registers that URL when you activate the workflow. Each event lands within seconds, and nothing checks the API on a schedule in the meantime. The flip side is that a deactivated workflow hears nothing, so an inactive test canvas will look broken when it is only asleep.
02Subscriber EventsNine of the ten events describe one contact, which makes this family the one most workflows are built on. Lifecycle first: subscriber.created when a new address joins the account, subscriber.updated when any custom field changes, subscriber.unsubscribed when someone opts out.

Nine of the ten events describe one contact, which makes this family the one most workflows are built on. Lifecycle first: subscriber.created when a new address joins the account, subscriber.updated when any custom field changes, subscriber.unsubscribed when someone opts out.

Group membership has its own pair, subscriber.added_to_group and subscriber.removed_from_group, useful when a group stands for a segment other tools also need to know about. Deliverability signals come through subscriber.bounced and subscriber.spam_reported. Automation sends two more, subscriber.automation_triggered at the start of a sequence and subscriber.automation_completed at the end.

When to use it
pick the narrow event rather than the broad one. A workflow listening only to subscriber.removed_from_group stays readable, while one that ticks every subscriber event ends up starting with a long chain of conditions.
03Campaign SentOne event covers the campaign side: campaign.sent, fired when a campaign goes out. It is the only member of its family, and it speaks about the send itself rather than about a single reader.

One event covers the campaign side: campaign.sent, fired when a campaign goes out. It is the only member of its family, and it speaks about the send itself rather than about a single reader.

When to use it
as a starting gun for everything that has to happen around a send. Post a short note in the channel where the team tracks launches, write the date into a tracking sheet, or start a timer that waits before the next step of a sequence. It also pairs well with the subscriber events: a campaign goes out, and the reactions arrive afterward as subscriber.unsubscribed or subscriber.spam_reported on the same canvas. Keeping both in one workflow gives you the send and its aftermath in a single execution history, instead of two workflows nobody reads together.
Actions

What can the MailerLite node do?

The MailerLite node exposes 4 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetGet ManyUpdate
Subscriber✓✓✓✓

Subscriber

4 operations
01

Create a subscriber

subscriber.create

What you see in n8n

Notes & use cases

Adds a contact to the MailerLite account and returns the created record, which the following nodes can reuse straight away.

Key parameters

  • Email: the address of the new subscriber, in the name@email.com form. It is required, so an empty value stops the node; most workflows pass an expression such as {{ $json.email }} taken from the form or the row that came in.
  • Additional Fields: optional, and worth opening. It holds Status (active, unconfirmed, bounced, junk or unsubscribed), Custom Fields, plus the consent trail: Subscribed At, Opted In At, Opt In IP, IP Address and Unsubscribed At.
Use cases
a webinar form fills a sheet, and the same execution puts the attendee in MailerLite with the source stored in a custom field.
02

Get a subscriber

subscriber.get

What you see in n8n

Notes & use cases

Reads one contact and returns that single record, which is the simplest way to know what MailerLite currently holds on an address.

Key parameters

  • Subscriber Email: the email of the subscriber to get. This operation works from the address itself, not from an internal identifier, so an address collected anywhere else is enough to look someone up.
Use cases
before sending a manual follow-up, read the record to see the current status and custom fields, then branch on what comes back instead of writing over fresher data.
03

Get many subscribers

subscriber.getAll

What you see in n8n

Notes & use cases

Lists the subscribers of the account and returns one item per contact, ready to loop over or export.

Key parameters

  • Return All: switched on, n8n walks through the API pages and brings back every subscriber. Switched off, Limit caps how many items come out, which keeps a test run short.
  • Filters: holds Status, so a run can ask only for active contacts, or only for unsubscribed ones when the point is to clean up.
Use cases
a weekly export of active contacts into a spreadsheet the sales team already opens every Monday.
04

Update a subscriber

subscriber.update

What you see in n8n

Notes & use cases

Writes new values onto a contact that already exists, and returns the record as it stands after the change.

Key parameters

  • Subscriber Email: the email of the subscriber, used to find the right record. Feed it from the trigger payload with an expression when the update follows an event.
  • Additional Fields: whatever you want changed. Custom Fields takes the values coming from another tool, and Status moves the contact between active, unsubscribed, bounced, junk and unconfirmed.
Use cases
a CRM marks a deal as won, and the workflow writes the new stage into the contact's custom fields the same minute.
Need help

Need help automating MailerLite with n8n?

A person reads every message.

FAQ

Questions people ask about MailerLite and n8n

01Is the MailerLite integration free in n8n?
Yes, on the n8n side. The MailerLite node and the MailerLite Trigger ship with n8n, so there is nothing to install and no extra cost, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use licence. A workflow behaves the same in both cases, and moving one from a laptop to a server does not change how the node works. What a MailerLite account itself costs is a separate question this page does not answer. The only thing you need on that side is an account able to generate an API key from the Integrations menu.
02What credentials do you need to connect MailerLite to n8n?
One API key, and that is the only supported authentication method. You generate it from the Integrations menu of your MailerLite account, then paste it into the API Key field of a MailerLite credential in n8n. The same credential covers both the node and the trigger, so you create it once and pick it from a dropdown in every workflow afterward. The one setting that needs attention is the Classic API toggle: turn it on only if the key belongs to a MailerLite Classic account. Most new accounts, and all free accounts, should leave it off.
03What are the limits of the MailerLite node in n8n?
The catalogue is deliberately small: 1 resource, Subscriber, and 4 operations on it. Anything the MailerLite API exposes beyond those operations goes through the HTTP Request node, which calls any endpoint and reuses the same credential through predefined authentication, so there is no second key to manage. On listings, remember that Return All is what makes n8n page through the API; leave it off and Limit decides how many subscribers come back, which is fine for a test and misleading for an export. On the trigger side, the absence of a wildcard means every event has to be ticked by name.
04Does the MailerLite Trigger react in real time?
Yes. The trigger works by webhook, which means MailerLite calls an n8n URL by itself each time one of the selected events happens. Nothing polls the API on a schedule. n8n registers that URL with MailerLite when you activate the workflow, and from then on each event reaches the canvas within seconds. Two practical consequences. A workflow that is not activated receives nothing, so testing on an inactive canvas gives a false impression of a broken connection. And only the events ticked in the Events parameter are sent, since the trigger offers no catch-all option covering all 10 at once.
05n8n or Make for a MailerLite n8n integration?
It depends on three things, and price per feature is not really one of them. Hosting: n8n runs on your own server through Docker or npm, or on n8n Cloud, while Make is hosted only, so the choice also decides where subscriber data transits. Cost model: Make bills by operation, which matters when a list workflow fires on every subscriber event of a busy account. Visual logic: both draw a canvas, and the honest answer is that the one you read faster is the one you will maintain. Try the same small workflow on each, then keep the platform that made it obvious.
Same platform

Other docs you might need on this stack.

Browse all integrations