Short answer: Drop the "Onfleet → Onfleet Task Created" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Onfleet, 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.
{"task": {},"task_id": "YI2UIGUx2nni6ZVOFH2oUEOr","admin_id": "abc","worker_id": null,"trigger_id": "6","action_type": "apiKey","occurred_at": 1778804246000,"trigger_name": "taskCreated","action_context_id": "xyz"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| task | object | { … } |
| task_id | string | "YI2UIGUx2nni6ZVOFH2oUEOr" |
| admin_id | string | "abc" |
| worker_id | null | null |
| trigger_id | string | "6" |
| action_type | string | "apiKey" |
| occurred_at | number | 1778804246000 |
| trigger_name | string | "taskCreated" |
| action_context_id | string | "xyz" |
One trigger. 2+ downstream actions. Zero glue.