Resources · Make integration

Onfleet Make integrationAutomate Onfleet with Make.

What does the Onfleet Make integration let you automate? It gives you 20 modules: 14 instant triggers on tasks and drivers, plus actions to create, update, find or delete tasks. This guide walks dispatchers and ops leads through the connection and a first working scenario.

Try the Onfleet integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Onfleet Make integration do for your deliveries?

The Onfleet Make integration links your Onfleet account to Make, so delivery events can start a scenario (the automation you build in Make, a chain of modules) without a line of code. Each module is one brick: a trigger that listens to Onfleet, an action that changes a task, or a search that finds tasks.

Failed drops reach support on their own. Watch Task Failed starts a scenario the moment a driver cannot complete a delivery, and the next module opens a ticket or posts in your support channel. Nobody has to refresh the dashboard to spot the problem.

Online orders turn into tasks. Your shop's new order starts the scenario, then Create a Task builds the delivery in Onfleet from the order data you map into it. Each order is one bundle (one item passed from module to module), and each module that handles it counts as one operation on your Make plan.

Proof of delivery gets filed. Watch Task Updated fires on feedback and attachment changes such as photos and signatures, which is a clean hook to copy them to the folder your accounting team uses.

What Make does not give you here: no scheduled trigger at all, since all 14 triggers are instant (Onfleet calls Make through a webhook), and the actions only touch tasks. For anything else in the Onfleet API, Make an API Call reuses the same connection. If you are still weighing tools, the n8n vs Make comparison helps, and the Onfleet n8n integration page covers the same app on the other side. For a guided start, the Make training builds these habits step by step.

Connect

How do you connect your Onfleet account to Make?

  1. 01

    Copy your API key in Onfleet

    In the Onfleet dashboard, open Settings, then the API section, and copy the API key shown on screen. You need an active Onfleet account for this, and the key is all Make asks for.

  2. 02

    Add an Onfleet module and open the connection

    In your scenario, add any Onfleet module and click Create a connection. A connection is your Onfleet account linked to Make once, then reused by every Onfleet module. The Connection name field is optional, but a clear name helps when you run several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied into the credentials field, or follow the on-screen instructions, then save. Make can now read and write your tasks, and the module fields start listing what it finds in your account.

First scenario

Your first scenario: an online order becomes an Onfleet task

GoalWhen a new order lands in your online store, Make creates the matching delivery task in Onfleet.

  1. 01

    Create an empty scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. This is the canvas where every brick of the automation will sit.

  2. 02

    Start from your store's order trigger

    Search for the app where orders arrive, your shop or your form tool, and pick its new order trigger. Connect that account the same way, so Make knows which orders to pass along.

  3. 03

    Add Create a Task

    Click the + on the right of the first module, search for Onfleet and choose Create a Task. Pick the Onfleet connection you set up earlier, or click Create a connection and paste your API key.

  4. 04

    Map the order into the task

    For each field Make shows in Create a Task, click the matching piece of order data from the first module. You map it once, and every new order fills the task on its own, with nothing retyped.

  5. 05

    Test it with Run once

    Place a test order, then click Run once. Make runs the scenario one time and shows the bundle each module received. Check that the new task shows up in your Onfleet dashboard with the right address.

  6. 06

    Schedule and switch it on

    If the order trigger is a scheduled one, set its clock (every 15 minutes by default, and 15 minutes is the minimum on the Free plan). Then switch the scenario on, and every new order reaches your dispatchers.

Triggers

The 14 Onfleet triggers, and when each one earns its place

14 modules start a scenario when something happens in Onfleet. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Onfleet as soon as it happens.

Onfleet1Watch Recipient SMS Response Missed

Watch Recipient SMS Response Missed

Instant trigger

In Make“Triggers when the recipient responds to a notification via SMS, but the organization is unable to handle it at that time.”

A customer replies to one of your Onfleet text notifications, but nobody on your side can pick it up at that moment. This trigger catches exactly that missed reply and hands it to your scenario, so the message does not vanish inside the dispatch dashboard.

How it fires
instant, Onfleet calls Make through a webhook as soon as the missed reply happens (the lightning badge on the module).
When to use it
route unanswered customer texts to the inbox or chat channel your support team actually watches.
Watch out
it only covers replies your organization could not handle, not every SMS a recipient sends.
Onfleet2Watch Task Arrival

Watch Task Arrival

Instant trigger

In Make“Triggers when worker is arriving, at or closer than the threshold value provided, in meters.”

Think of it as a doorstep alert. The scenario wakes up when a driver gets within a distance you set, counted in meters, of the task's destination.

How it fires
instant, Onfleet pings Make through a webhook the moment the driver crosses that threshold.
When to use it
warn a restaurant kitchen or a warehouse dock that the driver is almost there, so the order is ready at the door.
Watch out
a wide threshold fires long before the driver shows up, a tight one lands after arrival. Try it with Run once on a live task before you trust the number.
Onfleet3Watch Task Assigned

Watch Task Assigned

Instant trigger

In Make“Triggers when a task has been assigned to a worker.”

Once a task lands on a specific driver, this module starts your scenario with that assignment. It is the moment a delivery gets a name attached, which is often what the rest of the business is waiting for.

How it fires
instant, Onfleet notifies Make through a webhook right after the assignment.
When to use it
tell the account manager who is handling the delivery, or log each assignment in a shared sheet for the dispatch lead.
Watch out
every assignment is one run and at least one operation, so a busy dispatch board adds up on your plan.
Onfleet4Watch Task Cloned

Watch Task Cloned

Instant trigger

In Make“Triggers when a task has been cloned.”

Cloning is the quick way to reuse an existing task in Onfleet. This trigger reacts to that copy and gives your scenario the fresh clone to work with.

How it fires
instant, Onfleet sends the clone to Make through a webhook as soon as it exists.
When to use it
keep an external order sheet or billing tool aligned when a dispatcher duplicates a job instead of creating it from scratch.
Watch out
the documentation does not say whether a clone also counts for Watch Task Created. Test both with Run once before you rely on one of them to catch copies.
Onfleet5Watch Task Completed

Watch Task Completed

Instant trigger

In Make“Triggers when a task has been completed by the worker.”

The end of a delivery is where the paperwork begins. This trigger fires when the driver marks the task as completed and passes that finished task to the next module.

How it fires
instant, Onfleet tells Make through a webhook as soon as the driver completes it.
When to use it
mark the order as delivered in your store, send a thank-you email, or start the invoice in your accounting tool.
Watch out
it hears successes only. Failed deliveries have their own trigger, Watch Task Failed, so a scenario built on this one alone never learns about a missed drop.
Onfleet6Watch Task Created

Watch Task Created

Instant trigger

In Make“Triggers when a new task is created.”

Every new task in Onfleet can start a scenario here, which makes it the natural entry point for mirroring your delivery plan somewhere else.

How it fires
instant, Onfleet alerts Make through a webhook as soon as the task is created.
When to use it
copy each new delivery into a planning sheet, a CRM record or the calendar your warehouse team checks.
Watch out
tasks made by your own Create a Task module count as new tasks too. Never let this trigger feed a scenario that creates tasks again, or the two will keep calling each other.
Onfleet7Watch Task Delayed

Watch Task Delayed

Instant trigger

In Make“Triggers when the delay time is greater than or equal to the threshold value provided, in seconds.”

Late deliveries are easier to handle before the customer calls. This trigger starts your scenario once a task's delay reaches the threshold you enter, measured in seconds.

How it fires
instant, Onfleet warns Make through a webhook when the delay hits that value.
When to use it
alert customer service, or send the recipient an honest heads-up through your email or messaging app.
Watch out
the threshold is in seconds, not minutes. Convert the delay you have in mind before typing it, or the alert fires far too early.
Onfleet8Watch Task Deleted

Watch Task Deleted

Instant trigger

In Make“Triggers when a task is deleted.”

Removing a task in Onfleet can leave traces elsewhere: a row in a sheet, an open order, a booked slot. This trigger tells your scenario that the task is gone.

How it fires
instant, Onfleet reports the deletion to Make through a webhook as soon as it happens.
When to use it
clean up the matching row, cancel the order in your store, or post a note to the account manager.
Watch out
treat it as a signal to tidy up, not to rebuild the task. A scenario that recreates deleted tasks would fight your dispatchers every time.
Onfleet9Watch Task ETA

Watch Task ETA

Instant trigger

In Make“Triggers when a worker ETA is less than or equal to the threshold value provided, in seconds.”

This is the trigger behind a timely heads-up that the driver is close. It starts the scenario when the driver's ETA falls to or under a threshold you set, in seconds.

How it fires
instant, Onfleet calls Make through a webhook once the ETA drops to that value.
When to use it
text the recipient through your SMS tool, or let a pickup counter know the courier is minutes away.
Watch out
it counts time, while Watch Task Arrival counts distance in meters. Pick the one that matches the promise you make to customers.
Onfleet10Watch Task Failed

Watch Task Failed

Instant trigger

In Make“Triggers when a task has failed.”

When a delivery cannot be completed, this trigger hands the failed task to your scenario right away, instead of leaving it for someone to find at the end of the route.

How it fires
instant, Onfleet notifies Make through a webhook as soon as the task fails.
When to use it
open a support ticket, warn the customer, or ping the dispatcher in a chat channel so a second attempt gets planned.
Watch out
leave the retry decision to a person. Recreating the task automatically after every failure can loop on an address that will never work.
Onfleet11Watch Task Started

Watch Task Started

Instant trigger

In Make“Triggers when a task has been started by a worker.”

Here the scenario begins as soon as a driver starts working on a task. For the customer, that is the moment the delivery really leaves.

How it fires
instant, Onfleet pushes the event to Make through a webhook right when the driver starts.
When to use it
send an on the way email, or stamp the start in a sheet that tracks how deliveries flow through the day.
Watch out
started does not mean close. If the message should go out near the door, Watch Task ETA or Watch Task Arrival fits better.
Onfleet12Watch Task Unassigned

Watch Task Unassigned

Instant trigger

In Make“Triggers when a task has been unassigned from a worker.”

A task that loses its driver is easy to miss on a busy board. This trigger tells your scenario each time a task is unassigned from a worker.

How it fires
instant, Onfleet reaches Make through a webhook as soon as the assignment is removed.
When to use it
flag the task to the dispatch lead in a chat channel, so nothing sits without a driver.
Watch out
pair it with Watch Task Assigned if you track reassignments, and remember that each of the two events runs its own scenario and uses its own operations.
Onfleet13Watch Task Updated

Watch Task Updated

Instant trigger

In Make“Triggers when a task has been updated, including assignment, feedback, and attachment (photo, signature) changes.”

The widest net of the list. It fires whenever a task changes, including assignment, feedback and attachments such as photos and signatures.

How it fires
instant, Onfleet sends every update to Make through a webhook as it happens.
When to use it
collect proof of delivery, like signatures and photos, into the folder or record your finance team checks.
Watch out
because so many changes count, this scenario runs often. If you only care about one event, such as completion or assignment, the dedicated trigger keeps your operation count lower.
Onfleet14Watch Worker Duty

Watch Worker Duty

Instant trigger

In Make“Triggers when a worker status has changed (0 for off-duty, 1 for on-duty).”

Unlike the other triggers, this one follows drivers rather than tasks. It fires when a worker's status changes between off-duty and on-duty.

How it fires
instant, Onfleet tells Make through a webhook as soon as the status switches.
When to use it
keep a shift log in a sheet, or tell the dispatch lead who just came online.
Watch out
the status comes as a number, 0 for off-duty and 1 for on-duty. Turn it into words before it lands in a message people read.
Modules

What the Onfleet actions and search can do

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

Onfleet1

Create a Task

Action

In Make“Creates a new task in the Onfleet dashboard.”

Builds a new delivery task in your Onfleet dashboard from data another module hands over, so orders stop being copied by hand.

When to use it
right after a new order, booking or form entry in another app, when that event should become a delivery your dispatchers can plan.
Watch out
run it with Run once on a test order first, then check the task in Onfleet before you switch the scenario on.
Onfleet2

Delete a Task

Action

In Make“Deletes a task by its ID.”

Removes one task from Onfleet using its ID, which keeps the dashboard in step with orders cancelled somewhere else.

When to use it
when an order is cancelled in your store or a booking is dropped, and the matching delivery must disappear before a driver takes it.
Watch out
a delete cannot be undone from the scenario. Make sure the ID you map belongs to the right task before activating.
Onfleet3

Get a Task

Action

In Make“Returns a task's information by its ID.”

Fetches the full information of one task from its ID, handy when an earlier step only gives you a reference and you need the rest.

When to use it
in a scenario that stores Onfleet task IDs in a sheet or a CRM, before you write a status or a detail back to the customer record.
Watch out
it reads a single task; to look through several, Search Tasks is the right module.
Onfleet4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Your way out when the listed modules stop short. It calls any endpoint of the Onfleet API with the connection you already set up, no second key needed.

When to use it
when you need something beyond tasks, since the five other modules only create, read, update, delete or search tasks.
Watch out
you write the request yourself, so keep the Onfleet API reference open and test with Run once.
Onfleet5

Update a Task

Action

In Make“Updates a task by its ID.”

Changes an existing task, found by its ID, so the delivery in Onfleet follows what happens in your other tools.

When to use it
when a customer edits the delivery notes or the address in your shop after ordering, and the driver needs the new version.
Watch out
you need the task ID; if you only know the order, find it first with Search Tasks.
Onfleet6

Search Tasks

Search

In Make“Searches for tasks or lists them all.”

Looks for tasks in Onfleet or lists them all, and returns zero, one or many bundles for the modules that follow.

When to use it
when you need to find the task behind an order before updating it, or to build a list of tasks for a report.
Watch out
every task found runs the next modules once, and each run counts as an operation, so narrow the search before connecting heavy steps.
Need help

Need help automating Onfleet with Make?

A person reads every message.

FAQ

Onfleet and Make: the questions that come next

01Is the Onfleet Make integration free?
Yes on the Make side. Onfleet is a standard app, available from the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and allow unlimited active scenarios. You still need an active Onfleet account with an API key, and your Onfleet subscription follows Onfleet's own pricing page.
02What do you need to connect Onfleet to Make?
An active Onfleet account and its API key. In the Onfleet dashboard, go to Settings, open the API section and copy the key displayed on screen. Then add an Onfleet module in Make, click Create a connection, give it a name if you like and paste the key. With a trigger, the documentation says to click Create a webhook first, then Create a connection. The same connection is reused by every Onfleet module in your scenarios.
03Do Onfleet triggers in Make fire in real time?
Yes. All 14 Onfleet triggers are instant: Onfleet calls Make through a webhook as soon as the event happens, whether a task is completed, delayed, failed or a driver goes on duty. There is no scheduled Onfleet trigger to poll. The 15 minute default schedule only matters when your scenario starts from another app's scheduled trigger, like a store order that then feeds Create a Task. In the editor, the lightning badge on each Onfleet trigger shows it is instant.
04What if the Onfleet module you need is missing in Make?
Use Make an API Call. The six Onfleet modules that are not triggers only cover tasks: create, get, update, delete and search. Make an API Call reaches any endpoint of the Onfleet API with the same connection, so there is no second key to manage. You write the request yourself, which asks a bit more care, so test it with Run once before switching the scenario on. The official documentation lists no other limit for this app.
05Should you use Make or n8n for Onfleet?
It depends on the tool your team already runs. On Make, Onfleet comes with 20 modules, including 14 instant triggers, four task actions, one search and Make an API Call for the rest. Onfleet also has an n8n node, so both tools can handle it. Check that the events and actions your process needs are listed on the side you prefer, then build a small test scenario before moving your whole dispatch flow.
Same platform

Other docs you might need on this stack.

Browse all integrations