Reference · Tools
MailerLite
Manage subscribers in the MailerLite email marketing platform
The MailerLite node manages subscribers — creating, retrieving, listing and updating them — in the MailerLite platform, with filters and pagination for large audiences. A typical build is keeping a MailerLite list in step with your customer database as accounts are created and updated.
- Node type
- Action
- Parameters
- 10
- Outputs
- Output, Error
- Credentials
- MailerLite API
MailerLite
Create, get, list, and update subscribers in MailerLite.
Overview
MailerLite is an email marketing platform. This tool manages subscribers — creating, retrieving, listing, and updating subscriber records. It supports both the classic (v1) and new (v2) MailerLite APIs, determined by the credential configuration. Subscriber operations include managing custom fields, subscriber status, and metadata.
Category: Communication
Tool Name: mailerlite
Version: 2
Appearance: Icon: lucide-Mail | Color: #09C269
Node Type
Action — processes input items and produces output
Input / Output
| Direction | Port(s) |
|---|---|
| Input | Input |
| Output | Output, Error |
Credentials
This tool requires MailerLite API credentials. See the Credentials Guide for setup instructions.
Resources
| Resource | Value |
|---|---|
| Subscriber | subscriber |
Operations
| Operation | Value | Description |
|---|---|---|
| Create | create | Create a new subscriber |
| Get | get | Get a subscriber |
| Get Many | getAll | Get many subscribers |
| Update | update | Update a subscriber |
Parameters
Subscriber: Create
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
string | Yes | — | Email address of the new subscriber. Supports expressions like {{ $json.email }}. | |
| Additional Fields | collection | No | {} | Extra subscriber attributes to set alongside the email address. |
| — Custom Fields | fixedCollection | No | {} | Custom field key-value pairs. Field keys can be retrieved from the MailerLite dashboard under Settings > Subscriber fields, or via the GET /fields API endpoint. |
| — — Field Key | string | No | — | The key of the custom field. Find available fields in MailerLite dashboard under Settings > Subscriber fields, or via GET /fields API. |
| — — Value | string | No | — | The value to set on the custom field. Supports expressions. |
| — Status | options | No | — | Status of the subscriber. |
Options: active, bounced, junk, unconfirmed, unsubscribed | ||||
| — Subscribed At | dateTime | No | — | Timestamp when the subscriber was added. |
| — IP Address | string | No | — | IP address of the subscriber. |
| — Opted In At | dateTime | No | — | Timestamp when the subscriber opted in. |
| — Opt In IP | string | No | — | IP address where the subscriber opted in. |
| — Unsubscribed At | dateTime | No | — | Timestamp when the subscriber unsubscribed. |
Subscriber: Get
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
Subscriber Email (subscriberId) | string | Yes | — | Email address of the subscriber to retrieve. Supports expressions like {{ $json.email }}. |
Subscriber: Get Many
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Return All | boolean | No | false | Whether to return all results or only up to a given limit. |
| Limit | number | No | 50 | Max number of results to return. Accepts 1–100. (shown when Return All is false) |
| Filters | collection | No | {} | Narrow the subscribers returned. |
| — Status | options | No | — | Filter subscribers by status. |
Options: active, bounced, junk, unconfirmed, unsubscribed |
Subscriber: Update
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
Subscriber Email (subscriberId) | string | Yes | — | Email address of the subscriber to update. Supports expressions like {{ $json.email }}. |
| Additional Fields | collection | No | {} | The subscriber attributes to change. |
| — Custom Fields | fixedCollection | No | {} | Custom field key-value pairs. Field keys can be retrieved from the MailerLite dashboard under Settings > Subscriber fields, or via the GET /fields API endpoint. |
| — — Field Key | string | No | — | The key of the custom field. Find available fields in MailerLite dashboard under Settings > Subscriber fields, or via GET /fields API. |
| — — Value | string | No | — | The value to set on the custom field. Supports expressions. |
| — Status | options | No | — | Status of the subscriber. |
Options: active, bounced, junk, unconfirmed, unsubscribed | ||||
| — Subscribed At | dateTime | No | — | Timestamp when the subscriber was added. |
| — IP Address | string | No | — | IP address of the subscriber. |
| — Opted In At | dateTime | No | — | Timestamp when the subscriber opted in. |
| — Opt In IP | string | No | — | IP address where the subscriber opted in. |
| — Unsubscribed At | dateTime | No | — | Timestamp when the subscriber unsubscribed. |
All Operations
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Max Concurrency | number | No | 10 | Maximum number of items to process concurrently. |
Output Data
The subscriber record MailerLite returns is merged into the item JSON at the top level — the API’s data envelope is unwrapped for you — so the fields the input item already carried pass through unchanged and binary data is forwarded.
| Operation | Output items |
|---|---|
create | One item per input item, carrying the created subscriber record |
get | One item per input item, carrying the retrieved subscriber record |
getAll | Fans out — one output item per subscriber returned. An input item matching nothing yields a single item carrying _empty: true and subscribers: [] |
update | One item per input item, carrying the updated subscriber record |
getAll is the only operation that changes the item count: five subscribers become five items, each a full copy of the input item’s JSON with one subscriber’s fields merged on. Downstream nodes then process subscribers one at a time with no Split Out node in between.
Reference the returned fields directly with {{ $json.… }}; run the node once and inspect an output item to see the exact field names your MailerLite API version returns.
Usage Examples
- Create a new email subscriber in MailerLite
- Get subscriber details by email address
- List all active subscribers from MailerLite
- Update subscriber status to unsubscribed
Example Configuration
Create a subscriber with nothing but an email address:
{
"type": "mailerlite",
"parameters": {
"resource": "subscriber",
"operation": "create",
"email": "user@example.com"
}
}
Create a subscriber with metadata and custom fields:
{
"type": "mailerlite",
"parameters": {
"resource": "subscriber",
"operation": "create",
"email": "{{ $json.email }}",
"additionalFields": {
"status": "active",
"subscribed_at": "2024-01-01T00:00:00Z",
"ip_address": "192.168.1.1",
"customFieldsUi": {
"customFieldsValues": [
{
"fieldId": "first_name",
"value": "{{ $json.firstName }}"
},
{
"fieldId": "last_name",
"value": "{{ $json.lastName }}"
}
]
}
}
}
}
Get one subscriber by email address:
{
"type": "mailerlite",
"parameters": {
"resource": "subscriber",
"operation": "get",
"subscriberId": "user@example.com"
}
}
Update a subscriber’s status and a custom field:
{
"type": "mailerlite",
"parameters": {
"resource": "subscriber",
"operation": "update",
"subscriberId": "user@example.com",
"additionalFields": {
"status": "active",
"customFieldsUi": {
"customFieldsValues": [
{
"fieldId": "first_name",
"value": "Jane"
}
]
}
}
}
}
List subscribers, capped at 50:
{
"type": "mailerlite",
"parameters": {
"resource": "subscriber",
"operation": "getAll",
"returnAll": false,
"limit": 50
}
}
List every active subscriber:
{
"type": "mailerlite",
"parameters": {
"resource": "subscriber",
"operation": "getAll",
"returnAll": true,
"filters": {
"status": "active"
}
}
}
Error Handling
| Mode | Behavior |
|---|---|
| stop | Halts workflow on first error |
| continue | Skips failed items, passes successful ones through |
| errorPort | Routes failed items to Error output port |
Tips
Create, retrieve, list, or update subscribers in MailerLite email marketing platform.
Pagination Strategy
- For small datasets: Set
returnAlltotrue - For large datasets: Set
returnAlltofalseand specify alimit - Always consider using
filtersto reduce the result set when possible
Frequently asked questions
How should I page through a large audience?
For small result sets turn Return All on. For large ones turn it off and set a limit, and use filters to reduce the result set before it is fetched.
Can it create and update in one step?
Create and update are separate operations, so decide which you need — or look the subscriber up first and branch on whether they exist.
How do I react to subscriber events?
Use the MailerLite Trigger, which fires on subscriber creation, updates, bounces, unsubscribes and group membership changes.
Which credential does it need?
A MailerLite API credential.
Build with the MailerLite node
Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need MailerLite API credentials first.
Open BusyBotLast updated . Spotted something wrong? Tell us.