Onfleet
Last-mile dispatch events from Onfleet
Onfleet is the dispatch and routing platform for last-mile delivery teams, and Tiny Command wires its five lifecycle events (Task Created, Task Started, Task Completed, Task Failed, Worker Duty Change) into workflows that react the instant a driver picks up, drops off, or goes off-shift. Two actions cover the dispatch side: Create Task to push new stops into a worker's queue (with timing windows, recipient details, and pickup/dropoff metadata), and List Tasks to reconcile state. Task Completed carries the proof-of-delivery payload — signature, photo URL, recipient notes, completion time, and any failure reason if the worker marked the stop as partial. The Worker Duty Change trigger fires on shift start and end, which is the natural hook for capacity planning workflows that need to know how many drivers are actually rolling versus scheduled. Task Failed is the high-signal event for customer-success: it fires before the customer ever calls in to complain.
Workflows start when Onfleet does.
5 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
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.
Fires when a new delivery task is created. Useful for "log to delivery tracking spreadsheet" or "send pre-delivery SMS to recipient" workflows.
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.
Fires when the driver picks up the next stop in their queue. For "driver is now en route → SMS the customer ETA" workflows.
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".
Do anything Onfleet can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create Onfleet Task | Creates a delivery task with recipient, address, time window, pickup/dropoff metadata. The standard hook for "new e-commerce order → create Onfleet delivery task" workflows. |
| List Onfleet Tasks | Paginated tasks with filters by worker, status, time window. For "today's deliveries by driver" capacity dashboards. |
Pre-built Onfleet workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Onfleet once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Onfleet field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Onfleet integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Onfleet to Tiny Command?
What Onfleet triggers does Tiny Command support?
What Onfleet actions can I run from a workflow?
Is the Onfleet integration real-time?
Do I need to write code to use Onfleet with Tiny Command?
How much does the Onfleet integration cost?
More other apps people connect.
Same category as Onfleet, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Onfleet.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
