Menu
Mattering Automations connector

A MailerLite MCP that runs on a schedule, not only in a chat

97 nodes across subscribers, groups, segments, custom fields, forms, campaigns, automations, webhooks and the complete e-commerce surface of shops, products, categories, customers, orders, carts and cart items. Forty five read and fifty two act. At least one node for every operation MailerLite documents, typed, with destructive flags on the ones that can mail real people.

97 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the MailerLite MCP connector does

The MailerLite connector for Mattering Automations is 97 nodes on MailerLite's current API at connect.mailerlite.com, covering all 92 operations its reference documents. Subscribers, groups, segments, custom fields and forms cover the list itself. Campaigns and automations cover what goes out and reporting on what already went out. Webhooks cover the push side. Shops, products, categories, customers, orders, carts and cart items cover the whole e-commerce surface, including the carts and cart items most integrations skip, which is exactly the data abandoned-cart automations run on.

Every capability is a node on the Automations canvas, and every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. The same node is also a step in a scheduled workflow, so the thing an assistant helps you work out at 4pm can run at 6am on Monday with nobody present, chained to every other connector in the workspace, on a credential the workspace holds rather than one sitting in an individual's local config.

MailerLite ships its own MCP server, and this page is not going to pretend otherwise. It is hosted at mcp.mailerlite.com, authorizes with OAuth, and MailerLite links it from its own pricing table and features pages. It is a good fit for working inside Claude, ChatGPT, Cursor or a CLI, and it does things this connector cannot: install and discover templates, generate email content and subject lines, dry run and test an automation, and read campaign link reporting that the REST reference does not document. The counted tool list is 77 against our 97 nodes, and the ratio flatters neither side, because it is not like for like. Eight of their tools take an action parameter and stand in for a whole e-commerce family each. Going the other way, their list 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. If you want an assistant that also authors, use theirs. If you want a typed surface that runs unattended and chains with the rest of your stack, this is the one.

Two of their tools also describe operations the REST reference does not: create_segment and create_form. There is no documented POST to the segments collection and none to the forms collection, so this connector does not ship those, and it does not claim parity on them. What it ships is what MailerLite documents, which is why the node list on this page is generated from the connector's own spec rather than typed by hand.

Sending is the one thing a free MailerLite account cannot do through an API or an MCP server, and it is worth reading before you plan a workflow. MailerLite's pricing FAQ is explicit: email sending via the API and MCP server is available on paid plans, and on Free, API and MCP access is limited and does not include sending. So on a free account every node here that manages data works, MailerLite: Create Campaign builds the draft, MailerLite: Get Campaign reads it back, and MailerLite: Schedule or Send Campaign will not deliver mail. One node sends: MailerLite: Schedule or Send Campaign with delivery set to instant mails the campaign's entire audience with no dry run and no undo, which is why it carries a destructive flag. Six others can send indirectly by starting an automation, and each says so on the node.

This is MailerLite, not MailerLite Classic, and they are two different products rather than two versions of one. This connector talks to https://connect.mailerlite.com/api with an Authorization Bearer token and a date-valued X-Version header. Classic talks to a different host with an X-MailerLite-ApiKey header and a version in the path, and MailerLite documents it as the API for Classic accounts only. A Classic key pasted here returns a 401 whose entire body is the word Unauthenticated, which tells you nothing, so the connector's own error hint names this as one of the causes.

Two API behaviours shape how MailerLite workflows should be built, and both are surfaced on the nodes rather than left for you to discover. First, pagination is two different mechanisms and MailerLite does not unify them: MailerLite: List Subscribers, MailerLite: List Group Subscribers, MailerLite: List Form Subscribers and MailerLite: List Segment Subscribers are cursor paged and report no totals, while every other list is page numbered and reports a last page and a total. Sending the wrong one is ignored rather than rejected, which loops forever at HTTP 200, so each node declares only the parameter its own endpoint accepts and its sample output carries the real meta shape. Second, the global rate limit is 120 requests per minute, but imports run on a separate limit of 5 per minute, and that is the one that bites a bulk workflow. MailerLite: Run Batch Request folds up to 50 calls into one request against the global limit, with one catch worth knowing: a batch made entirely of subscriber upserts is treated as an import and falls under the 5 per minute limit instead.

One connection, three surfaces

  • Visual automations. Drag MailerLite nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every MailerLite node, ready to drop on the canvas

97 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 45

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

Connecting MailerLite takes one credential

MailerLite issues a token from inside the app: open Integrations, choose MailerLite API and click Generate new token. There is no OAuth application to register and nothing to wait for. Two things are worth knowing before you generate it. MailerLite states that API keys are permanently bound to the user who created them, so if that person is removed from the account or their user account is deleted, the token stops authenticating, which shows up later as a 401 that nothing on your side caused. And sending is plan gated: MailerLite's pricing FAQ says 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 data nodes perfectly well.

1

Decide which MailerLite user holds the token. MailerLite binds an API key permanently to its creator, so a key generated by a person who later leaves the account stops working with no warning and no change on the Mattering side. A user the business controls beats an individual's login.

2

In MailerLite, open Integrations, choose MailerLite API and click Generate new token. Copy it once. Confirm you are on the current MailerLite rather than MailerLite Classic: Classic issues a different key for a different host and its key will not authenticate here.

3

In Mattering Automations, open Connectors, click Add Connector and choose MailerLite, then create a new credential and paste the token. It is stored encrypted and never appears in workflow logs.

4

Click Test Connection. Mattering calls the subscriber count endpoint, which reads a single number rather than any subscriber data and needs no ids. A 401 means the token is wrong, is a Classic key, or belonged to a user who has been removed. A 403 is a different finding: the credential is fine and MailerLite is refusing the action for that account, which on this API usually means a plan gate rather than a bad key.

5

All 97 MailerLite nodes appear in the canvas palette. Run MailerLite: List Groups first, since it takes no ids and feeds most of the pickers, then MailerLite: Count Subscribers to see the account size without paging anything.

Common uses for the MailerLite MCP

Grow the list from every system that already knows your customers

MailerLite: Create or Update Subscriber is the node to build on, because it is an upsert: MailerLite answers 201 when it created the person and 200 when it matched an existing address, so a retry on a flaky webhook does not produce duplicates. That matters more than usual here, because this API has no idempotency keys at all. It is also additive rather than replacing, so it leaves group memberships and field values you did not send alone. Read MailerLite: List Fields before you write anything into a subscriber's custom fields: the fields object is keyed by the field key rather than its display name, and MailerLite derives the key from the name at creation, so the two drift apart after a rename. Adding somebody to a group is an automation trigger in MailerLite, which means this node can cause mail to be sent to a real person.

Abandoned cart data kept current from your own shop

This is the part of MailerLite most integrations only half build. MailerLite: Create Order creates the order, its customer and its cart in one call, and it is the only way to create a cart on this API, because carts have no create endpoint of their own. MailerLite: Add Cart Item, MailerLite: Update Cart Item and MailerLite: Delete Cart Item keep the lines accurate as a shopper changes their mind, and MailerLite: Update Cart is the one that matters most for recovery, because the checkout URL it holds is the link the abandoned-cart email puts in front of the shopper. Two things to design around: an item's price is a snapshot of what was charged and does not follow the product's later price, which is correct, and changing lines does not recompute the cart total, so set it deliberately.

Campaign reporting that lands where the business already looks

MailerLite: List Campaigns carries the full per-email stats block on sent campaigns, with sends, unique opens, clicks, unsubscribes, spam complaints and hard and soft bounces. One default trips people up and the node says so: with no status filter MailerLite returns ready campaigns only, so ask for sent explicitly. MailerLite: Get Campaign Subscriber Activity goes a level deeper for a single send, per recipient, and its meta aggregations object carries the whole-campaign totals in one place, which is usually what a dashboard actually wants. A weekly schedule can write that into a Mattering database, open a Productivity task with the numbers, or post the summary into Comms, without anybody exporting a CSV.

An initial catalogue sync that fits inside the rate limits

MailerLite: Import Products and MailerLite: Import Categories each take a bare JSON array and create many records in one request, which is one call against the 120 per minute limit instead of one per row. Order matters: categories referenced by a product have to exist first. MailerLite: Count Products and MailerLite: Count Categories are the cheap way to confirm the sync landed, because MailerLite documents a limit of zero as its own operation returning a single total with no rows at all. Use MailerLite: Update Product rather than delete and recreate when something changes, and prefer setting a product's automation exclusion over MailerLite: Delete Product when retiring it, so campaign blocks and automations that reference it do not lose their target.

Bulk imports without tripping the limit nobody expects

MailerLite: Import Subscribers to Group is the right node for a file of addresses, and it behaves differently from looping the create node in two ways worth planning for. It runs on its own limit of 5 requests per minute, separate from the global 120, and MailerLite says so in the error message rather than in a header. And it is asynchronous: the response is a progress URL rather than a result, so the work is still running when the call returns. MailerLite: Get Import Report reads the outcome, with counts split by imported, updated, errored, invalid, mistyped, unchanged, unsubscribed, role based and banned, each carrying a sample of addresses. Poll it until it reports done rather than assuming the import finished when the request that started it returned. Importing into a group can start an automation, so treat this as a sending action.

Hygiene and erasure handled with the right node

MailerLite gives two different removals and they are not interchangeable. MailerLite: Delete Subscriber takes somebody off the account while MailerLite keeps their information in case they subscribe again. MailerLite: Forget Subscriber is the erasure path: MailerLite removes them immediately and deletes all of their information within 30 days, and the response is the last full copy of the record you will see, so capture whatever your own compliance records need before running it. Neither is reversible after the fact. On the e-commerce side, MailerLite: Delete Customer removes a purchase identity and MailerLite is explicit that the linked subscriber survives untouched, so it is not an erasure either. A scheduled workflow that reads a suppression list from your own system and applies the correct one of these is a good first automation, because it is the kind of job that gets skipped when it is manual.

Example: A weekly campaign digest that never sends anything by itself

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a weekly schedule fires. This connector has no trigger nodes, so MailerLite workflows either run on a schedule or start from another app's trigger. If you want MailerLite to push, register an endpoint with MailerLite: Create Webhook and receive the delivery there.

2

MailerLite: List Campaigns runs with the status filter set to sent, because leaving it empty returns ready campaigns only, and it comes back with the per-email stats block already attached rather than needing a read per campaign.

3

For the most recent send, MailerLite: Get Campaign Subscriber Activity reads the per-recipient outcomes, and the workflow takes the whole-campaign totals from its meta aggregations object rather than summing pages itself.

4

MailerLite: Count Subscribers returns the current list size as a single number. It is the limit-of-zero operation, so it costs one request and pages nothing, which keeps the whole digest well inside the 120 per minute budget.

5

An AI step writes the plain summary: what went out, how it performed against the previous week, and which segments moved. Nothing has been written back to MailerLite at this point.

6

A task is created in Mattering Productivity with the numbers and the draft, so a person reads it. Sending stays a deliberate act: MailerLite: Schedule or Send Campaign mails a real audience with no dry run and no recall, so it belongs behind an approval step rather than at the end of a schedule.

MailerLite MCP questions, answered

Does MailerLite publish its own MCP server, and why use this one?

Yes. MailerLite ships a first-party hosted MCP server at mcp.mailerlite.com, authorized with OAuth, linked from its own pricing table and features pages, and supported in Claude, Claude Code, ChatGPT, Cursor, Gemini CLI and VS Code. It is a genuinely good assistant surface and it does several things this connector does not: discovering and installing templates, generating email content and subject lines, dry running and test sending an automation, and reading campaign link reporting that MailerLite's REST reference does not document. The honest comparison is 77 tools against 97 nodes, and it is not like for like in either direction. Eight of their tools take an action parameter and cover a whole e-commerce family each, so their coverage is wider than the count suggests. Their list also has no timezone reader, no campaign language reader, no subscriber forget, no import report reader, and a count for subscribers only rather than for the eight collections that support one. The reason to use this connector is a different one from tool count: these nodes run on a schedule with nobody present, chain with every other connector in one workflow, hold the credential once in a shared workspace store rather than in each person's config, and carry destructive flags on the nodes that can mail real people or erase data.

Can I send email through this on a free MailerLite plan?

No, and MailerLite is explicit about it rather than leaving you to find out. Its 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. What that means in practice is that a free account can use almost all of this connector: manage subscribers, groups, segments, custom fields and forms, build campaigns and read their reports, run the entire e-commerce surface, register webhooks. MailerLite: Create Campaign will create the draft. MailerLite: Schedule or Send Campaign is the node that will not deliver. MailerLite does list MCP access itself among its free plan features, so this is a sending gate rather than an API gate. If a workflow's whole point is delivery, budget for a paid MailerLite plan before you build it.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, the open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and work with MailerLite through it. Matter, the assistant built into the platform, uses the same nodes natively. The same nodes are also steps on the automation canvas, which is the part a chat-only connection cannot give you: the workflow an assistant helps you design then runs on a schedule, alongside every other connector, without anybody watching. Given that one node here mails a live audience and two erase data, the sensible split is to give an assistant the 45 read nodes freely and put MailerLite: Schedule or Send Campaign, MailerLite: Forget Subscriber and the deletes behind a condition or an approval step.

Is this the same as the MailerLite Classic API?

No, and mixing them up is the most common way to lose an hour here. MailerLite runs two APIs for two products. This connector is built entirely on the current one at https://connect.mailerlite.com/api, which authenticates with an Authorization Bearer token and pins its version with a date-valued X-Version header. MailerLite Classic is a separate product on a different host that authenticates with an X-MailerLite-ApiKey header and carries its version in the path, and MailerLite documents it as being for Classic accounts, to be migrated away from eventually. A Classic key pasted into this connector fails with a 401 whose body is a single word, Unauthenticated, with nothing pointing at the cause, which is why the connector's error hint names it explicitly. There is no shared token and no compatibility layer between the two.

What are MailerLite's rate limits, and which one will I actually hit?

MailerLite documents a global limit of 120 requests per minute, with X-RateLimit-Limit, X-RateLimit-Remaining and Retry-After headers on the response and a message of Too Many Attempts when you exceed it. The one that catches people is the second limit: import endpoints allow 5 requests per minute, and it applies to the group import, to subscriber import, and to any batch whose items are all subscriber upserts, because MailerLite processes that batch as an import internally. The two need different fixes, which is why the connector reads the error message rather than guessing from the endpoint: back off a few seconds for the global limit, but restructure the workflow for the import limit, because waiting does not help when the shape is wrong. MailerLite: Run Batch Request is the intended answer to the global limit, folding up to 50 calls into one request, as long as the batch is not made entirely of subscriber upserts.

Why do some list nodes have a Cursor field and others a Page field?

Because MailerLite genuinely paginates two ways and does not unify them, and the connector surfaces the difference rather than smoothing it over. MailerLite: List Subscribers, MailerLite: List Group Subscribers, MailerLite: List Form Subscribers and MailerLite: List Segment Subscribers are cursor paged: you pass the next cursor from the response's meta object, and there are no page numbers and no total. Everything else, including all the e-commerce lists, is page numbered and reports a current page, a last page and a total. What makes this worth a paragraph rather than a footnote is that sending the wrong parameter is silently ignored rather than rejected, so a cursor sent to a page-numbered endpoint re-reads page one forever at HTTP 200 and a page number sent to a cursor endpoint re-reads the first slice forever. Each node here declares only the parameter its own endpoint accepts, and its sample output carries the real shape, so the canvas offers the right field to map. MailerLite: List Segment Subscribers is the one exception carried as-is, because MailerLite documents two forward mechanisms on it and expects you to pick one.

Can this create segments or forms in MailerLite?

No, and this is a place where MailerLite's own MCP server does something this connector cannot. Its tool list includes create_segment, get_segment and create_form, but MailerLite's REST reference documents no POST to the segments collection and no POST to the forms collection: the segments page documents listing, reading subscribers, updating and deleting, and the forms page documents listing, reading, updating, deleting and reading subscribers. Their server may call undocumented endpoints, compose the result from other calls, or the reference may be behind. This connector is built strictly from what MailerLite documents, because a node built on a guessed request shape ships broken and looks fine, so segment and form creation happen in the MailerLite app or through their server. What is here is everything else: MailerLite: List Segments, MailerLite: Update Segment, MailerLite: Delete Segment and MailerLite: List Segment Subscribers, and the same set for forms.

Can I sync only what changed since last time?

Not from filters, and that is a property of MailerLite's API rather than a gap in this connector. Nothing on this API accepts a created-after or updated-after filter: MailerLite: List Subscribers filters on status only, and MailerLite: List Orders, MailerLite: List Products and every other e-commerce list offer paging and nothing more. The single windowed endpoint on the whole API is MailerLite: Get Automation Activity, and even there the window depends on what you asked for: the date filters apply to the completed, canceled and failed statuses while the scheduled filters apply to the active status, and sending the wrong pair returns an unfiltered window rather than an error. So an incremental sync against MailerLite means paging and comparing timestamps on your side. Two nodes make that cheaper than it sounds: the count nodes tell you whether anything moved without reading a row, and MailerLite: Run Batch Request folds fifty reads into one request.

97 nodes waiting on the canvas

Put MailerLite to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. MailerLite is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products