Short answer: Drop the "MailerLite → MailerLite Automation Triggered" 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.
Drop it on the canvas. Configure a couple of fields. Publish.
You 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.automation_triggered"}
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.automation_triggered" |
One trigger. 2+ downstream actions. Zero glue.