Short answer: Drop the "Zendesk → Ticket Updated" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Zendesk, 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.
{"status": "open","subject": "Cannot access my account","priority": "high","ticket_id": 12345,"updated_at": "2026-04-11T14:30:00Z","latest_comment": "I've reset your password. Please try logging in again."}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| status | string | "open" |
| subject | string | "Cannot access my account" |
| priority | string | "high" |
| ticket_id | number | 12345 |
| updated_at | string | "2026-04-11T14:30:00Z" |
| latest_comment | string | "I've reset your password. Please try logging in again." |
One trigger. 17+ downstream actions. Zero glue.