Resources · Zapier integration

Onfleet Zapier integrationAutomate Onfleet with Zapier.

The Onfleet Zapier integration covers 14 triggers, 7 actions and 0 searches. Every trigger is instant, so a failed drop, a driver going on duty or a late task reaches your other tools straight away, and orders or tasks can be created from them too.

See the 21 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Onfleet Zapier integration is good for

Connecting Onfleet to Zapier lets your delivery operation talk to the rest of your stack without anyone copying data. Onfleet reports what happens on the road (a task started, completed, failed, delayed) and Zapier passes it on. It also works the other way round: another app can create orders and tasks in Onfleet.

Three outcomes cover most setups. A second attempt that books itself: Task Failed followed by Create Task schedules the return pickup without a dispatcher typing it. A customer team that hears about delays first: Task Delayed and Task ETA fire on thresholds you set, so support can warn the customer before they call. Orders that arrive from your shop already in Onfleet: an order event in another app followed by Create Order or Create Linked Pickup & Dropoff Tasks.

What Zapier does not do here: there is no search, so a Zap cannot look up an existing task or order by itself. The order actions (Update Order, Cancel Order, Clone Order) all need the full Onfleet order ID, which has to come from an earlier step. And Zapier never edits drivers or teams: the actions stop at orders and tasks.

Comparing platforms? The same app has an Onfleet n8n integration and an Onfleet Make integration. Judge them on your scenario, not on the brand.

Vocabulary

Zapier vocabulary in one minute

Seven words do most of the work on this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap, such as an Onfleet task being completed. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that creates, updates or cancels something for you, here an order or a task.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's monthly count is a count of these, not of Onfleet tasks.
Instant trigger
A trigger the app reports itself, the moment the event happens. All 14 Onfleet triggers work this way, unlike polling triggers checked on a timer.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it quietly otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A filter or a second action makes it one, and it then needs a paid plan.
Cost

What an Onfleet Zap really costs

Onfleet is not reserved to paid plans, so it runs on the free plan. Two rules decide the bill.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap size2 steps: one trigger, one action
  • Onfleet triggers14, all instant: no waiting interval

The trigger costs nothing, however many Onfleet events come in. Each action that succeeds is one task, and a failed action is not billed. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap. A filter, like the one that keeps only certain failures, makes the Zap multi-step and needs a paid plan. The polling grid below is the general Zapier rule: it does not apply here, because every Onfleet trigger is instant and fires straight away on every plan.

Connect

Connect Onfleet to Zapier in 3 steps

  1. 01

    Open your apps

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Onfleet account linked once, then reused by every step that uses Onfleet.

  2. 02

    Pick Onfleet

    Type Onfleet in the search box of the dialog, select it and click Add connection. You need an existing Onfleet account, with access to the tasks and orders your Zap will touch.

  3. 03

    Sign in and grant access

    Log in to Onfleet in the tab that opens, then allow Zapier to use the account. The connection appears in your list and every Onfleet step can pick it.

First Zap

Your first Zap: rebook failed deliveries automatically

GoalWhen a delivery fails, create the pickup task that brings the parcel back to the depot.

  1. 01

    Start with the trigger

    Create a new Zap, pick Onfleet and the Task Failed event. Give the webhook a name in Name, the one required box, so you can recognize it later.

  2. 02

    Test it on a real failure

    Run the trigger test. Zapier brings back the three most recent items of your account, so you map the next steps on a real failed task, not on blanks.

  3. 03

    Add a filter

    Add a Filter step and set the condition on a value the test brought back. The Zap is now multi-step, so it needs a paid plan.

  4. 04

    Create the pickup

    Add Onfleet with Create Task, choose a pickup, then fill Merchant, Executor, recipient, coordinates and assignment from the failed task's details.

  5. 05

    Test and publish

    Run each step once and read what came back before going further. If the new task looks right in Onfleet, click Publish to switch the Zap on.

Triggers

The 14 Onfleet triggers

14 events start a Zap when something happens in Onfleet, and 14 of them are instant: the app calls Zapier straight away, whatever your plan.

1

SMS Recipient Response Missed

Instant trigger

In Zapier“Triggers when an Onfleet recipient responds to a notification via SMS, but the organization is unable to handle it due to the task being marked as complete.”

Catches the replies nobody will read: a customer answers a notification by text, but the task is already marked complete, so Onfleet cannot route the message anywhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a florist whose customers text back after delivery ("the card is missing") and wants those replies to reach someone instead of disappearing.
Watch out
you must name the webhook in the Name box; pick something explicit, it is the custom name of the webhook behind this trigger.
2

Task Arrival

Instant trigger

In Zapier“Triggers when a driver is arriving, at or closer than threshold value provided, in meters.”

Fires when a driver gets within a distance you choose from the destination. You set the threshold in meters, anywhere from 0 to 20000.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a meal kit service that wants the kitchen or the customer warned a few streets before the van stops.
Watch out
Distance and Name are both required; a threshold set too wide fires while the driver is still far away.
3

Task Assigned

Instant trigger

In Zapier“Triggers when an Onfleet task is assigned to a driver or a team.”

Starts your Zap as soon as an Onfleet task lands on a driver or a team, to a driver or to a whole team.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
logging who carries which delivery in your planning sheet, so the office knows who to call when a customer asks.
Watch out
it only reports the assignment; pair it with Task Unassigned if you track ownership over time.
4

Task Cloned

Instant trigger

In Zapier“Triggers when an Onfleet task is cloned via the dashboard or the API. Note that the TaskCreated trigger will not fire when a task is simply cloned.”

Reacts to a copied task, whether the copy was made in the dashboard or through the API.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a laundry service that duplicates a regular customer's pickup and wants each copy counted in its billing tool.
Watch out
Task Created stays silent when a task is simply cloned, so a Zap built only on Task Created misses every copy.
5

Task Complete

Instant trigger

In Zapier“Triggers when an Onfleet task is completed by a driver.”

Goes off when a driver finishes a task successfully. This is the event most follow-ups hang on: invoices, review requests, stock updates.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a pharmacy delivery service that closes the order in its back office the moment the bag is handed over.
Watch out
failures have their own trigger, Task Failed, so build a separate Zap for them.
6

Task Created

Instant trigger

In Zapier“Triggers when an Onfleet task is created.”

Runs each time a task is created in Onfleet, which makes it the natural start for anything that reacts to newly planned deliveries.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
sending the customer a booking confirmation from your own email tool as soon as the delivery is planned.
Watch out
clones do not count as creations; if a Zap of yours creates tasks too, filter them out or you will loop.
7

Task Delayed

Instant trigger

In Zapier“Triggers when an Onfleet task has a delay time greater than or equal to a user-defined threshold, in seconds.”

Fires once a task runs late by at least the number of seconds you set, between 0 and 20000. You decide what counts as late.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a furniture retailer whose support team wants a heads-up on late deliveries before the customer picks up the phone.
Watch out
the threshold is in seconds, not minutes; typing the minutes you had in mind gives a delay sixty times shorter.
8

Task Deleted

Instant trigger

In Zapier“Triggers when an Onfleet task is deleted.”

Tells your other tools that a task is gone from Onfleet, so they do not keep waiting on a delivery that will never happen.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
removing the matching line from a shared delivery calendar when a dispatcher deletes the stop.
Watch out
nothing stops a deletion here; this trigger reports it after the fact, so keep any backup you need elsewhere.
9

Task ETA

Instant trigger

In Zapier“Triggers when the Onfleet task ETA is less than or equal to a user-defined threshold.”

Fires when the driver's estimated arrival drops to or below a threshold you define in seconds, from 0 to 20000.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a technician visit where the customer needs time to get home, so a message goes out when the van is close.
Watch out
ETA Threshold is required and measured in seconds; Task Arrival is the distance-based alternative.
10

Task Failed

Instant trigger

In Zapier“Triggers when an Onfleet task is completed with a failure.”

Signals a task that the driver closed as a failure.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an e-commerce brand that books a second attempt or a return pickup without waiting for the evening report.
Watch out
a Zap that creates a new task after each failure can pile up attempts; a filter keeps it to the cases you really want to retry.
11

Task Started

Instant trigger

In Zapier“Triggers when an Onfleet task is started.”

The moment a driver begins a task is the point where the delivery stops being a plan and becomes a trip.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
switching an order to "out for delivery" in your shop so the customer sees progress in their account.
Watch out
once a task has started, Update Order can no longer change its recipient or completion requirements.
12

Task Unassigned

Instant trigger

In Zapier“Triggers when an Onfleet task is unassigned from a driver or a team.”

Whenever a task is taken off a driver or a team, this one reports it going back to being nobody's job.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
alerting the dispatch lead in a team chat when a stop is left without a driver late in the day.
Watch out
only the Name box is required; a filter keeps the alerts to the stops that matter to you.
13

Task Updated

Instant trigger

In Zapier“Triggers when an Onfleet task is updated, including assignment, feedback, and attachment (photo, signature) changes.”

The broadest trigger of the set: it reacts to changes on a task, including assignment, customer feedback and attachments such as a photo or a signature.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
filing the proof-of-delivery signature in your customer folder as soon as it is attached.
Watch out
it fires often; add a filter, and never let the same Zap update that task, or it restarts itself.
14

Worker Duty

Instant trigger

In Zapier“Triggers when a driver (worker) changes status (0 for off-duty, 1 for on-duty).”

Follows your drivers rather than your tasks: it fires when a driver goes on or off duty, reported as 1 for on duty and 0 for off.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
filling a timesheet with the start and end of each shift without asking drivers to clock in twice.
Watch out
the status arrives as a number, so a filter on it must use a number rule, not a text one.
Actions

The 7 Onfleet actions

Onfleet gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Cancel Order

Action

In Zapier“Cancel an order in Onfleet given the order ID”

Cancels an order in Onfleet from its order ID, so drivers stop seeing a delivery that is no longer wanted.

When to use it
a refund issued in your payment tool that should pull the delivery off the road at once.
Watch out
only the full Onfleet order ID works, so it must travel from an earlier step of the Zap.
2

Clone Order

Action

In Zapier“Creates a copy of an order in Onfleet given the order ID”

Makes a copy of an existing order, so a repeat delivery does not need to be typed again.

When to use it
a wholesaler reordering the same drop for a regular client whenever their sheet flags a refill.
Watch out
it needs the full-length Onfleet order ID of the original; the Onfleet order ID set at creation, not your shop's own reference.
3

Create Order

Action

In Zapier“Creates an order in Onfleet”

Builds a full Onfleet order, with a pickup address and a dropoff address, from data held in another app.

When to use it
pushing each paid web order straight into dispatch, no manual entry.
Watch out
Address Line 1 takes the street number and name only; put the apartment there, or a vague place name, and the address will not be located.
4

Create Task

Action

In Zapier“Creates a pickup or dropoff task.”

Creates one task, either a pickup or a dropoff, with its recipient, location and assignment choice.

When to use it
turning a return request from your helpdesk into a pickup for the next driver nearby.
Watch out
six boxes are required, including Merchant, Executor and whether you have coordinates; answer each before testing.
5

Create Linked Pickup & Dropoff Tasks

Action

In Zapier“Creates a linked pickup and dropoff task.”

Creates a pickup and a dropoff tied together, so one must be done before the other. By default the pickup comes first.

When to use it
a courier collecting from a restaurant and delivering to a diner in one linked job.
Watch out
choose Dropoff then Pickup in Task Link Order only when the reverse really applies, since it makes the dropoff a prerequisite to the pickup.
6

Create Task (Template Use)

Action

In Zapier“Creates a single task. Used for simple zap templates only.”

A simplified single-task creator that Onfleet keeps for simple Zap templates, with the address split into plain boxes.

When to use it
starting from one of the ready-made Onfleet templates in Zapier rather than from a blank Zap.
Watch out
when you provide coordinates, the address fields are only shown to people; the coordinates decide where the driver goes.
7

Update Order

Action

In Zapier“Updates an order in Onfleet given the order ID”

Changes an existing order: who gets notified at pickup and dropoff, and what proof the driver must collect.

When to use it
requiring a signature on high-value orders flagged in your shop after checkout.
Watch out
each field replaces the current value, and recipients and requirements are no longer updated once the task has started.
When it breaks

When an Onfleet Zap breaks

Zapier links no help article to Onfleet, so these cases combine the general Zapier limits with what the Onfleet fields themselves warn about.

Before rebuilding a Zap, check these six. For anything else, the Zapier troubleshooting guide walks through the usual fixes.

  • Yesterday's deliveries are ignored

    A Zap only reacts to what happens after it is switched on. Tasks completed before that are never picked up; moving that backlog is a separate job.

  • Task Updated feeds itself

    A Zap that changes the very task its trigger watches starts itself again and again, and burns through your task count fast.

  • A bulk import gets held back

    If a huge batch of tasks lands at once after an import or a migration, Zapier's flood protection can hold the runs instead of firing them all.

  • The address is not found

    Address Line 1 is for street number and name only. Apartment details or a vague place there stop Onfleet from locating the stop.

  • Update Order changes nothing

    Recipients and completion requirements are frozen once the task has started. An update sent after that point leaves them as they were.

  • Clones slip past Task Created

    A cloned task does not fire Task Created. If your Zap must see every new stop, add a second Zap on Task Cloned.
Need help

Need help automating Onfleet with Zapier?

A person reads every message.

FAQ

Onfleet and Zapier: the questions people ask

01Is the Onfleet Zapier integration free?
On the Zapier side, yes, within the free plan's limits. Onfleet is not reserved to paid plans, so it works with 100 tasks a month and unlimited Zaps. The catch is size: a free Zap has two steps, one trigger and one action. Task Failed then Create Task fits. Add a filter to keep only some failures and you need a paid plan. Your Onfleet subscription is a separate matter and is not covered here.
02How many tasks does an Onfleet Zap use?
One per action that succeeds, each time the Zap runs. The trigger is free, so the fourteen Onfleet events cost nothing by themselves, however many deliveries you run. A Zap that creates a pickup after each failure uses one task per failure. A failed action is not counted. Watch broad triggers like Task Updated: they fire often, and every run that reaches an action spends a task. Check your usage after the first real runs.
03Is Onfleet real time with Zapier?
Yes. All 14 Onfleet triggers are instant: Onfleet calls Zapier the moment the event happens, so your Zap starts right away on every plan, including Free. The polling intervals you may read about elsewhere (15 minutes on Free, down to 1 on Team and Enterprise) apply to apps that are checked on a timer, not to Onfleet. In the editor, a lightning bolt confirms an instant trigger. That speed is the main reason Onfleet works well for customer alerts.
04What do you need to connect Onfleet to Zapier?
An Onfleet account and a Zapier account. From the Apps page in Zapier, click + Add connection, choose Onfleet, sign in in the tab that opens and grant access. You also need access to the tasks and orders the Zap will touch. If a partner delivers for you, it must already be a connected Onfleet organization to be chosen as Executor in Create Task. Fields such as webhook names are filled later, inside each Zap.
05Why doesn't Task Created fire when a task is cloned?
Because Onfleet treats a clone as a different event. When a task is copied, from the dashboard or the API, only Task Cloned fires; Task Created stays silent. A Zap that must see every new stop needs both: one Zap on Task Created and another on Task Cloned, or you miss every duplicate. The same logic matters for reporting, since cloned tasks would otherwise vanish from your counts. Test both Zaps once before publishing.
06What if the Onfleet operation you need is not in Zapier?
Then it is not available for this app in Zapier. The integration offers 14 triggers, 7 actions and no search, and that list is complete: there is no action for drivers or teams, and no way to look up an order. Options are to fetch the missing value in another step of the Zap, to handle that part in Onfleet directly, or to check what the same app exposes elsewhere.
07Zapier, Make or n8n for Onfleet?
Decide by criteria, not by brand. On Zapier, the 14 Onfleet triggers are instant even on the free plan, and the 7 actions cover orders and tasks. If your flows need many steps, compare how each platform counts usage, since every successful action on Zapier is a task. In every case, check which Onfleet operations each platform exposes, and whether its triggers react at once or on a timer, since that decides how fast a customer alert goes out.
Same platform

Other docs you might need on this stack.

Browse all integrations