OtherReal-timeUpdated June 2026

Onfleet integration

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.

Connect Onfleet See 5 triggers

No credit card required · Set up in under 2 minutes

5triggers

2actions

≈ 2 minto set up

Freetier · no card

Triggers

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.

Real-time · webhook-driven

Trigger live

When onfleet task completed

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.

See what it returns →

Trigger live

When 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.

See what it returns →

Trigger live

When 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.

See what it returns →

Trigger live

When 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.

See what it returns →

Trigger live

When 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".

See what it returns →

Actions

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	Inputs	Open action
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.	4 inputs	View
List Onfleet Tasks	Paginated tasks with filters by worker, status, time window. For "today's deliveries by driver" capacity dashboards.	2 inputs	View

Recipes

Pre-built Onfleet workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Onfleet → Slack alerts

AI-triage every Onfleet event, ping the right channel only when it matters.

Onfleet → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Onfleet → Notion database

Turn Onfleet into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Onfleet once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Onfleet field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

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?

Open the Tiny Command workflow builder, drop in a Onfleet node, and click Connect. Authorize Onfleet once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Onfleet triggers does Tiny Command support?

Tiny Command supports 5 real-time Onfleet triggers, including "Onfleet Task Completed", "Onfleet Task Created", "Onfleet Task Failed". Each trigger fires within seconds of the event happening in Onfleet.

What Onfleet actions can I run from a workflow?

2 Onfleet actions are available out of the box, covering other operations like "Create Onfleet Task". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Onfleet integration real-time?

Yes. Onfleet Task Completed and every other Onfleet trigger uses webhooks or push subscriptions, so workflows fire within seconds of the event in Onfleet rather than on a polling schedule.

Do I need to write code to use Onfleet with Tiny Command?

No. Every Onfleet trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Onfleet API endpoint directly.

How much does the Onfleet integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Onfleet integration itself has no per-app surcharge.

Onfleet integration

Workflows start when Onfleet does.

Do anything Onfleet can do, from a workflow.

Pre-built Onfleet workflows.

Three things worth knowing.

Questions about the Onfleet integration.

More other apps people connect.

Do more with Onfleet.