Short answer: Drop the "Zendesk → New Ticket" 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.
{"url": "https://yourcompany.zendesk.com/api/v2/tickets/12345.json","status": "new","subject": "Cannot access my account","priority": "high","ticket_id": "12345","created_at": "2026-04-11T10:00:00Z","requester_name": "Jane Smith","requester_email": "jane.smith@example.com"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| url | string | "https://yourcompany.zendesk.com/api/v2/tickets/12345.json" |
| status | string | "new" |
| subject | string | "Cannot access my account" |
| priority | string | "high" |
| ticket_id | string | "12345" |
| created_at | string | "2026-04-11T10:00:00Z" |
| requester_name | string | "Jane Smith" |
| requester_email | string | "jane.smith@example.com" |
One trigger. 17+ downstream actions. Zero glue.