Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

MailerLite

Email marketing software

CategoryMarketing
Authenticationcustom
Version0.8.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect MailerLite with Flows360

Email marketing software

Use the MailerLite connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 11 actions and 4 triggers.

Available actions

  • Add Subscriber to a Group
  • Add or Update subscriber
  • Find a Subscriber
  • Remove Subscriber from a Group
  • List Subscribers
  • Unsubscribe Subscriber
  • Delete Subscriber
  • List Groups
  • Plus 3 additional declared actions.

Available triggers

  • Subscriber Created
  • Subscriber Fields Updated
  • Subscriber Unsubscribed
  • Subscriber Added to Group

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: MailerLite
  • Package: @activepieces/piece-mailer-lite@0.8.0
  • Exact artifact digest: sha256:fa322725efa49a915a53b262b1a6e3b7e006c15f479651c4f9c153fec5e81824
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Add Subscriber to a Group (add_subscriber_to_group), Adds existing subscriber to a specific group. Classification: read.
  • Add or Update subscriber (add_or_update_subscriber), Create a new subscriber or updates an existing one if the email already exists. Classification: read.
  • Find a Subscriber (find_subscriber), Search for subscriber by email or name. Classification: read.
  • Remove Subscriber from a Group (remove_subscriber_from_group), Removes subscriber from a specific group. Classification: read.
  • List Subscribers (list_subscribers), List subscribers, optionally filtered by status. Classification: read.
  • Unsubscribe Subscriber (unsubscribe_subscriber), Set a subscriber status to unsubscribed. Classification: read.
  • Delete Subscriber (delete_subscriber), Permanently delete a subscriber. Classification: read.
  • List Groups (list_groups), List groups in the account, one page at a time. Classification: read.
  • Create Group (create_group), Create a new group. Classification: read.
  • List Group Subscribers (list_group_subscribers), List the subscribers belonging to a group. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Subscriber Created, webhook.
  • Subscriber Fields Updated, webhook.
  • Subscriber Unsubscribed, webhook.
  • Subscriber Added to Group, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects15
Supported actions11
Triggers4

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Subscriber to a Group Yes No Adds existing subscriber to a specific group.
Add or Update subscriber Yes No Create a new subscriber or updates an existing one if the email already exists.
Find a Subscriber Yes No Search for subscriber by email or name.
Remove Subscriber from a Group Yes No Removes subscriber from a specific group.
List Subscribers Yes No List subscribers, optionally filtered by status.
Unsubscribe Subscriber Yes No Set a subscriber status to unsubscribed.
Delete Subscriber Yes No Permanently delete a subscriber.
List Groups Yes No List groups in the account, one page at a time.
Create Group Yes No Create a new group.
List Group Subscribers Yes No List the subscribers belonging to a group.
Custom API Call Yes No Make a custom API call to a specific endpoint
Subscriber Created Yes No webhook trigger declared by the pinned package.
Subscriber Fields Updated Yes No webhook trigger declared by the pinned package.
Subscriber Unsubscribed Yes No webhook trigger declared by the pinned package.
Subscriber Added to Group Yes No webhook trigger declared by the pinned package.

Supported actions

Add Subscriber to a Group · Read

Adds existing subscriber to a specific group.

add_subscriber_to_group · Risk: low · Retry: safe

Inputs

  • subscriberId · string · Required
  • subscriberGroupId · string · Required
Add or Update subscriber · Read

Create a new subscriber or updates an existing one if the email already exists.

add_or_update_subscriber · Risk: low · Retry: safe

Inputs

  • email · string · Required, Email of the new contact
  • subscriberFields · object · Required
  • status · string · Optional, If empty, status Active is used by default.
  • subscriberGroupId · array · Optional
  • subscribed_at · string · Optional
  • opted_in_at · string · Optional
  • ip_address · string · Optional
  • optin_ip · string · Optional
Find a Subscriber · Read

Search for subscriber by email or name.

find_subscriber · Risk: low · Retry: safe

Inputs

  • searchValue · string · Required
Remove Subscriber from a Group · Read

Removes subscriber from a specific group.

remove_subscriber_from_group · Risk: low · Retry: safe

Inputs

  • subscriberId · string · Required
  • subscriberGroupId · string · Required
List Subscribers · Read

List subscribers, optionally filtered by status.

list_subscribers · Risk: low · Retry: safe

Inputs

  • status · string · Optional, Only return subscribers with this status
  • limit · number · Optional, Subscribers to return (1-1000, default 25).
Unsubscribe Subscriber · Read

Set a subscriber status to unsubscribed.

unsubscribe_subscriber · Risk: low · Retry: safe

Inputs

  • email · string · Required, Email address of the subscriber to unsubscribe
Delete Subscriber · Read

Permanently delete a subscriber.

delete_subscriber · Risk: low · Retry: safe

Inputs

  • subscriberId · string · Required
List Groups · Read

List groups in the account, one page at a time.

list_groups · Risk: low · Retry: safe

Inputs

  • limit · number · Optional, Groups to return per page (1-1000, default 100).
  • page · number · Optional, Page number to return, starting at 1. Use `meta.last_page` from a previous response to know when to stop.
Create Group · Read

Create a new group.

create_group · Risk: low · Retry: safe

Inputs

  • name · string · Required
List Group Subscribers · Read

List the subscribers belonging to a group.

list_group_subscribers · Risk: low · Retry: safe

Inputs

  • subscriberGroupId · string · Required
  • limit · number · Optional, Subscribers to return (1-1000, default 25).
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

Subscriber Created · Webhook

Triggers when a subscriber was created on your mailing list.

Inputs

  • name · string
Subscriber Fields Updated · Webhook

Triggers when the subscriber fields have been updated.

Inputs

  • name · string
Subscriber Unsubscribed · Webhook

Triggers when a subscriber has unsubscribed from your mailing list.

Inputs

  • name · string
Subscriber Added to Group · Webhook

Triggers when a subscriber is added to a group.

Inputs

  • name · string

Setup

Setup

  1. Add the MailerLite connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-mailer-lite@0.8.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 11 actions and 4 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required MailerLite connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-mailer-lite@0.8.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com