MailerLite
Turn orders and customer changes into the right MailerLite audiences and campaigns, with a person approving what goes out.
40 ways to read, 20 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with MailerLite, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create draft automationApproval by rule
- Create draft campaignApproval by rule
- List automation subscriber activityRead
Example flow
- MailerLite · List automation subscriber activityDone
- MailerLite · Create draft automationNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches MailerLite.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to MailerLite
- MailerLite's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Read and upsert MailerLite subscribers; manage groups, fields, segments, forms and draft campaigns; read automations, webhooks and reports; sync e-commerce shops, categories, products and customers.
MailerLite API docs- Source actions
- 40
- Destination actions
- 20
- Data types
- 30
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Automation activity1
- List automation subscriber activitySource
Subscribers in an automation by queue status.
Automations3
- Create draft automationDestinationNot retried automaticallyApproval before production
Creates an empty, disabled automation; it has no trigger or steps and sends nothing.
- Get automationSource
An automation with steps, email stats and triggers.
- List automationsSource
Automations with enabled state, steps and stats.
Campaign ecommerce stats1
- Get campaign e-commerce statsSource
Orders, revenue, average order value and conversion rate a campaign earned in a shop.
Campaign languages1
- List campaign languagesSource
Languages available for campaign unsubscribe templates (use the ID as languageId).
Campaign orders1
- List campaign e-commerce ordersSource
Orders a campaign earned in a shop, with the ordering subscriber.
Campaign subscriber activity1
- List campaign recipient activitySource
Per-recipient opens and clicks for a sent campaign.
Campaigns4
- Create draft campaignDestinationNot retried automaticallyApproval before production
Creates a regular campaign as a draft; it is not scheduled or sent.
- Get campaignSource
A campaign with emails and delivery stats.
- List campaignsSource
Campaigns with status, sender, audience and delivery stats.
- Update draft campaignDestinationProvider duplicate protectionApproval before production
Updates a draft campaign's name, sender, subject, content and audience; it is not scheduled or sent.
Carts2
- Get shop cartSource
A cart with checkout URL, total, customer and items.
- List shop cartsSource
Carts of a shop with checkout URL, total, customer and items.
Category products1
- List category productsSource
Products assigned to a shop category.
Ecommerce categories4
- Create shop categoryDestinationNot retried automaticallyApproval before production
Creates a product category in a shop.
- Get shop categorySource
A product category of a shop.
- List shop categoriesSource
Product categories synced for a shop.
- Update shop categoryDestinationProvider duplicate protectionApproval before production
Renames a category or changes whether it triggers automations.
Ecommerce customers4
- Create shop customerDestinationNot retried automaticallyApproval before production
Creates a shop customer, linked to an existing subscriber with the same email or, when asked, a new subscriber.
- Get shop customerSource
A shop customer by ID.
- List shop customersSource
Customers of a shop with marketing consent and linked subscriber.
- Update shop customerDestinationProvider duplicate protectionApproval before production
Updates a shop customer's email, marketing consent or total spent.
Ecommerce orders2
- Get shop orderSource
A shop order with customer, cart items and attribution.
- List shop ordersSource
Orders of a shop with customer, cart items and campaign or automation attribution.
Ecommerce products4
- Create shop productDestinationNot retried automaticallyApproval before production
Creates a product in a shop for product blocks and e-commerce automations.
- Get shop productSource
A product of a shop with its categories.
- List shop productsSource
Products synced for a shop, with categories.
- Update shop productDestinationProvider duplicate protectionApproval before production
Updates a product's name, price, links, descriptions or automation flag.
Fields3
- Create fieldDestinationNot retried automaticallyApproval before production
Creates a custom subscriber field.
- List fieldsSource
Default and custom subscriber fields with key and type.
- Rename fieldDestinationProvider duplicate protectionApproval before production
Renames a custom field (the key does not change).
Form subscribers1
- List form sign-upsSource
Subscribers who signed up through a form.
Forms3
- Get formSource
A form with conversion stats.
- List formsSource
Pop-up, embedded or promotion forms with conversion stats.
- Rename formDestinationProvider duplicate protectionApproval before production
Renames a form.
Group memberships1
- Add subscriber to groupDestinationProvider duplicate protectionApproval before production
Assigns an existing subscriber to a group; repeating it has no further effect.
Group subscribers1
- List group subscribersSource
Subscribers in a group (active by default).
Groups3
- Create groupDestinationNot retried automaticallyApproval before production
Creates a subscriber group.
- List groupsSource
Groups with subscriber counts and engagement rates.
- Rename groupDestinationProvider duplicate protectionApproval before production
Renames a subscriber group.
Segment subscribers1
- List segment subscribersSource
Subscribers in a segment (active by default).
Segments2
- List segmentsSource
Segments with size and engagement rates.
- Rename segmentDestinationProvider duplicate protectionApproval before production
Renames a segment.
Shop stats1
- Get shop e-commerce statsSource
Orders and revenue your emails earned in a shop over a period, with a daily series.
Shops4
- Create e-commerce shopDestinationNot retried automaticallyApproval before production
Registers a shop for e-commerce tracking (platform access data is never sent).
- Get e-commerce shopSource
A connected shop.
- List e-commerce shopsSource
Shops connected to the account with currency, state and subscriber group.
- Update e-commerce shopDestinationProvider duplicate protectionApproval before production
Updates a shop's name, URL, currency, group or e-commerce settings.
Subscriber activity1
- List subscriber activitySource
A subscriber's activity log (sends, opens, clicks, unsubscribes, preference changes).
Subscriber ecommerce stats1
- Get subscriber e-commerce statsSource
Orders and revenue a subscriber placed in a shop from your emails.
Subscriber imports1
- Get subscriber importSource
Progress and outcome counts of a subscriber import (for example a group import).
Subscriber orders1
- List subscriber e-commerce ordersSource
Completed orders a subscriber placed in a shop from your emails.
Subscribers4
- Get subscriberSource
A subscriber by ID or email address.
- List subscribersSource
Subscribers with fields, engagement counts and consent timestamps.
- Update subscriberDestinationProvider duplicate protectionApproval before production
Updates a subscriber by ID. Group IDs, when given, replace the subscriber's group membership.
- Create or update subscriberDestinationProvider duplicate protectionApproval before production
Creates a subscriber or updates the one with this email; fields and groups are only added, never removed.
Timezones1
- List time zonesSource
Time zone IDs MailerLite accepts, with UTC offsets.
Webhooks2
- Get webhookSource
A webhook subscription (the signing secret is omitted).
- List webhooksSource
Webhook subscriptions with URL, events and state (signing secrets are omitted).
Access and limits
- Authentication
- API token (bearer)
- Plans and access
- All MailerLite plans (new MailerLite) include the API; custom HTML campaign content needs the Advanced plan. API tokens have full account access; create a dedicated token per integration.
- Test environment
- A free MailerLite account works for testing.
- Rate limits
- 120 requests per minute per account; group subscriber imports are limited to 5 per minute; HTTP 429 when exceeded.
- Pagination
- Subscriber lists use cursors (meta.next_cursor); groups, segments, fields, campaigns, automations, forms, webhooks, reports and e-commerce lists use page numbers until links.next is empty.
- Provider events
- Webhooks for subscriber, campaign and automation events, signed with a per-webhook secret. Flows can start the moment something happens: when someone subscribes; when a subscriber is updated; when someone unsubscribes; when a subscriber joins a group.
Before you build a flow
- Deleting or forgetting subscribers, unassigning groups and deleting groups, fields, segments, campaigns, automations, forms, webhooks, shops, categories, products, customers, orders and carts are not implemented.
- Campaigns can be created and updated as drafts only; scheduling, sending or cancelling campaigns is not implemented. Automations can only be created as empty, disabled drafts.
- E-commerce order, cart and cart item writes and the bulk import endpoints are not implemented because MailerLite uses them to trigger purchase and abandoned-cart automations.
- Operations added for depth never put email addresses in a URL.
- Webhook subscriptions are read only and their signing secrets are not returned; creating or changing webhooks is not implemented.
- Shops are created without platform access data; shop, category, product and customer creation have no idempotency key, so uncertain writes are not repeated automatically.
- Subscriber status, resubscribe and opt-in timestamps change only when a flow maps them explicitly; customer marketing consent is only sent when mapped explicitly.
- Updating a subscriber with group IDs replaces their group membership (unlisted groups are removed); use the add-to-group operation for additive changes.
- Batch requests (/api/batch) and group subscriber imports are not used.
Developer reference
- Create the MailerLite credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose MailerLite, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/mailerlite and the Connections API.
