Short answer: Drop the "Freshdesk → New Ticket" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Freshdesk, 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.
{"ticket_id": 12345,"ticket_status": "Open","ticket_subject": "Need help with login","ticket_priority": "High","ticket_requester_email": "customer@example.com"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| ticket_id | number | 12345 |
| ticket_status | string | "Open" |
| ticket_subject | string | "Need help with login" |
| ticket_priority | string | "High" |
| ticket_requester_email | string | "customer@example.com" |
One trigger. 15+ downstream actions. Zero glue.