MailerLite Trigger

Triggers on MailerLite subscriber and campaign events

Overview

Receives webhook notifications from MailerLite when subscriber or campaign events occur. Supports multiple event types including subscriber creation, updates, bounces, unsubscribes, group membership changes, automation triggers/completions, spam reports, and campaign sends. The webhook payload contains subscriber field data for subscriber events or campaign data for campaign events. MailerLite uses the v2 API (connect.mailerlite.com) with Bearer token auth. Multiple events can be selected per webhook. Useful for syncing subscriber data, triggering follow-up workflows on unsubscribes or bounces, tracking automation completions, and reacting to campaign sends in real time.

Category: Marketing
Tool Name: mailerlite_trigger
Version: 1

Appearance: Icon: lucide-Mail | Color: #09c269

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	Output

Credentials

This tool requires MailerLite credentials. See the Credentials Guide for setup instructions.

Parameters

Parameter	Type	Required	Default	Description
Events	multiOptions	Yes	[]	The events to listen for. Select one or more MailerLite webhook event types.
				Options: campaign.sent, subscriber.added_to_group, subscriber.automation_completed (the subscriber finishes an automation), subscriber.automation_triggered (the subscriber starts an automation), subscriber.bounced, subscriber.created, subscriber.removed_from_group, subscriber.spam_reported (the subscriber marks a campaign as spam), subscriber.unsubscribed, subscriber.updated (any of the subscriber’s custom fields change)

Output Data

Each delivery produces one output item; when MailerLite sends an array of subscriber records, each record becomes its own item. Every item carries three metadata fields:

• _trigger — always mailerlite_webhook
• _timestamp — ISO 8601 timestamp of when the request arrived
• _webhookEvent — the event type MailerLite reported, or unknown when the payload does not name one

The payload’s fields object is merged in at the top level (the whole body is used when the payload has no fields), so subscriber attributes such as the address, name and status sit directly on the item. Reference them downstream by expression, e.g. {{ $json.email }}.

Usage Examples

• Start a workflow when a new subscriber is created in MailerLite
• Trigger a notification when a subscriber unsubscribes from a mailing list
• Sync CRM data when a subscriber is added to a MailerLite group
• Automate follow-ups when a subscriber bounces or reports spam
• React in real time when a MailerLite campaign is sent

Example Configuration

Fire on new subscribers:

{
  "type": "mailerlite_trigger",
  "parameters": {
    "events": ["subscriber.created"]
  }
}

Track list hygiene events — unsubscribes, bounces and spam reports:

{
  "type": "mailerlite_trigger",
  "parameters": {
    "events": [
      "subscriber.unsubscribed",
      "subscriber.bounced",
      "subscriber.spam_reported"
    ]
  }
}

Watch group membership and automation progress:

{
  "type": "mailerlite_trigger",
  "parameters": {
    "events": [
      "subscriber.added_to_group",
      "subscriber.removed_from_group",
      "subscriber.automation_triggered",
      "subscriber.automation_completed"
    ]
  }
}

Trigger Behavior

• Activation: When the workflow is activated, a webhook endpoint is registered with the service.
• Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
• Payload: The incoming webhook payload is parsed and output as workflow items.
• Verification: Supports signature verification where applicable.

Tips

Entry point that fires when MailerLite sends a webhook for subscribed events. Select one or more events to listen for (subscriber created, updated, bounced, unsubscribed, added to group, removed from group, automation triggered/completed, spam reported, or campaign sent). The incoming payload contains subscriber field data or campaign details depending on the event type.