Short answer: Drop the "Onfleet → Onfleet Worker Duty Change" 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.
{"event": "workerDuty","address": "123 Main St, San Francisco","task_id": "task_123"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| event | string | "workerDuty" |
| address | string | "123 Main St, San Francisco" |
| task_id | string | "task_123" |
One trigger. 2+ downstream actions. Zero glue.