LionWheel
LogisticsConnect AI agents to LionWheel, a local delivery management and route planning platform. Agents create and update deliveries, optimize daily driver routes, and manage customer companies so last-mile dispatch runs without manual coordination.
What This Integration Enables
LionWheel is written for the company that is the delivery operation, not for a shipper buying delivery from someone else. The clearest evidence is in the credentials: company operations require an organization token, while the customers you deliver for hold a scoped customer key. So the same connectors behave differently depending on whose chair you configured them from, and that is a design-time decision worth making deliberately. Configured as the shipping company, an agent can onboard and maintain the businesses it serves, plan and reorder driver days, and update individual visits. Configured as a customer, it pushes its own orders in and reads its own deliveries back.
FlowRunner agents create deliveries from incoming orders, move them through the LionWheel status set as the day progresses, and attach documents to a delivery from a public file URL. A delivery can be looked up three ways: by its LionWheel task ID, by the external order ID from the originating system, or by the recipient's phone number. The three lookup paths matter more than they sound. Support agents get a phone number, order systems have an order number, and only LionWheel has the task ID. A workflow that can only search one way ends up asking a human to translate identifiers, which is exactly the clerical work the agent was supposed to remove.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Store order becomes a tracked delivery
An order is placed in Shopify or an internal system. The agent calls Create Delivery with the recipient, the address, the requested date, and where relevant the amount to collect, which LionWheel expresses in cents rather than currency units. It returns the tracking link to the customer by email and writes the LionWheel task ID back onto the order record. Later status checks use Get Deliveries By Order ID, so the two systems stay joined by an identifier the merchant already owns rather than one the agent has to remember.
Support answers a delivery question without opening the dispatch app
A customer messages asking where their delivery is. The support agent has a phone number and nothing else. The FlowRunner agent calls Get Deliveries By Phone, finds the open delivery, reads its status and its position in the driver's day from Get Daily Route, and replies inside the support thread. If the delivery is already marked Failed, the agent does not improvise an explanation. It hands the case to a person with the status, the driver, and the visit detail already gathered.
Client onboarding for a delivery contract
A new business signs a delivery agreement. The agent calls Create Company with the client's details, then keeps that record current with Update Company as billing contacts and addresses change upstream. Because company operations need the organization token, this workflow runs under the shipping company's credentials while the client's own workflows run under their scoped key. Access separation is enforced by the platform rather than by convention.
Human-in-Loop Highlight
The gate sits on Optimize Daily Route. Reordering a driver's day is not a routing calculation, it is a re-promise. Every stop already carries an expectation somebody made: a clinic that closes at noon, a customer who took the afternoon off, a restaurant that cannot accept a delivery during service. LionWheel will happily return a shorter total sequence, and the shorter sequence is often correct, but the stops that move to the back of it are the ones whose promises break. So the agent computes the optimization, diffs it against the current order, and stops before applying it. It posts a short message: "Optimizing route 14 saves nine stops of backtracking. Three visits move later than their requested window, including Ramat Gan clinic which closes at 12:00. Apply, apply but pin the clinic, or leave as is?" The dispatcher makes the call, because the dispatcher is the only party who knows which promises are soft. That is the digital andon cord in the middle of a working shift: the agent does the arithmetic, the person owns the commitment.
Agent Capabilities
14 actionsDeliveries
6- Create Delivery Creates a delivery from an upstream order, including recipient details, the requested date, and any amount to collect, which is expressed in cents. Used to push shop or ERP orders into dispatch automatically.
- Get Delivery Retrieves a delivery by its LionWheel task ID. Used when a workflow already holds the LionWheel identifier.
- Get Deliveries By Order ID Finds deliveries by the external order identifier from the originating system. Used to keep the order record and the delivery record joined by a reference the merchant already owns.
- Get Deliveries By Phone Finds deliveries by the recipient's phone number. Used in support workflows where the phone number is the only identifier available.
- Update Delivery Modifies a delivery, including reassigning a driver or moving it to Completed, Canceled, or Failed. Used to keep status honest as the day progresses.
- Add Document Attaches a document to a delivery from a publicly accessible file URL. Used to file a signed receipt, a customs form, or a delivery note against the job.
Routes and Visits
5- Get Daily Route Returns a driver's route for a given day with its ordered stops. Used to see where a delivery sits in the day before answering a customer.
- Optimize Daily Route Computes an optimized stop sequence for a driver's day. Used to cut backtracking, and reviewed by a person before it is applied because it changes when every customer is served.
- List Routes Returns all routes for a given day. Used for shift planning and for reporting across drivers.
- Get Visit Retrieves a single stop on a route. Used to inspect one delivery attempt in detail.
- Update Visit Modifies a stop on a route. Used to correct or annotate an individual visit without rewriting the whole delivery.
Companies
3- Get Company Retrieves a customer company you deliver for. Requires the organization token. Used to check the current record before writing to it.
- Create Company Registers a new customer company. Requires the organization token. Used to onboard a new delivery client from the same record that closed the contract.
- Update Company Updates an existing customer company. Requires the organization token. Used to keep contacts and addresses current without duplicate data entry.
Frequently Asked Questions
What can FlowRunner do with LionWheel?
FlowRunner agents can run Create Delivery, Get Delivery, and Get Deliveries By Order ID in LionWheel, plus 11 more actions.
Does connecting LionWheel to FlowRunner require OAuth?
No. LionWheel connects to FlowRunner with an API key, no OAuth flow required.
Can LionWheel trigger a FlowRunner workflow automatically?
LionWheel doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with LionWheel
$100 in credits. No card required. Connect in minutes.