Send a Twilio SMS to a customer when an Onfleet driver is arriving
When an Onfleet driver is arriving at a delivery or gets closer than a set distance, this workflow texts the customer through Twilio, so they know to expect the driver.
Onfleet
Twilio2 steps Setup ~5 min Used on 1.1k sites Free to import

What this workflow does
A driver who reaches the door before the customer is ready has to wait or try again later. A text shortly before arrival gives them a chance to come to the door or leave instructions. This workflow sends that text from your Twilio number using Onfleet's arrival event.
The Onfleet trigger is Driver Arriving, or Closer Than, which fires when a driver is arriving or closer than a certain number of meters. FlowMattic passes the task data to Twilio, where Send SMS sends a text to a number. You map the recipient's phone number from the Onfleet task and write the message, adding details such as the driver's name if the event carries them.
The SMS goes to whatever number you map, so make sure your Onfleet tasks hold the customer's phone. Task History shows each run, including the number used and Twilio's response.
Grocery and meal deliveries
Customers get a text as the driver approaches, so chilled or hot food isn't left waiting on the doorstep.
Furniture and large items
A heads-up text tells the customer to be ready to receive a delivery that needs someone at home.
Pharmacy drop-offs
Patients receive an arrival text so they can meet the driver for a delivery that needs a signature.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Onfleet Driver Arriving, or Closer ThanFires when an Onfleet driver is arriving at a task's destination or is closer than a certain distance. The task data becomes available to use in the SMS. Connect Onfleet on import.
Twilio Send SMSSends an SMS to a number using Twilio. Map the customer's phone number from the Onfleet task, write the text, and connect your Twilio account with a number that can send SMS.
What you need
- FlowMatticCore
- Onfleet AccountAccount
- Twilio AccountAccount
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- Run one test delivery with your own phone number on the Onfleet task, so you can see which field holds the recipient's phone and how the text reads.
- Add a Filter after the trigger that continues only when the recipient phone field is not empty, so tasks without a number don't produce failed Twilio sends.
- Pair it with a second workflow on Onfleet's Task Completed trigger to text the customer once the delivery is done.
Questions about this workflow
Where does the customer's phone number for Twilio come from?
From the Onfleet task data the trigger receives. Map the recipient phone field into Twilio's Send SMS step, and check a test run to confirm the right number is used.
What happens if an Onfleet task has no phone number?
Twilio can't send to an empty number and returns an error. Task History shows that error on the Twilio step for that run.
How close does the Onfleet driver have to be?
The trigger fires when the driver is arriving or closer than a certain number of meters. Test with a real route to see when the text goes out for your setup.
Can the customer reply to the Twilio text?
Any answer the customer sends lands on your Twilio number. This workflow doesn't handle them, but Twilio's Incoming SMS trigger can start a separate workflow.
More Communication workflows
Other ready-to-import templates from the same category.







Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted