FlowRunner
Pricing
Theme

Onfleet

Logistics

Last-mile delivery management for FlowRunner. Create and dispatch delivery tasks, manage drivers and teams, define reusable destinations and recipients, and auto-dispatch routes over the Onfleet API.

26 actions available
A new e-commerce order arrives that needs same-day delivery
Agent reads the customer address and order value
Agent geocodes the destination and confirms the recipient phone is valid
Agent flags orders above a value threshold or with an address it could not geocode cleanly
Agent creates the task and assigns it to the right team for routine orders
Agent posts the flagged exceptions to the dispatch channel with the order value and the issue
A dispatcher confirms the destination and dispatches the high-value order; only then does the agent call Auto-Dispatch Team

What This Integration Enables

FlowRunner agents use Onfleet to run delivery operations without a dispatcher touching every order. An agent can create tasks with destinations and recipients supplied inline or referenced by ID, onboard drivers and organize them into teams, auto-dispatch and optimize routes, maintain reusable destinations and recipients so repeat deliveries skip re-geocoding, and share tracking URLs with customers. Get Organization Details doubles as a connection check. The pattern the agent holds to is exception routing: routine orders dispatch on their own, and the deliveries that carry real cost or real uncertainty go to a person first.

Without FlowRunner

Manual order entry Someone retypes each order into Onfleet as a delivery task
Address guesswork A bad address is discovered when the driver is already lost
No exception path High-value deliveries get the same hands-off treatment as everything else

With FlowRunner

Orders become tasks The agent turns each order into a task with a geocoded destination
Validation first The agent catches bad addresses before dispatch, not on the road
Human on high-value A dispatcher confirms the exceptions before a driver is assigned

Use Case Scenarios

High-value delivery exception routing

An order arrives for same-day delivery. The agent creates the destination, validates the recipient phone, and checks the order value. Routine orders get a task and are dispatched with the right team. An order above the value threshold, or one whose address would not geocode cleanly, is posted to the dispatch channel with the order value and the specific issue. A dispatcher confirms the destination and gives the go-ahead. Only then does the agent create and dispatch the task. High-value customers get a human behind their delivery.

Order-to-delivery from commerce

When an order ships in your commerce system, the agent calls Create Task with the customer's inline destination and coordinates, longitude first, to schedule the delivery. It reuses stored destinations and recipients for repeat customers so nothing is re-geocoded or retyped. The order becomes a delivery without manual entry.

Auto-dispatch and customer tracking

After a batch of tasks is created, the agent calls Auto-Dispatch Team to optimize and assign routes across the team. It then reads each task's tracking URL with Get Task and texts it to the customer through a messaging connector. Customers get a tracking link the moment their delivery is on a route.

Human-in-Loop Highlight

The human-in-loop moment in Onfleet is the exception gate on high-value and uncertain deliveries. Routine orders become tasks and dispatch on their own. Two kinds of order do not: one whose value crosses a threshold, and one whose address the agent could not geocode with confidence. For those, the agent posts to the dispatch channel: "This 1,200 dollar order could not be geocoded to a single address. Confirm the destination before I dispatch?" A dispatcher confirms the address and releases the order. Only then does the agent create the task and call Auto-Dispatch Team. The agent handles the volume of clean orders. A person owns the deliveries where a wrong drop is expensive.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

26 actions

Tasks

7
  • Create Task Create a delivery task with a destination and recipient, referenced by ID or supplied inline. Used to turn an incoming order into dispatchable work.
  • Get Task Retrieve a task by ID, including its tracking URL and state. Used to share tracking or check progress.
  • Get Task by Short ID Retrieve a task by its short ID.
  • List Tasks List tasks. Used to reconcile dispatched work against source orders.
  • Update Task Update a task's details. Used to adjust a delivery before it is completed.
  • Complete Task Mark a task complete. Used to close out a delivery from a workflow.
  • Delete Task Delete a task. Used to cancel a delivery that should not proceed.

Workers

6
  • List Workers List drivers. Used to route or report on the fleet.
  • Get Worker Retrieve a single driver.
  • Create Worker Onboard a driver. Used during fleet onboarding automation.
  • Update Worker Update a driver's details.
  • Delete Worker Remove a driver.
  • Get Worker Schedule Read a driver's schedule. Used to plan dispatch around availability.

Teams

5
  • List Teams List delivery teams.
  • Get Team Retrieve a single team.
  • Create Team Create a delivery team. Used to organize drivers by region or shift.
  • Get Team's Tasks List the tasks assigned to a team.
  • Auto-Dispatch Team Optimize and assign routes across a team automatically. Used to dispatch a batch of tasks in one step.

Destinations

2
  • Create Destination Create a reusable geocoded destination. Used so repeat deliveries skip re-geocoding.
  • Get Destination Retrieve a destination by ID.

Recipients

4
  • Create Recipient Create a reusable recipient record. Used so repeat customers skip re-entry.
  • Get Recipient by Name Look up a recipient by name.
  • Get Recipient by Phone Look up a recipient by phone number.
  • Update Recipient Update a recipient's details.

Hubs

1
  • List Hubs List dispatch hubs, such as warehouses or stores.

Organization

1
  • Get Organization Details Read organization settings. Used as a quick connection check.

Start building with Onfleet

$100 in credits. No card required. Connect in minutes.