Short answer: Drop the "Mailchimp → New Subscriber" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Mailchimp, 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.
{"ip": "127.0.0.1","email": "tc@example.com","phone": "","web_id": "441282457","address": "","company": "","list_id": "8f33ddce6d","fired_at": "2026-04-11 10:00:00","last_name": "Test","member_id": "2f60c281f7","email_type": "html","event_type": "subscribe","first_name": "TC"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| ip | string | "127.0.0.1" |
| string | "tc@example.com" | |
| phone | string | "" |
| web_id | string | "441282457" |
| address | string | "" |
| company | string | "" |
| list_id | string | "8f33ddce6d" |
| fired_at | string | "2026-04-11 10:00:00" |
| last_name | string | "Test" |
| member_id | string | "2f60c281f7" |
| email_type | string | "html" |
| event_type | string | "subscribe" |
| first_name | string | "TC" |
One trigger. 16+ downstream actions. Zero glue.