Short answer: Drop the "Mailjet → Mailjet Unsubscribed" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Mailjet, 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.
{"email": "user@example.com","event": "unsub","message_id": 123456789}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| string | "user@example.com" | |
| event | string | "unsub" |
| message_id | number | 123456789 |
One trigger. 2+ downstream actions. Zero glue.