TriggerMailerLiteReal-timeUpdated May 2026
When does MailerLite fire on unsubscribes?
Short answer: Drop the "MailerLite → MailerLite Unsubscribe" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in MailerLite, not on a polling schedule.
Anatomy
What this trigger looks like in a workflow.
Drop it on the canvas. Configure a couple of fields. Publish.
In the builder
Trigger
MailerLite Unsubscribe
When the matching event happens
new subscriber unsubscribedwhen subscriber unsubscribedon subscriber unsubscribedwatch for subscriber unsubscribedwhen a subscriber unsubscribes
What this trigger returns
for the curiousYou don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"name": "John Doe","email": "user@example.com","event": "subscriber.unsubscribed"}
Output shape
Fields available to downstream nodes.
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| name | string | "John Doe" |
| string | "user@example.com" | |
| event | string | "subscriber.unsubscribed" |
Pairs with
Drop these actions after MailerLite Unsubscribe.
FAQ
Questions about MailerLite Unsubscribe.
How does the MailerLite Unsubscribe trigger work in MailerLite?
Fires when a subscriber opts out. For "suppress in CRM, log to churn" downstream cleanup workflows.
Is the MailerLite Unsubscribe trigger real-time?
Yes. MailerLite Unsubscribe uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in MailerLite.
What data does MailerLite Unsubscribe return?
The full event payload from MailerLite. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter MailerLite Unsubscribe so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need MailerLite admin permissions to use MailerLite Unsubscribe?
For most MailerLite accounts a standard user can authorize the trigger. Some MailerLite plans require an admin to enable third-party webhooks. Check MailerLite's docs if the trigger fails to register.
More triggers
Other MailerLite triggers.
Trigger
MailerLite Automation Triggered
Fires when a subscriber enters a MailerLite automation. Useful for cross-app fan-out: "they entered nurture sequence → also create the Pipedrive activity / Notion task".
TriggerMailerLite Email Bounced
Fires when an outbound email bounces. Distinguishes hard vs soft in payload type field. For hard-bounce list-hygiene workflows.
TriggerMailerLite Subscriber Added
Fires after double-opt-in confirms (or immediately for single opt-in). The base hook for "new subscriber → push to CRM, fan out welcome" workflows.
TriggerMailerLite Subscriber Updated
Fires on any subscriber field change. For specific updates (tag added, custom field set), inspect the payload.
Build a workflow on this trigger.
One trigger. 2+ downstream actions. Zero glue.
