Webhooks
Webhooks make it possible for your application to be notified of important system events, as soon as these take place within Onfleet.
While you are generally able to create as many webhook entries as you'd like, remember that a single webhook always targets a single trigger. The following triggers are available:
ID | Name | Description | Includes | Limitations |
|---|---|---|---|---|
0 | taskStarted | Task started by worker. |
| None |
1 | taskEta | Worker ETA less than or equal to |
| Limit of 10 webhooks. Each will fire once per task, at most once every 30 seconds, when threshold is met. |
2 | taskArrival | Worker arriving, at or closer than |
| Limit of 10 webhooks. Each will fire once per task, at most once every 30 seconds, when threshold is met. |
3 | taskCompleted | Task marked as successful. |
| Task cannot be both successful and failed. |
4 | taskFailed | Task failed. |
| Task cannot be both successful and failed. |
5 | workerDuty | Worker status changed ( |
| None |
6 | taskCreated | New task created. |
| Does not include tasks created via task import from the Onfleet dashboard. |
7 | taskUpdated | Task updated, including: Updated When attachment ids are received under Recipient feedback has been received(when |
| None |
8 | taskDeleted | Task deleted. |
| None |
9 | taskAssigned | Task assigned to worker. |
| This webhook will only be triggered when a Task is assigned to different containers (organization, worker, team). However, when a task is assigned during creation, it will not trigger a change of assignment as the task is just created with a direct assignment. |
10 | taskUnassigned | Task unassigned from worker. |
| None |
12 | taskDelayed | Task is delay time is greater than or equal to |
| Limit of 10 webhooks, applies only to active tasks, will only fire once. Only sent for active tasks. |
13 | taskCloned | Task cloned via dashboard or API. Note that the |
| None |
14 | smsRecipientResponseMissed | Recipient responds to a notification via SMS, but the organization is unable to handle it at that time. |
| None |
15 | workerCreated | A new worker has been created. |
| None |
16 | workerDeleted | A worker has been deleted. |
| None. |
17 | SMSRecipientOptOut | When a recipient replied "STOP" to opt out of SMS communications. |
| None. |
18 | autoDispatchJobCompleted | When Team Auto-Dispatch calculation is completed. |
| None. |
19 | taskBatchCreateJobCompleted | When Async Batch Tasks creation is completed. |
| None. |
20 | routeOptimizationJobCompleted | When Route Optimization is completed |
| |
22 | routePlanCreated | When a Route plan is created |
| |
23 | routePlanStarted | When a Route plan is started |
| |
24 | routePlanCompleted | When a Route plan completed |
| |
25 | workerUpdated | When a worker information is updated |
| |
26 | routePlanUpdated | When a Route plan is changed |
| |
27 | routePlanUnassigned | When a Route Plan is unassigned |
| |
28 | routePlanAssigned | When a Route Plan is assigned |
| |
29 | routePlanDelayed | When a Route Plan is marked as delayed |
| |
30 | predictedTaskDelay | Predicted task is delay time is greater than or equal to |
| Will be sent for tasks in an "assigned" state. Note that this is evaluated when tasks in the driver's queue are started, and messages will be sent at this point. |
Webhooks can be maintained via dashboard or API. All standard, non-validation requests from Onfleet to you are made via POST.
In addition to the properties from the Includes column above, the JSON body we will POST to your url will include a time property along with triggerId and triggerName so you may overload the same url on your application as required. In addition, full objects will be provided in the data property, as relevant. Note that all other properties not relevant to the trigger may be provided as null.
Unix Precision
All time data fields returned are in milliseconds precision, with the exception of
etaSeconds, which is in seconds.