Menu

Mattering Automations MailerLite integration

Connect MailerLite to Mattering Automations: subscribers, groups, segments, custom fields, forms, campaigns, automations, webhooks and the full e-commerce surface as workflow steps, authorized with a single API token.

The Mattering Automations MailerLite integration puts MailerLite's current API on your automation canvas: create and update subscribers, manage groups, segments and custom fields, read forms and their signups, build campaigns and read their reports, register webhooks, and run the entire e-commerce surface of shops, products, categories, customers, orders, carts and cart items. Ninety seven nodes in total, forty five that read and fifty two that act, covering all 92 operations MailerLite's reference documents.

The credential is a single API token that you generate inside MailerLite and paste into a Mattering connector. There is no OAuth application to register and no approval to wait for. Click Test Connection afterwards and Mattering reads the subscriber count, which proves the token without touching any subscriber data.

Two things are worth reading before you build anything, because both are cheaper to know now than to hit later. Sending is plan gated: MailerLite's pricing FAQ states that email sending via the API and MCP server is available on paid plans, and that on Free, API and MCP access is limited and does not include sending, so on a free account every data node works and MailerLite: Schedule or Send Campaign will not deliver. And this is MailerLite, not MailerLite Classic, which is a separate product on a different host with a different authentication header. Both are explained in full below, and this guide ends with the complete node reference.

Before you start

  • A MailerLite account on the current MailerLite rather than MailerLite Classic. Classic is a separate product with its own host, its own X-MailerLite-ApiKey header and its own documentation site, and a Classic key will not authenticate here.
  • A paid MailerLite plan if any workflow needs to send. MailerLite's pricing FAQ states that email sending via the API and MCP server is available on paid plans, and that on Free, API and MCP access is limited and does not include sending. A free token still exercises the rest of this integration: subscribers, groups, segments, fields, forms, campaign drafts, reports, webhooks and the whole e-commerce surface all work, and MailerLite: Schedule or Send Campaign is the node that will not deliver mail.
  • An awareness of two further plan gates on campaigns. MailerLite's campaign reference states that the resend and multivariate campaign types are available only on its higher paid tiers, and that supplying raw HTML as campaign content requires its top tier. The tier names in MailerLite's API reference and on its current pricing page do not match, so check the pricing page for which plan that is today rather than trusting a name.
  • An API token generated from Integrations, then MailerLite API, then Generate new token inside MailerLite. Decide who generates it first: MailerLite states that API keys are permanently bound to the user who created them, so a token stops working if that person is removed from the account.
  • A connected shop, if you intend to use any of the 46 e-commerce nodes. Every e-commerce path below the shops collection is scoped to a shop id, so MailerLite: List Shops or MailerLite: Create Shop is the first call in every one of those workflows.
  • A plan for bulk work that respects two different rate limits. MailerLite allows 120 requests per minute globally and 5 per minute on imports, and the import limit also applies to any batch made entirely of subscriber upserts.
  • A Mattering workspace with access to the Automations app.

Generate a MailerLite API token

MailerLite issues API tokens from inside the app, so there is nothing to register and nothing to wait for. The only decision that carries weight is which user generates it, because MailerLite ties the token's lifetime to that user's membership of the account.

Sign in to MailerLite and confirm you are on the current MailerLite rather than MailerLite Classic. The two products have separate applications, separate hosts and separate API keys, and only the current one works here.
Open Integrations, choose MailerLite API and click Generate new token. Copy the token: this is the only time it is shown.
MailerLite states that API keys are permanently bound to the user who created them, and that if the user is removed from the account or the user account is deleted, the key stops working and no longer authenticates any requests. Generate the token from an account the business controls rather than an individual's personal login, or the integration will fail one day with a 401 and nothing on the Mattering side will have changed.
Sending is the one capability a free MailerLite plan does not give an API token. MailerLite's pricing FAQ states that email sending via the API and MCP server is available on paid plans, and that on Free, API and MCP access is limited and does not include sending. Every other node in this integration works on a free token.

Connect MailerLite to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose MailerLite from the list.
Click Create new credential and paste the API token into the token field. There is nothing else to fill in: a MailerLite token is a plain bearer token with no subdomain, no second field and no expiry.
The token is stored encrypted in Google Secret Manager and never appears in workflow logs. Revoking it inside MailerLite ends the connection immediately, and generating a replacement is a one-field edit on the credential rather than a rebuild of anything.
Click Test Connection. Mattering calls the subscriber count endpoint with all of MailerLite's required headers, which reads a single number rather than any customer data and needs no ids, so a success proves the token and the header wiring together.
A 403 is not a pass and it is not the same finding as a 401. MailerLite defines 403 as the action being denied for that account or that token, which on this API usually means a plan gate rather than a bad key. A 401 with a body of Unauthenticated means the token itself was rejected.
All 97 MailerLite nodes appear in your canvas palette, grouped as 45 read nodes and 52 action nodes.

Verify it works

Open any automation canvas and check the palette: a MailerLite section should list the read and action nodes. Drop MailerLite: List Groups onto the canvas and run a test step. It is the natural first probe because it takes no ids, needs nothing set up in advance, and is the node most pickers in this integration read from, so a working response confirms the credential and the picker plumbing at the same time. Each group comes back with its membership counts and engagement rates broken down by status.

Now run MailerLite: Count Subscribers. It returns a single total and nothing else, because MailerLite documents a limit of zero as its own operation with its own response body: no rows, no links and no paging metadata. This is the cheapest read on the whole API and it is what Test Connection uses, so if it works here the credential is unambiguously fine. Note that the node carries no limit field at all, because the value is fixed by the connector and cannot be overridden from configuration.

Finish with MailerLite: List Subscribers and look at what comes back in the response metadata. You should see a next cursor and no page numbers, because this endpoint is cursor paged. Compare it with MailerLite: List Campaigns, which reports a current page, a last page and a total instead. That difference is real and it is the single most useful thing to have seen before you build a loop. Everything in this verify path is read-only, so it cannot reach a delete or a send, and it is safe to re-run whenever you want to check the connection.

Node reference

97 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 45

MailerLite: Count Cart Items

mailerlite_count_cart_items

Return the number of line items in one cart as a single number. limit=0 is a distinct MailerLite operation returning {"total": 123} with no data array and no meta. Note it counts LINE ITEMS, not units: an item with quantity 3 counts once. The limit is fixed at 0 by this node.

MailerLite: Count Carts

mailerlite_count_carts

Return the number of carts in a shop as a single number. limit=0 is a distinct MailerLite operation returning {"total": 123} with no data array and no meta. The limit is fixed at 0 by this node.

MailerLite: Count Categories

mailerlite_count_categories

Return the number of categories in a shop as a single number. limit=0 is a distinct MailerLite operation returning {"total": 123} with no data array and no meta. The limit is fixed at 0 by this node.

MailerLite: Count Customers

mailerlite_count_customers

Return the number of customers in a shop as a single number. limit=0 is a distinct MailerLite operation returning {"total": 123} with no data array and no meta. The limit is fixed at 0 by this node.

MailerLite: Count Orders

mailerlite_count_orders

Return the number of orders in a shop as a single number. limit=0 is a distinct MailerLite operation returning {"total": 123} with no data array and no meta, and it is far cheaper than paging orders, whose rows are large. The limit is fixed at 0 by this node.

MailerLite: Count Products

mailerlite_count_products

Return the number of products in a shop as a single number. limit=0 is a distinct MailerLite operation returning {"total": 123} with no data array and no meta, and it is the cheap way to check whether a catalogue sync landed. The limit is fixed at 0 by this node.

MailerLite: Count Shops

mailerlite_count_shops

Return the number of connected shops as a single number. MailerLite documents limit=0 as its own operation returning {"total": 100} with no data array and no meta. The limit is fixed at 0 by this node.

MailerLite: Count Subscribers

mailerlite_count_subscribers

Return the total number of subscribers on the account as a single number. MailerLite documents limit=0 as its own operation with its own response body, {"total": 100}, carrying no data array, no links and no meta. It is the cheap way to branch on list size without paging anything. The limit is fixed at 0 by this node and cannot be changed.

MailerLite: Get Automation

mailerlite_get_automation

Fetch one automation with its steps, triggers, warnings and stats. Two fields are worth branching on: broken on a trigger says the trigger references something that no longer exists, for example a deleted group, and has_banned_content says MailerLite has flagged the automation's content. Returns 404 for an unknown id.

MailerLite: Get Automation Activity

mailerlite_get_automation_activity

List the subscribers currently in, or previously through, one automation, with the step each is on and the step it is waiting for. Status is REQUIRED here, and it also decides which pair of date filters applies: Date From and Date To filter the completed, canceled and failed statuses, while Scheduled From and Scheduled To filter the active status. Sending the wrong pair for the status silently returns an unfiltered window rather than an error, so match them deliberately. This endpoint is PAGE paged.

MailerLite: Get Campaign

mailerlite_get_campaign

Fetch one campaign in full, including its emails array with subject, sender, plain-text body and per-email stats, its audience filter in both machine and human readable form, and every schedule timestamp from queued_at through finished_at. Returns 404 for an unknown id.

MailerLite: Get Campaign Subscriber Activity

mailerlite_get_campaign_subscriber_activity

Per-recipient results for a SENT campaign: who opened, who clicked, who unsubscribed, who bounced and who marked it as spam, with each person's open and click counts. The campaign must have status sent. Beyond the rows, meta.aggregations carries the whole-campaign totals for every outcome in one object, which is usually what a dashboard wants. This endpoint is PAGE paged and its limit accepts only 10, 25, 50 or 100.

MailerLite: Get Cart

mailerlite_get_cart

Fetch one cart with its customer and its line items, each item carrying the full product record. Returns 404 when the shop or the cart cannot be found.

MailerLite: Get Cart Item

mailerlite_get_cart_item

Fetch one cart line item with its quantity, recorded price, variant and full product record. This is the deepest path on the API and it needs all three ids. Returns 404 when the shop, the cart or the item cannot be found.

MailerLite: Get Category

mailerlite_get_category

Fetch one category by id. The category record itself does not carry its products; use MailerLite: List Category Products for those. Returns 404 when the shop or the category cannot be found.

MailerLite: Get Customer

mailerlite_get_customer

Fetch one shop customer, with the linked subscriber embedded in full when one exists and null when it does not. Returns 404 when the shop or the customer cannot be found.

MailerLite: Get Form

mailerlite_get_form

Fetch one form by id, with its slug, its conversion stats and its double opt-in setting. Note that the id alone is enough here even though the LISTER needs a type, so a workflow holding a form id does not need to know its type.

MailerLite: Get Import Report

mailerlite_get_import

Read the progress and outcome of a subscriber import. MailerLite: Import Subscribers to Group returns an import_progress_url whose trailing id goes here. The report carries done, percent, and counts split by outcome: imported, updated, errored, invalid, mistyped, unchanged, unsubscribed, role_based and banned, each with a sample array of up to five addresses. Poll this until done is true rather than assuming an import finished when the request that started it returned.

MailerLite: Get Order

mailerlite_get_order

Fetch one order with its customer, its linked subscriber and its full cart of line items. Returns 404 when the shop or the order cannot be found.

MailerLite: Get Product

mailerlite_get_product

Fetch one product with its price, descriptions, image and full category list. Returns 404 when either the shop or the product cannot be found, so a 404 here does not tell you which of the two was wrong.

MailerLite: Get Shop

mailerlite_get_shop

Fetch one shop, with its currency and currency sign, its enabled flags and the group its customers are assigned to. Read the currency before writing prices anywhere else in this connector: every price on a product, cart or order is expressed in the SHOP's currency and carries no currency of its own.

MailerLite: Get Subscriber

mailerlite_get_subscriber

Fetch one subscriber by id OR by email address. The same path segment accepts either, which is what MailerLite's (:id or :email) notation means, so an automation holding only an address does not need a lookup step first. The address is URL encoded before it is sent. Returns 404 when no subscriber matches.

MailerLite: Get Subscriber Activity

mailerlite_get_subscriber_activity

Read one subscriber's activity log: campaign sends, automation emails, opens, clicks, bounces, spam complaints, unsubscribes, forwards and preference changes. Each row carries a log_name, a timestamp and a properties object whose shape depends on the log_name, so a workflow reading these should branch on log_name before touching properties. This endpoint is PAGE paged.

MailerLite: Get Webhook

mailerlite_get_webhook

Fetch one webhook by id. The signing secret is blanked, as on every webhook node here. Returns 404 for an unknown id.

MailerLite: List Automations

mailerlite_list_automations

List automations with their full step tree, their triggers and their aggregate stats. Each step carries a human readable description, so a workflow can report what an automation actually does without interpreting the tree. The group filter is the useful one: it returns every automation whose trigger references a given group, which is how you find out what will fire before you add someone to it. This endpoint is PAGE paged.

MailerLite: List Campaign Languages

mailerlite_list_campaign_languages

List the languages a campaign's unsubscribe template can be rendered in, each with its id, two-letter shortcode, full ISO 639 tag, display name and text direction. The id is what the campaign nodes' Language field wants. This is a static reference list, it takes no parameters, and it is not paged.

MailerLite: List Campaigns

mailerlite_list_campaigns

List campaigns with their settings, audience filter, schedule timestamps and, for sent campaigns, the full per-email stats block: sends, unique opens, clicks, unsubscribes, spam complaints and hard and soft bounces. Note the default: with no status filter MailerLite returns READY campaigns only, not everything, so ask for sent or draft explicitly. This endpoint is PAGE paged.

MailerLite: List Cart Items

mailerlite_list_cart_items

List the line items of one cart, each with its quantity, the price actually recorded for it, its variant text and the full product record. The item price is a snapshot of what was charged and does not follow later changes to the product's own price. This endpoint is PAGE paged.

MailerLite: List Carts

mailerlite_list_carts

List a shop's carts with their checkout URL, total, customer and line items. This is the abandoned-cart view: the checkout_url on each row is the link an abandoned-cart email sends people back to. Each cart also carries ecommerce_order_id linking it to its order. This endpoint is PAGE paged.

MailerLite: List Categories

mailerlite_list_categories

List a shop's product categories. A category is flat, with a name and an exclude_from_automations flag, and it exists so campaigns and automations can target a group of products at once. This endpoint is PAGE paged.

MailerLite: List Category Products

mailerlite_list_category_products

List the products assigned to one category. Each row is the full product record, including its OTHER category memberships, so this is also how you see the whole categorisation of a product from one end. This endpoint is PAGE paged.

MailerLite: List Customers

mailerlite_list_customers

List a shop's customers, each with its marketing-consent flag and the SUBSCRIBER it is linked to. That link is the whole point of the e-commerce customer record: it is what joins a purchase to a mailing list identity. The subscriber field is null when no subscriber exists for that address, so always branch on it rather than reaching straight into it. This endpoint is PAGE paged.

MailerLite: List Fields

mailerlite_list_fields

List the subscriber fields on the account, both MailerLite's defaults and your custom ones. The KEY is the important column: a subscriber's fields object is keyed by key, not by display name, so this is the node to read before writing anything into a subscriber's fields. MailerLite derives the key from the name and the two can drift apart after a rename. This endpoint is PAGE paged.

MailerLite: List Form Subscribers

mailerlite_list_form_subscribers

List the people who signed up through one form. Defaults to active subscribers, so ask for another status explicitly if you want the people who later unsubscribed. This is the attribution view: it answers which form produced which subscriber, which the account-wide subscriber list cannot. This endpoint is CURSOR paged, using meta.next_cursor.

MailerLite: List Forms

mailerlite_list_forms

List the account's signup forms of ONE type with their visitor, conversion and open counts and their conversion rate. The type is part of the path and is required, so listing every form on an account means three calls: popup, embedded and promotion. The response's meta.aggregations gives the count of each type in one go, which is a cheap way to know whether the other two are worth calling. Also worth branching on: is_broken flags a form that no longer works, and used_in_automations says whether deleting it would damage something. This endpoint is PAGE paged.

MailerLite: List Group Subscribers

mailerlite_list_group_subscribers

List the subscribers in one group. Defaults to active subscribers only, so pass a status explicitly when you want the unsubscribed or bounced members too. This endpoint is CURSOR paged, using meta.next_cursor, and takes up to 1000 rows per page, which is higher than the account-wide subscriber list allows.

MailerLite: List Groups

mailerlite_list_groups

List the account's groups with their membership counts and engagement rates broken down by status: active, unsubscribed, unconfirmed, bounced and junk. An account can hold at most 1000 groups. This is the node every group picker in this connector reads from, and it is PAGE paged.

MailerLite: List Orders

mailerlite_list_orders

List a shop's orders, each with its shop, its customer and the customer's linked subscriber, and its cart with every line item and product expanded. That makes each row large but self-contained, so a workflow rarely needs a follow-up read. Note that MailerLite offers no date filter on this endpoint: it is PAGE paged and nothing more, so an incremental sync has to page and compare timestamps itself.

MailerLite: List Products

mailerlite_list_products

List a shop's products with their price, URL, image and the categories each belongs to. Prices are in the SHOP's currency and carry no currency of their own. This endpoint is PAGE paged and it is the node the product pickers on the cart and category nodes read from.

MailerLite: List Segment Subscribers

mailerlite_list_segment_subscribers

List the subscribers currently matching a segment's rule. Defaults to active subscribers. This endpoint is the one MailerLite gives TWO forward-paging mechanisms: a Cursor, read from meta.next_cursor, and an After field taking the last subscriber id from meta.last. Use one or the other, not both. Because a segment is a live rule, a long paging run can see membership change underneath it.

MailerLite: List Segments

mailerlite_list_segments

List the account's segments with their current member count and their open and click rates. A segment is a saved rule rather than a fixed list, so total moves on its own as subscribers come to match or stop matching. An account can hold at most 250 segments. This is the node every segment picker reads from, and it is PAGE paged.

MailerLite: List Shops

mailerlite_list_shops

List the e-commerce shops connected to the MailerLite account, each with its URL, ISO 4217 currency, whether e-commerce features are enabled for it, and the group new customers are added to. This is the first call in almost every e-commerce workflow, because every other e-commerce path is scoped to a shop id. It is PAGE paged.

MailerLite: List Subscribers

mailerlite_list_subscribers

List the subscribers on the account, newest first, with each subscriber's status, source, lifetime send and engagement counts and the values of every custom field. This endpoint is CURSOR paged: pass the response's meta.next_cursor back in the Cursor field to walk forward. It reports no page numbers and no total, so use MailerLite: Count Subscribers when you need a number rather than a list.

MailerLite: List Timezones

mailerlite_list_timezones

List every timezone MailerLite recognises, each with its id, IANA name, human readable name and UTC offset. The id is what the campaign schedule fields want; the offset is a snapshot rather than a rule, so do not use this to do your own daylight-saving arithmetic. This is a static reference list, it takes no parameters, and it is not paged.

MailerLite: List Webhooks

mailerlite_list_webhooks

List the webhooks configured on the MailerLite account, with their target URL, subscribed events, enabled flag and batchable flag. Each webhook's signing secret is blanked by this connector on every node: it is the key that proves a delivery is genuine, and a workflow that logged its own output would otherwise publish it. Read it in the MailerLite dashboard when you need it for signature verification. This endpoint takes no parameters and is not paged.

Action nodes 52

MailerLite: Add Cart Item

mailerlite_add_cart_item

Add a line item to an existing cart. The product must already exist in this shop. Price is the amount actually charged for this line and is recorded independently of the product's current price, which is what keeps historic carts accurate after a price change. Changing a cart is what abandoned-cart automations watch, so this can affect what gets sent to the shopper.

MailerLite: Assign Product to Category

mailerlite_assign_product_to_category

Add one product to one category. All three ids go in the path and there is no request body. A product can belong to several categories, and this adds one membership rather than replacing them, so it is safe to run repeatedly. Reverse it with MailerLite: Unassign Product from Category.

MailerLite: Assign Subscriber to Group

mailerlite_assign_subscriber_to_group

Add one existing subscriber to one group, leaving their other memberships alone. Both ids go in the path and there is no request body. Joining a group is a MailerLite automation trigger, so this node can start an automation and therefore cause an email to be sent to a real person. Answers 200 or 201; the body is the group, not the subscriber.

MailerLite: Cancel Campaign

mailerlite_cancel_campaign

Return a scheduled campaign to draft before it goes out. This only works while the campaign is in the READY state: MailerLite answers 400 Bad Request for a campaign in any other state, which includes one that has already started sending. There is no way to recall mail that has been sent. Pair it with MailerLite: Schedule or Send Campaign as the stop half of a scheduled send.

MailerLite: Create Campaign

mailerlite_create_campaign

Create a campaign as a draft. Creating one sends nothing: delivery is a separate, explicit step through MailerLite: Schedule Campaign. Three constraints are worth knowing before you build the body. The sender address in emails[].from must already be VERIFIED on the MailerLite account or the call is rejected. Supplying emails[].content as raw HTML requires MailerLite's Advanced plan, and the body must carry an unsubscribe link, the account name, address and country or MailerLite appends its default footer. The resend and multivariate campaign types need a Growing or Advanced plan; regular and ab do not. If you pass both groups and segments, only segments are used.

MailerLite: Create Category

mailerlite_create_category

Create a product category in a shop. Categories are flat, with no parent and no nesting. Setting exclude_from_automations true keeps every product in the category from triggering automations, which is the wholesale version of the same flag on a product. Products are attached afterwards with MailerLite: Assign Product to Category, or in bulk with MailerLite: Import Categories.

MailerLite: Create Customer

mailerlite_create_customer

Create a customer on a shop. Two linking behaviours matter. If a subscriber already exists with the same email address, the customer is associated with that subscriber automatically, so this is not a way to keep purchase data separate from the mailing list. And setting create_subscriber true will ADD the person to the mailing list, which can start an automation and therefore send them email; only set it when the customer actually consented, which is what accepts_marketing is for recording.

MailerLite: Create Draft Automation

mailerlite_create_automation

Create an empty, disabled automation with a name. That is the whole endpoint: MailerLite's API exposes no way to add a step, edit a step, set a trigger or enable an automation, so the result is a placeholder that a person finishes in the MailerLite app. It sends nothing and it cannot send anything until someone enables it there. Like MailerLite: Create Group this is not an upsert, so a retry creates a second automation with the same name.

MailerLite: Create Field

mailerlite_create_field

Create a custom subscriber field. The type is fixed at creation: MailerLite offers no way to change a field from text to number or date afterwards, so picking wrong means deleting the field, which discards every value stored in it. The response carries the generated key, which is what subscriber payloads are keyed by. This is not an upsert, so a retry creates a second field with the same name.

MailerLite: Create Group

mailerlite_create_group

Create a group. Note that this is NOT an upsert: MailerLite does not match on name, so running this twice with the same name gives you two groups with the same name and different ids. On an API with no idempotency keys that makes a retry unsafe, so check MailerLite: List Groups with a name filter first if the workflow can run more than once.

MailerLite: Create Order

mailerlite_create_order

Create an order, which also creates its customer and its cart in one call. This is the ONLY way to create a cart on this API: carts have no create endpoint of their own. The customer is created if no customer holds that email already. Two consequences worth planning for: passing create_subscriber true inside the customer object adds the buyer to the mailing list, and a new order is what MailerLite's post-purchase and abandoned-cart automations watch for, so this node can cause email to be sent to a real person.

MailerLite: Create Product

mailerlite_create_product

Add a product to a shop's MailerLite catalogue, which is what lets campaigns embed it and what abandoned-cart automations refer to. Price is in the shop's currency. Two details from MailerLite: HTML tags are stripped from both description fields automatically, and short_description is capped at 255 characters. Setting exclude_from_automations true keeps this product from triggering any automation, which is the switch to use for test rows and for items you never want to chase carts about. Use MailerLite: Import Products for more than a handful.

MailerLite: Create Shop

mailerlite_create_shop

Connect an external shop to MailerLite. This is what unlocks the e-commerce features on the account: abandoned cart and post-purchase automations, product blocks inside campaigns and revenue tracking. Currency is fixed here in ISO 4217 and is what every price on this shop's products, carts and orders is denominated in. Note that enabled defaults to FALSE, so a shop created without it is connected but inert. MailerLite's access_data parameter, which carries platform-specific credentials for its own Shopify and WooCommerce integrations, is deliberately not exposed here: MailerLite's own documentation says third-party users should not need it, and this connector does not store shop platform credentials.

MailerLite: Create Webhook

mailerlite_create_webhook

Register a webhook so MailerLite pushes events to a URL instead of you polling for them. Three delivery facts shape how the receiving endpoint must behave: MailerLite treats any non 2xx response as a failure and retries three times at 10, 100 and 1000 seconds, it treats anything slower than 3 seconds as a failure too, and it signs every delivery with an HMAC-SHA256 of the JSON body in a Signature header. So do the real work asynchronously and answer 2xx quickly, or you will receive duplicates. Three events, campaign.open, campaign.click and subscriber.deleted, require Batchable set to true and will not work without it. Webhooks are the one thing MailerLite's batch endpoint does not support.

MailerLite: Create or Update Subscriber

mailerlite_create_subscriber

Add a subscriber, or update the one that already holds this email address. This is an UPSERT and it is the safe retry path on an API with no idempotency keys: MailerLite answers 201 when it created the subscriber and 200 when it matched an existing one, so calling it twice does not produce a duplicate. It is also non-destructive by design, meaning omitting a field or a group leaves the existing value alone rather than clearing it. Use MailerLite: Update Subscriber when you need group membership replaced instead of added to. Adding someone to a group can start an automation whose first step is an email, so this node can cause mail to be sent to a real person.

MailerLite: Delete Automation

mailerlite_delete_automation

Delete an automation and everything it recorded. Any subscribers currently partway through it stop where they are, and the completed-run history goes with it, so a welcome series that has run for a year loses its reporting. MailerLite offers no undelete and no archive here. Answers 204 on success.

MailerLite: Delete Campaign

mailerlite_delete_campaign

Delete a campaign. Deleting a SENT campaign takes its reporting with it, so the open, click and bounce history for that send is gone from the account and from every subscriber's activity view. Export anything you need first. Answers 204 on success and 404 for an unknown id, with no undelete.

MailerLite: Delete Cart Item

mailerlite_delete_cart_item

Remove one line item from a cart. The cart, the product and the order all survive; only the line goes. The cart's stored total is not recomputed, so follow this with MailerLite: Update Cart if the total matters. Re-adding the item with MailerLite: Add Cart Item recreates it with a NEW id. Answers 404 when the shop, cart or item cannot be found.

MailerLite: Delete Category

mailerlite_delete_category

Delete a category. The products in it are not deleted, they simply stop being categorised, but any campaign block or automation that targeted the category loses its target. There is no undelete. Answers 404 when the shop or the category cannot be found.

MailerLite: Delete Customer

mailerlite_delete_customer

Delete a shop customer. MailerLite is explicit that the linked SUBSCRIBER is not deleted or affected, so this removes the purchase identity and leaves the mailing-list identity in place. That means it is not a GDPR erasure: use MailerLite: Forget Subscriber for that. There is no undelete. Answers 404 when the shop or the customer cannot be found.

MailerLite: Delete Field

mailerlite_delete_field

Delete a custom field. Every VALUE stored in it, across every subscriber on the account, goes with it, and there is no undelete and no export step built into this endpoint. Anything referencing the field breaks too: personalisation tags in campaign content, automation conditions and segment rules that test it. Export the values first if they matter. Answers 204 on success and 404 for an unknown id.

MailerLite: Delete Form

mailerlite_delete_form

Delete a form. Anywhere it is embedded stops collecting signups, which is a change to a live website rather than just to MailerLite. Read the form first and check used_in_automations: a form an automation depends on will leave that automation with a broken trigger. Answers 204 on success and 404 for an unknown id, with no undelete.

MailerLite: Delete Group

mailerlite_delete_group

Delete a group. The subscribers in it are not deleted, they simply stop belonging to it. Anything that targeted the group loses that targeting, which is the real cost here: an automation triggered by joining this group, a form that assigns to it, or a campaign filtered on it all reference a group that no longer exists. Answers 204 on success and 404 when the id is unknown. There is no undelete.

MailerLite: Delete Order

mailerlite_delete_order

Delete an order. MailerLite deletes the associated CART and all of its CART ITEMS with it, which is the only way a cart is ever removed on this API. The customer survives. Revenue attributed to this order disappears from the shop's reporting, and there is no undelete. Answers 404 when the shop or the order cannot be found.

MailerLite: Delete Product

mailerlite_delete_product

Delete a product from a shop's MailerLite catalogue. Any campaign block or automation that referred to it loses its reference, and there is no undelete. To retire a product without breaking those references, set exclude_from_automations true with MailerLite: Update Product instead. Answers 404 when the shop or the product cannot be found.

MailerLite: Delete Segment

mailerlite_delete_segment

Delete a segment. The subscribers it matched are untouched, but the RULE is gone and cannot be recovered through the API, which is the real loss: MailerLite exposes no endpoint that reads a segment's conditions, so there is nothing to back up first and nothing to rebuild it from. Any campaign targeting it loses that targeting. Answers 204 on success.

MailerLite: Delete Shop

mailerlite_delete_shop

Delete a shop. This is the widest-blast-radius call in the connector: everything scoped under the shop, meaning its products, categories, customers, orders, carts and cart items, is scoped to a shop that no longer exists, and MailerLite documents no undelete. Any e-commerce automation or campaign product block that depended on it stops working. If the goal is to stop the integration, set Enabled to false with MailerLite: Update Shop instead.

MailerLite: Delete Subscriber

mailerlite_delete_subscriber

Remove a subscriber from the account. MailerLite keeps their information in case they subscribe again, so this is the gentler of the two removals; use MailerLite: Forget Subscriber for a GDPR erasure. Answers 204 No Content on success and 404 when the id does not exist. There is no undelete on this API.

MailerLite: Delete Webhook

mailerlite_delete_webhook

Delete a webhook. Deliveries stop at once and the signing secret is gone, so recreating it later produces a NEW secret and any receiver that pinned the old one must be updated. If you only want to stop deliveries for a while, set Enabled to false with MailerLite: Update Webhook instead. Answers 204 on success.

MailerLite: Forget Subscriber

mailerlite_forget_subscriber

Erase a subscriber. MailerLite removes them from the account immediately and deletes all of their information within 30 days, which is the GDPR erasure path rather than the ordinary delete. It cannot be reversed once the 30 days elapse, and the response is the last full copy of the record you will see, so capture anything you must retain for your own compliance records before running it. Use MailerLite: Delete Subscriber when you only want them off the list.

MailerLite: Import Categories

mailerlite_import_categories

Create many categories in a shop in one call. The whole request body is a bare JSON ARRAY of category objects, not an object with a key, which is unlike every other write on this API. The response is the array of created categories with their new ids, so a follow-up read is not needed. Validation errors are reported per position, for example "0.name" for the first element.

MailerLite: Import Orders

mailerlite_import_orders

Create many orders in one call, each bringing its customer, its cart and its cart items with it. The whole request body is a bare JSON ARRAY, not an object with a key. Treat this as a sending action: every element carrying create_subscriber true adds a person to the mailing list, and a batch of new orders is exactly what MailerLite's post-purchase automations react to, so a historical backfill run against a live account can mail every buyer in the file. Turn the relevant automations off, or exclude the products, before importing history.

MailerLite: Import Products

mailerlite_import_products

Create many products in a shop in one call, each optionally attached to existing categories by id. The whole request body is a bare JSON ARRAY, not an object with a key. This is the node for an initial catalogue sync: it is one request against the 120 per minute limit rather than one per product. Categories named here must already exist; create them first with MailerLite: Import Categories.

MailerLite: Import Subscribers to Group

mailerlite_import_subscribers_to_group

Bulk import subscribers into a group in one call. Two things make this different from looping the create node. First, it runs on its own rate limit of 5 requests per minute per API token, separate from the global 120 per minute, and it says so when you exceed it with the message "You're being rate limited on import creation.". Second, it is asynchronous: the response is an import_progress_url rather than a result, and the work is still running. Feed that id to MailerLite: Get Import Report and poll until done is true. Importing into a group can start an automation and therefore send mail to every address in the file, so treat this as a sending action.

MailerLite: Run Batch Request

mailerlite_batch

Run up to 50 MailerLite API calls in one request. This is the intended answer to the 120 requests per minute limit: it counts as one request rather than fifty. Four rules govern it. Each item's path must start with api/, for example api/subscribers. Responses come back in the SAME ORDER the items were sent, each with its own code and body. A failing item does not fail the batch, so the call returns 200 while an individual item carries a 422, and a workflow must inspect responses[] rather than trusting the outer status. Webhooks are explicitly unsupported inside a batch. One more trap: a batch made ENTIRELY of subscriber upserts is treated as an import and falls under the separate 5 requests per minute import limit.

MailerLite: Schedule or Send Campaign

mailerlite_schedule_campaign

THIS NODE SENDS EMAIL TO REAL PEOPLE. With delivery set to instant it mails the campaign's entire audience immediately; the other delivery modes set a future time. There is no dry run, no test-recipient option and no undo. MailerLite: Cancel Campaign only works while the campaign is in the ready state, so once sending starts nothing can stop it. Check the audience with MailerLite: Get Campaign before wiring this into anything that runs unattended. Sending through the API requires a paid MailerLite plan: on the free plan API access is limited and does not include sending, so this node will not deliver mail there.

MailerLite: Unassign Product from Category

mailerlite_unassign_product_from_category

Remove one product from one category. Neither the product nor the category is deleted and the product's other category memberships are untouched, so this is fully reversible with MailerLite: Assign Product to Category. Answers 404 when any of the three ids cannot be found.

MailerLite: Unassign Subscriber from Group

mailerlite_unassign_subscriber_from_group

Remove one subscriber from one group. The subscriber is not deleted and their other group memberships are untouched, so this is reversible with MailerLite: Assign Subscriber to Group. Leaving a group is also an automation trigger in MailerLite. Answers 204 on success and 404 when either id is unknown.

MailerLite: Update Campaign

mailerlite_update_campaign

Update a campaign that is still a DRAFT. MailerLite returns 422 for a campaign in any other status, which means a ready or sent campaign cannot be edited through the API at all. Name and emails are both required on every update, so read the campaign first and send its current values back unless you mean to change them. The type cannot be changed here.

MailerLite: Update Cart

mailerlite_update_cart

Update a cart's checkout URL or its total. The checkout URL is the field that matters: it is the link an abandoned-cart automation puts in front of the shopper, so a stale or expired one is the difference between a recovered sale and a broken link. Line items are not edited here; use the cart item nodes. Carts cannot be created or deleted directly.

MailerLite: Update Cart Item

mailerlite_update_cart_item

Update one line item on a cart: its quantity, its recorded price, its variant text, or the product it points at. MailerLite requires the product id on this endpoint, so read the item first and send its current product back unless you mean to change it. Updating an item does not recompute the cart's total; set that with MailerLite: Update Cart.

MailerLite: Update Category

mailerlite_update_category

Update a category's name or its automation exclusion. Name is required by MailerLite on every update, so send the current name back unless you mean to change it. Membership is not edited here.

MailerLite: Update Customer

mailerlite_update_customer

Update a shop customer, typically to refresh total_spent or to record a change of marketing consent. MailerLite spells out what create_subscriber does here: set true on a customer with no subscriber and it CREATES one, which puts the person on the mailing list; set false on a customer that already has one and nothing happens, because it does not unlink or delete the subscriber. So this flag only ever adds, and removing someone is done through the subscriber nodes.

MailerLite: Update Field

mailerlite_update_field

Rename a custom field. Only the display name changes: the type cannot be changed here, and the stored KEY that subscriber payloads use does not necessarily follow the new name. Re-read MailerLite: List Fields after a rename rather than assuming the key tracks it.

MailerLite: Update Form

mailerlite_update_form

Rename a form. Name is the only property this endpoint accepts: the form's fields, design, targeting and double opt-in setting are all edited in the MailerLite app and are not exposed here.

MailerLite: Update Group

mailerlite_update_group

Rename a group. Name is the only property a group has, so this endpoint changes nothing about membership and nothing about the automations or forms that reference the group.

MailerLite: Update Order

mailerlite_update_order

Update an order's status or total, which is how a pending order becomes complete and how a post-purchase automation learns the sale went through. MailerLite is explicit that the CART and the CUSTOMER cannot be changed here: edit those through MailerLite: Update Cart, the cart item nodes and MailerLite: Update Customer instead. Those two fields are therefore not offered on this node.

MailerLite: Update Product

mailerlite_update_product

Update a product. Name is required by MailerLite on every update, so read the product first and send its current name back unless you mean to change it. Category membership is NOT set here: use MailerLite: Assign Product to Category. Changing a price does not change the price recorded on carts or orders that already exist, which is correct, since those record what was actually charged.

MailerLite: Update Segment

mailerlite_update_segment

Rename a segment. Name is the only property this endpoint accepts, and MailerLite's API exposes no way to read or change a segment's CONDITIONS, so the rule that decides membership is edited in the app only.

MailerLite: Update Shop

mailerlite_update_shop

Update a connected shop. The reversible switch worth knowing is Enabled: setting it false turns the shop's e-commerce features off without deleting any of its products, orders or customers, which is the safe way to pause an integration. MailerLite requires name, url and currency on this endpoint, so read the shop first and send its current values back unless you mean to change them. Changing the currency does not convert any price already stored.

MailerLite: Update Subscriber

mailerlite_update_subscriber

Update one existing subscriber by id. Two differences from MailerLite: Create or Update Subscriber matter. First, groups here REPLACE the subscriber's memberships: any group not listed is removed, which is the opposite of the create node's additive behaviour. Second, MailerLite refuses to reactivate anyone whose status is unsubscribed, bounced or junk, as an abuse-prevention measure; those people can only come back through the app, a form or a landing page. The email address itself cannot be changed here.

MailerLite: Update Webhook

mailerlite_update_webhook

Update a webhook: change its URL, replace its event list, or turn it off and on again with Enabled, which is the reversible way to stop deliveries during maintenance instead of deleting and recreating it. Sending Events REPLACES the subscribed list rather than adding to it, so include every event you still want. The signing secret does not change and is blanked in the response.

Using the integration

Sending, and the free plan boundary

One node in this integration mails real people: MailerLite: Schedule or Send Campaign. With delivery set to instant it sends to the campaign's entire audience immediately, and MailerLite offers no dry run, no test-recipient option and no recall. The node's delivery field therefore defaults to scheduled rather than instant, and the node is flagged destructive so it stands out in an approval flow. MailerLite: Cancel Campaign is only half an undo: MailerLite accepts it while the campaign is in the ready state and answers 400 for a campaign in any other state, including one that has already started sending. Six more nodes can send indirectly by starting an automation whose first step is an email, and each says so on itself: MailerLite: Create or Update Subscriber, MailerLite: Assign Subscriber to Group, MailerLite: Import Subscribers to Group, MailerLite: Create Customer, MailerLite: Create Order and MailerLite: Import Orders. The strongest warning is on MailerLite: Import Orders, because a historical backfill against a live account is exactly what post-purchase automations react to and can mail every buyer in the file. Turn the relevant automations off before importing history. All of this sits behind one plan boundary: MailerLite's pricing FAQ states that email sending via the API and MCP server is available on paid plans, and that on Free, API and MCP access is limited and does not include sending, so a free account can build and manage everything here and cannot deliver.

The two pagination shapes, and the loop they break

MailerLite paginates two different ways and does not unify them. Four nodes are cursor paged: MailerLite: List Subscribers, MailerLite: List Group Subscribers, MailerLite: List Form Subscribers and MailerLite: List Segment Subscribers. They take a cursor, return a next cursor in the response metadata, and report no page numbers and no total. Everything else is page numbered: fields, groups, segments, campaigns, automations, forms, both activity logs and every e-commerce list take a page number and report a current page, a last page and a total. The reason this deserves attention rather than a footnote is that sending the wrong parameter is ignored rather than rejected. A cursor sent to a page-numbered endpoint re-reads the first page forever, a page number sent to a cursor endpoint re-reads the first slice forever, and both answer HTTP 200 the whole time. This integration refuses to paper over it: each node declares only the parameter its own endpoint accepts, and its sample output carries that endpoint's real metadata shape, so the canvas offers a next cursor on one set of nodes and a last page on the other rather than offering both everywhere. MailerLite: List Segment Subscribers is the one node carrying two forward mechanisms, a cursor and an after field taking the last subscriber id, because MailerLite documents both and expects you to pick one.

Rate limits, and the one that catches bulk workflows

MailerLite documents a global limit of 120 requests per minute, with limit, remaining and retry-after headers on the response and a message of Too Many Attempts when it trips. There is a second limit that is easier to hit and harder to diagnose: import endpoints allow 5 requests per minute. It applies to MailerLite: Import Subscribers to Group and, less obviously, to any batch whose items are all subscriber upserts, because MailerLite processes that batch as an import internally. So the endpoint you called does not tell you which limit you hit, which is why this integration reads the message rather than guessing from the path, and attaches a different hint for each. The fixes are genuinely different: back off a few seconds for the global limit, but restructure the workflow for the import limit, because pacing does not fix a shape that fires imports in a loop. MailerLite: Run Batch Request is MailerLite's own answer to the global limit, folding up to 50 calls into one request that counts once. Four rules govern it: every item path must start with api, responses come back in the order the items were sent, webhooks are explicitly unsupported inside a batch, and a failing item does not fail the batch. That last one matters for workflow design: the call returns 200 while an individual item carries its own 422 inside the responses array, so a branch on the outer status alone treats a half-failed batch as a success.

Retries, upserts and the endpoints that duplicate

MailerLite documents no idempotency mechanism anywhere on this API, so the safety of a retry depends entirely on which endpoint you are calling, and this integration says which on each node rather than leaving it to be discovered. Safe to retry: MailerLite: Create or Update Subscriber is a true upsert, answering 201 when it created the person and 200 when it matched an existing address, and the e-commerce creates for shops, products, categories, customers and orders are documented by MailerLite as create-or-update too. Not safe to retry: MailerLite: Create Group, MailerLite: Create Field, MailerLite: Create Draft Automation and MailerLite: Create Webhook do not match on name, so running one twice leaves you with two records carrying the same name and different ids. If a workflow can run more than once, and a form-submission workflow always can, read the collection first or key the write on something you control. One more behaviour worth planning for: MailerLite answers 202 Accepted when it has taken the request and will finish the work in the background, which is a success in the envelope for work that has not happened yet. The group import is the concrete case, returning a progress URL rather than a result, and MailerLite: Get Import Report is the node that says whether it actually finished.

The e-commerce surface, and why every path needs a shop

Forty six nodes cover MailerLite's e-commerce data, and every path below the shops collection is scoped to a shop id, down to a single line item on a single cart. So MailerLite: List Shops is the first call in almost every e-commerce workflow, and shop id is a required, picker-backed field on the 43 nodes that sit below the shops collection, with every deeper picker chaining off it. Read the shop's currency before writing prices anywhere: every price on a product, cart or order is expressed in the shop's currency and carries none of its own. Two structural facts shape what is possible. Carts have no create endpoint: MailerLite: Create Order is the only way one comes into existence, creating the order, its customer and its cart in one call, and MailerLite deletes the cart and its items along with the order. And MailerLite: Update Order cannot change an order's cart or customer, which MailerLite states outright, so those two fields are deliberately not offered on the node and the description names MailerLite: Update Cart and MailerLite: Update Customer instead. One thing to expect in testing: the e-commerce 404 is ambiguous by design, returning the same status and body whether the shop was not found or the record inside it was not found, so re-confirm the shop id before recording a child endpoint as broken.

Counting without paging

MailerLite documents a limit of zero as its own distinct operation on most collections, with its own request rule and its own response body: a single total, with no rows, no links and no metadata. Eight nodes here expose it: MailerLite: Count Subscribers, MailerLite: Count Shops, MailerLite: Count Products, MailerLite: Count Categories, MailerLite: Count Customers, MailerLite: Count Orders, MailerLite: Count Carts and MailerLite: Count Cart Items. They are the cheap way to branch on size, to check whether a catalogue sync landed, or to decide whether a nightly job has anything to do, and they cost one request instead of a walk. The count nodes carry no limit field at all, because the value is fixed by the connector after everything else including any extra query parameters, so a count node cannot be turned into a one-row list from configuration. Two notes on reading them. MailerLite: Count Cart Items counts line items rather than units, so an item with a quantity of three counts once. And not every collection has one: MailerLite documents no count operation for groups, segments, fields, forms, campaigns, automations or webhooks, and none was invented here.

Incremental syncs, and why MailerLite makes them awkward

Sync only what changed is the first thing most people try, and this API does not support it. Nothing here accepts a created-after or an updated-after filter: MailerLite: List Subscribers filters on status and nothing else, and MailerLite: List Orders, MailerLite: List Products and every other e-commerce list offer paging and nothing more. That is a property of MailerLite's API rather than a gap in this integration, and it means an incremental sync has to page and compare timestamps on your side. The only windowed endpoint on the whole API is MailerLite: Get Automation Activity, and it is conditional rather than simple: status is required, and it decides which pair of date filters applies. The date from and date to fields filter the completed, canceled and failed statuses, while the scheduled from and scheduled to fields filter the active status. Sending the pair that does not match the status returns an unfiltered window rather than an error, so match them deliberately. Two things make the paging cheaper than it sounds: the count nodes tell you whether anything moved at all before you read a row, and MailerLite: Run Batch Request folds fifty reads into a single request against the limit.

Webhooks, and the secret this integration blanks

MailerLite can push events to you instead of being polled, and MailerLite: Create Webhook registers the endpoint. Three delivery facts shape how your receiver must behave: MailerLite treats any non-2xx response as a failure and retries three times at 10, 100 and 1000 seconds, it treats anything slower than 3 seconds as a failure too, and it signs every delivery with an HMAC-SHA256 of the JSON body in a signature header. So do the real work asynchronously and answer quickly, or you will receive duplicates. Three events, campaign open, campaign click and subscriber deleted, require the batchable flag and will not work without it. One deliberate limitation is worth stating plainly: MailerLite returns the webhook's signing secret in plaintext from four endpoints, and this integration blanks it on every node rather than only on the webhook ones, because a webhook object can also arrive inside a batch response. The cost is real: a workflow here cannot read the secret in order to verify a signature itself, and the way to get it is to read it in the MailerLite dashboard. That trade is deliberate, weighed against a credential ending up in a workflow log. Note also that this connector ships no trigger nodes, so MailerLite workflows in Mattering run on a schedule or start from another app's trigger, and a MailerLite webhook is received by an endpoint you provide.

Deletes, and which ones can be undone

None of MailerLite's deletes has an undo, so the useful distinction is what each one takes with it. Two are gentler than they look: MailerLite: Delete Subscriber removes somebody from the account while MailerLite keeps their information in case they subscribe again, and MailerLite: Delete Customer removes a purchase identity while MailerLite explicitly leaves the linked subscriber untouched, which means neither is a GDPR erasure. MailerLite: Forget Subscriber is the erasure: MailerLite removes the person immediately and deletes all of their information within 30 days, and the response is the last complete copy of the record you will see. Several deletes destroy more than their own row. MailerLite: Delete Field takes every value stored in that field across every subscriber, and breaks the personalisation tags, automation conditions and segment rules that reference it. MailerLite: Delete Campaign takes the send's whole reporting history with it. MailerLite: Delete Automation stops anyone partway through and discards the completed-run history. MailerLite: Delete Segment destroys a rule that MailerLite exposes no endpoint to read, so there is nothing to back up first and nothing to rebuild it from. MailerLite: Delete Shop has the widest blast radius in the integration. Where a reversible alternative exists, the node names it: set enabled to false with MailerLite: Update Shop to pause an integration, or set a product's automation exclusion with MailerLite: Update Product to retire it without breaking the campaign blocks that point at it.

From AI assistants over MCP, and MailerLite's own server

Every node here speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT and any MCP-capable assistant can drive the same surface, as can Matter, the assistant built into the platform. MailerLite also publishes its own hosted MCP server, at mcp.mailerlite.com, authorized with OAuth and supported in Claude, Claude Code, ChatGPT, Cursor, Gemini CLI and VS Code, and it is worth knowing what each is good at rather than pretending there is no choice. Their server ships authoring and validation features this integration has no equivalent for: discovering and installing templates, generating email content and subject lines, dry running and test sending an automation, and campaign link reporting the REST reference does not document. It also documents create_segment, get_segment and create_form as tools, and MailerLite's REST reference documents no POST to either the segments or the forms collection, so this integration does not ship those and does not claim parity on them. Going the other way, their counted list of 77 tools has no timezone reader, no campaign language reader, no subscriber forget, no import report reader and a count for subscribers only rather than for all eight collections that support one. The practical difference is not the tool count: it is that these nodes are also canvas steps, so the workflow an assistant helps you design then runs on a schedule with nobody present, chains with every other connector in one workflow, and holds the credential once in a shared workspace rather than in each person's local config. Given that one node mails a live audience, put MailerLite: Schedule or Send Campaign, MailerLite: Forget Subscriber and the deletes behind a condition or an approval step before handing an assistant the keys.

On the automation canvas

MailerLite nodes chain with every other node in Mattering. A Forms submission can run MailerLite: Create or Update Subscriber and then MailerLite: Assign Subscriber to Group, which is safe to retry because the first is an upsert and the second leaves other memberships alone. A shop event can call MailerLite: Create Order and keep MailerLite: Update Cart current so an abandoned-cart email carries a working checkout link. A weekly schedule can read MailerLite: List Campaigns with the status filter set to sent, since MailerLite returns ready campaigns only when the filter is empty, and write the numbers into a Mattering database or open a Productivity task for a person. The pickers do most of the wiring: group, segment, field, campaign, automation, webhook, timezone, language, form, shop, product, category, customer, order, cart and cart item fields all populate from the corresponding list node, with the e-commerce ones scoped by the shop you chose and the cart item picker scoped by both a shop and a cart. Two pickers carry deliberate decoration. The campaign picker is grouped by status, because schedule, cancel, update and delete behave completely differently on a draft, a ready and a sent campaign and one of them mails the list. The field picker is described by its key rather than only its display name, because a subscriber's fields object is keyed by key and two custom fields can share a display name. One field exists only to scope a picker and is never sent to MailerLite: form type, on the four form-scoped nodes, because MailerLite's form lister takes the type as a path segment and there is no single call that returns every form on an account.

Troubleshooting

Test Connection fails with a 401 and a body of Unauthenticated
MailerLite gives no detail in that response, so work through three causes in order. First, the token may be from MailerLite Classic, which is a separate product on a different host that authenticates with an X-MailerLite-ApiKey header rather than a bearer token. A Classic key can never work here and this is the most common cause. Second, the token may have been revoked or regenerated in MailerLite, in which case paste the current one onto the credential. Third, and the one that looks like a bug because nothing changed on your side: MailerLite states that API keys are permanently bound to the user who created them, so if that person was removed from the MailerLite account or their user account was deleted, the token stops authenticating from that moment. Generate a replacement from a user the business controls.
A node returns 403 while other nodes work fine
A 403 is a different finding from a 401 rather than a worse one: MailerLite defines it as the action being denied for that account or that token, and on this API that usually means a plan gate rather than a bad credential. The gate that catches most people is sending: MailerLite's pricing FAQ states that email sending via the API and MCP server is available on paid plans, and that on Free, API and MCP access is limited and does not include sending. Two more come from the campaign reference: the resend and multivariate campaign types need one of MailerLite's higher paid tiers, and supplying raw HTML as campaign content needs its top tier. Check MailerLite's current pricing page for which tier that is, because the tier names in the API reference and on the pricing page do not currently match. If the plan is not the cause, confirm the account can perform the same action in the MailerLite app.
A campaign was created and scheduled but no email arrived
Start with the plan, because it is the likeliest answer and it produces no obvious error in a workflow: MailerLite's pricing FAQ states that email sending via the API and MCP server is available on paid plans and that on Free it is excluded, so on a free account MailerLite: Schedule or Send Campaign will not deliver even though everything up to it worked. On a paid plan, check three things on the campaign itself. The sender address in the campaign's from field must already be verified on the MailerLite account. The delivery mode matters: the node defaults to scheduled rather than instant, deliberately, so a workflow that meant to send now has to say so. And read the campaign back with MailerLite: Get Campaign and look at its audience filter and its schedule timestamps, which run from queued through to finished, to see what state MailerLite actually put it in.
A paging loop never finishes and keeps returning the same rows
You are almost certainly sending the wrong paging parameter, and MailerLite ignores it rather than rejecting it, so every response is a perfectly valid HTTP 200. Four endpoints are cursor paged: the account subscriber list, and the group, form and segment subscriber lists. They take a cursor and return the next one in the response metadata, with no page numbers and no total. Everything else is page numbered and reports a current page, a last page and a total. A cursor sent to a page-numbered endpoint re-reads page one forever, and a page number sent to a cursor endpoint re-reads the first slice forever. Each node in this integration only offers the field its own endpoint accepts, so the fix is to map the loop to the field the node actually shows rather than the one you expected. On MailerLite: List Segment Subscribers, which offers both a cursor and an after field, pick one and leave the other empty.
Requests start failing with 429 partway through a run
Read the message, because there are two different limits and they need different fixes. Too Many Attempts is the global limit of 120 requests per minute, and the response carries limit, remaining and retry-after headers, so backing off for a few seconds is the right response. The message about being rate limited on import creation is the separate import limit of 5 requests per minute, and waiting does not fix that one: it applies to MailerLite: Import Subscribers to Group and, less obviously, to any batch whose items are all subscriber upserts, because MailerLite processes that batch as an import. So a workflow that loops the create-subscriber node to generate rows trips the import limit rather than the global one. The durable fix is shape: use MailerLite: Run Batch Request to fold up to 50 mixed calls into one request against the global limit, and use the count nodes instead of paging when all you need is a number.
A batch returned 200 but some of the work did not happen
That is MailerLite's documented behaviour rather than a fault. A failing item inside a batch does not fail the batch: the call answers 200 with a failed count, and the individual item's own status, typically a 422, sits inside the responses array. A workflow that branches on the outer status alone therefore treats a half-failed batch as a complete success. Inspect the responses array, which comes back in the same order the items were sent, and branch on each item's own code. Two other batch rules explain most of the rest: every item path must start with api, and webhooks are explicitly unsupported inside a batch, so a webhook item fails while the surrounding batch reports fine.
An import returned successfully but nobody appeared in the group
The import is asynchronous and the response tells you the request was accepted, not that the work finished. MailerLite defines 202 Accepted as the request having been accepted with further actions taken in the background, and MailerLite: Import Subscribers to Group returns a progress URL rather than a result. Take the id from the end of that URL and feed it to MailerLite: Get Import Report, then poll until it reports done. The report is the useful part: counts split by imported, updated, errored, invalid, mistyped, unchanged, unsubscribed, role based and banned, each with a sample of up to five addresses, which is usually enough to see what the file got wrong. If the import itself was rejected, check the 5 per minute import limit before checking the file.
An e-commerce node returns 404 and the id looks correct
MailerLite returns the same 404 whether the shop was not found or the record inside it was not found, and the body does not say which, so the ambiguity is by design rather than a missing detail. Re-confirm the shop first, with MailerLite: List Shops or MailerLite: Get Shop, before concluding that the product, order, cart or item is the problem. A stale shop id is the more common cause, because every e-commerce path is scoped to one and a shop deleted or recreated elsewhere leaves every downstream id pointing nowhere. On the cart item nodes, which need a shop, a cart and an item, check them in that order for the same reason.
A picker on a node stays empty or says to choose something first
Start with the node the picker reads from and run it on its own: if MailerLite: List Groups returns nothing, no group picker will populate either. If the message asks you to choose something first, a parent field is unset. The e-commerce pickers are scoped by shop, and the cart item picker is scoped by both a shop and a cart, so it asks for them one at a time. The form pickers are scoped by form type, which is a field that exists only to scope the picker and is never sent to MailerLite: it is there because MailerLite's form lister takes the type as a path segment, so there is no single call that returns every form on an account. A few fields are deliberately free text rather than broken pickers. Subscriber id is one: MailerLite's subscriber list has no name or email search parameter at all, filtering on status only, so a picker would be an unbounded list of every address on the account with nothing to search on, which is worse than a text box. Import id is another, because MailerLite documents no endpoint that lists imports.
A subscriber update did not take, or wiped their groups
The two subscriber write nodes behave differently on purpose and picking the wrong one accounts for most of these. MailerLite: Create or Update Subscriber is an upsert and is additive: omitting a field or a group leaves the existing value alone, which is what makes it safe to retry. MailerLite: Update Subscriber replaces group membership: any group not listed in the call is removed. So an update that appeared to wipe memberships usually sent a partial group list to the second node. Two more behaviours are MailerLite's own. It refuses to reactivate anyone whose status is unsubscribed, bounced or junk through the API, as an abuse-prevention measure, so those people can only return through the app, a form or a landing page. And the email address itself cannot be changed on the update node. If a custom field value did not take, read MailerLite: List Fields: a subscriber's fields object is keyed by the field key rather than its display name, and MailerLite derives the key at creation, so the two drift apart after a rename.

MailerLite is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products