ActionMailerLiteUpdated May 2026

How do I add a MailerLite subscriber?

Short answer: Drop the "MailerLite → Create MailerLite Subscriber" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 2 MailerLite actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Email email	email	Required	The email address. Used as the recipient or identifier depending on context.
Name name	string	Optional	Name
Status status	options	Optional	Status. Options: Active, Unsubscribed, Unconfirmed

Sample request

{
  "email": "e.g. user@example.com",
  "name": "{{trigger.name}}",
  "status": "{{trigger.status}}"
}

Returns

{
  "data": {
    "id": "sub123",
    "email": "john@example.com",
    "status": "active",
    "subscribed_at": "2026-04-11T10:00:00Z"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Create MailerLite Subscriber.

Any of these apps can fire this action as part of a workflow.

Google Sheets → MailerLite

2 Google Sheets triggers

HubSpot → MailerLite

18 HubSpot triggers

FAQ

Questions about Create MailerLite Subscriber.

What does the Create MailerLite Subscriber action do in MailerLite?

Adds a subscriber with email, name, custom fields, group memberships, double-opt-in toggle. For "form submission → push to MailerLite" sync workflows.

What inputs does Create MailerLite Subscriber require?

Required: Email. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if MailerLite returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create MailerLite Subscriber support batch operations?

Yes. Run Create MailerLite Subscriber inside a Loop node to process arrays. Tiny Command handles MailerLite's rate limits automatically so you don't have to throttle manually.

More actions