Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the MailerLite connector page.Automatic webhook setup
No manual configuration is required. When you connect your MailerLite account, StackOne automatically creates a webhook subscription in MailerLite that delivers the events listed below, and removes it again when you disconnect. Only the events you enable in StackOne are included in the subscription — MailerLite will not deliver events that are not subscribed.
Available webhook events
The following MailerLite events can be enabled. Only events selected in StackOne are included in the subscription — MailerLite will not deliver events that are not subscribed.
Subscriber events
Events related to subscribers on your account.
- Subscriber Created (
subscriber.created) — Fired when a new subscriber is added - Subscriber Updated (
subscriber.updated) — Fired when an existing subscriber’s data changes - Subscriber Unsubscribed (
subscriber.unsubscribed) — Fired when a subscriber unsubscribes - Subscriber Added to Group (
subscriber.added_to_group) — Fired when a subscriber is added to a group - Subscriber Removed from Group (
subscriber.removed_from_group) — Fired when a subscriber is removed from a group - Subscriber Bounced (
subscriber.bounced) — Fired when a subscriber’s email address bounces - Subscriber Spam Reported (
subscriber.spam_reported) — Fired when a subscriber marks a campaign as spam - Subscriber Automation Triggered (
subscriber.automation_triggered) — Fired when a subscriber starts an automation - Subscriber Automation Completed (
subscriber.automation_completed) — Fired when a subscriber finishes an automation - Subscriber Active (
subscriber.active) — Fired when a subscriber’s status is set to active
Campaign events
Events related to campaigns.
- Campaign Sent (
campaign.sent) — Fired when a campaign finishes sending
Delivery format
How MailerLite delivers events to StackOne.
Single and batched payloads
MailerLite delivers most events as a single JSON object. Some deliveries are batched — a payload containing an events array with a total count — in which case StackOne routes each event in the batch to its matching handler. Simple events carry the event name in an event field with the record at the root; group and automation events carry it in a type field with nested subscriber and related objects.
Events that require batch mode
The subscriber.deleted, campaign.open, and campaign.click events are not part of the default subscription — MailerLite only delivers them when a webhook is created in batch mode, which changes every payload into the batched events array format. StackOne still receives any such batched deliveries via its generic batch handler.