TriggerOnfleetReal-timeUpdated June 2026

When does Onfleet fire on task completion?

Short answer: In TinyCommand, add the Onfleet Onfleet Task Completed trigger to a workflow and publish. It listens through a Onfleet webhook and fires your workflow within seconds of the event, with no polling and no code. Add a filter if you only want some events to start a run.

Trigger workflows on Onfleet Task Completed in Onfleet — start free
Anatomy

What this trigger looks like in a workflow.

Drop it on the canvas. Configure a couple of fields. Publish.

In the builder
Trigger
Onfleet Task Completed
When the matching event happens
when a delivery task is completednew task completedon task completedwatch for task completedwhen task completed
What this trigger returns
for the curious

You don’t need to read this. TinyCommand 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": "taskCompleted",
"address": "123 Main St, San Francisco",
"task_id": "task_123"
}
Output shape

Fields available to downstream nodes.

Every field below can be referenced by name in any action or filter that comes after this trigger.

FieldTypeExample
eventstring"taskCompleted"
addressstring"123 Main St, San Francisco"
task_idstring"task_123"
FAQ

Questions about Onfleet Task Completed.

How does the Onfleet Task Completed trigger work in Onfleet?
Fires when a driver completes a delivery. Payload includes proof-of-delivery (signature URL, photo URL), completion time, notes. For "delivered → notify customer, log to order record" cascading workflows.
Is the Onfleet Task Completed trigger real-time?
Yes. Onfleet Task Completed uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Onfleet.
What data does Onfleet Task Completed return?
The full event payload from Onfleet. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter Onfleet Task Completed so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need Onfleet admin permissions to use Onfleet Task Completed?
For most Onfleet accounts a standard user can authorize the trigger. Some Onfleet plans require an admin to enable third-party webhooks. Check Onfleet's docs if the trigger fails to register.
More triggers

Other Onfleet triggers.

Trigger
Onfleet Task Created
Fires when a new delivery task is created. Useful for "log to delivery tracking spreadsheet" or "send pre-delivery SMS to recipient" workflows.
Trigger
Onfleet Task Failed
Fires when the driver marks a stop as unsuccessful (customer unavailable, refused, damaged). The high-signal CS hook — fires before the customer ever calls in to complain.
Trigger
Onfleet Task Started
Fires when the driver picks up the next stop in their queue. For "driver is now en route → SMS the customer ETA" workflows.
Trigger
Onfleet Worker Duty Change
Fires on shift start and end transitions. For capacity-planning workflows that track "who's actually rolling vs scheduled" or for "all drivers off-duty alert".
Trigger workflows on Onfleet Task Completed in Onfleet — start free