Shipday

Connect AI agents to Shipday for local delivery dispatch. Agents create delivery orders, advance them through pickup and delivery, assign orders to drivers, and keep the driver roster in sync with your POS or ordering systems.

9 actions API key available

Shipday website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

An online order lands from the storefront with a delivery address inside the service area

Create Order writes the delivery into Shipday with customer, pickup location, instructions, and expected timing

List Drivers pulls the roster and filters to drivers currently active and available

The agent matches the order to a candidate driver by availability and current load

The dispatcher confirms the match, or overrides it, because they know driver three is already stacked and the kitchen is running behind

Assign Order to Driver dispatches the delivery to the confirmed carrier

The customer gets an on-the-way text and the dispatch channel gets the assignment with timing

What This Integration Enables

Local delivery is a real-time operations problem compressed into minutes: the order arrives, a driver must be chosen, the food or package must move, and the customer judges the whole business by what happens in the next half hour. Shipday runs that dispatch loop; this connector wires your other systems into it. FlowRunner agents create delivery orders from POS and storefront events, advance orders through the pickup and delivery lifecycle, assign orders to drivers from the live roster, and keep that roster in sync with the systems where couriers are actually hired and managed. The stance: the dispatcher should not be a data entry clerk. The agent moves the data, and the dispatcher makes the calls that need eyes on the room, which drivers are really available, which kitchen is really behind. - Create dispatch-ready orders from Shopify, POS, and ordering system events - Assign and reassign orders to drivers by carrier ID from the live roster - Advance orders through started, picked up, delivered, and failed states - Sync driver onboarding and offboarding from external systems - Feed live delivery status into support tools and reporting

Without FlowRunner

Dispatch by shouting distance Orders print, someone reads them aloud, and assignment happens by whoever looks least busy

The status board is the dispatcher's memory Which orders are picked up, which are stuck, and which failed lives in one person's head

Roster maintenance after hours New couriers get added to the system whenever someone finds time, so day one is often day two

With FlowRunner

Orders flow straight into dispatch POS and storefront events create Shipday orders within seconds, complete with instructions and timing

Lifecycle tracked as data Started, picked up, delivered, and failed are statuses agents advance and report on, not facts to reconstruct at close

Roster synced from the source Driver onboarding and offboarding flow from your HR or courier system, with invitations sent automatically

Use Case Scenarios

Storefront to driver in under a minute

A [Shopify](/integrations/shopify) order fires the flow. Create Order writes the delivery with the customer's address and instructions, List Drivers surfaces who is active, and the dispatcher taps to confirm the suggested assignment. Assign Order to Driver dispatches it, [Twilio](/integrations/twilio) texts the customer that their order is moving, and the dispatch channel in [Slack](/integrations/slack) logs the assignment. The order that used to wait for someone to notice the printer now waits for nothing.

The delivery ops dashboard that answers the phone

Support gets the eternal question: where is my order? The agent answers it before the call escalates: a scheduled List Orders sweep keeps a live log of active deliveries in [Google Sheets](/integrations/google-sheets), and Get Order pulls full detail, driver, status, timing, for any order number a support rep pastes into the flow. Failed deliveries surface immediately with Update Order Status history attached, so the make-good process starts while the customer is still on the line.

Courier onboarding that ends at the driver app

A new courier clears onboarding in the HR system. The agent calls Add Driver with their name, email, and phone; Shipday sends the app invitation automatically, and the roster update posts to the dispatch channel. When a courier leaves, the offboarding flow checks List Orders for active assignments first, then stages the removal for the ops manager's confirmation. The roster matches reality on both edges, the day it changes.

Human-in-Loop Highlight

Delete Driver permanently removes a carrier from the account, and Shipday's own guidance carries the warning that matters: make sure the driver has no active assigned orders first, because this cannot be undone. An offboarding flow that fires on an HR event without checking the road first could strand in-flight deliveries with no assigned carrier at dinner rush. So FlowRunner offboarding runs in two stages: the agent verifies through List Orders that nothing active is assigned to the carrier, then presents the removal, driver name, assignment history, roster impact, to the ops manager, and Delete Driver executes only on their confirmation. Delete Order sits behind the same gate for the same reason: it erases the delivery record by internal order ID with no recovery, and that record is your evidence when a customer disputes what happened. Dispatch moves at machine speed. Permanent removals move at the speed of a person saying yes.

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

9 actions

Orders

List Orders Retrieves delivery orders, active ones by default, with customer, pickup, driver, and status details for each. The live board behind dashboards and support flows.
Get Order Retrieves a single order's full details by its human-readable order number: customer, pickup, driver assignment, cost, timing, and current status.
Create Order Creates a new delivery order for dispatch, requiring an order number, customer name and address, and pickup name and address, with optional contact details, instructions, cost, and expected timing. Orders are created unassigned.
Update Order Status Advances an order through its delivery lifecycle by internal order ID: started, picked up, delivered, or failed, mapped to the corresponding Shipday status token.
Assign Order to Driver Dispatches an order to a specific driver by carrier ID. Requires the internal order ID and the driver's carrier ID from List Drivers.
Delete Order Permanently deletes a delivery order by its internal numeric order ID, not the order number. Cannot be undone; gated behind human confirmation in FlowRunner flows.

Drivers

List Drivers Retrieves all registered drivers with carrier ID, name, email, phone, and availability status. The roster read behind every assignment.
Add Driver Adds a new driver to the account with name, email, and phone. Shipday sends the driver an invitation to join through the Shipday driver app.
Delete Driver Permanently removes a driver by carrier ID. Cannot be undone, and the driver must have no active assigned orders. The removal this page's human gate exists for.

Frequently Asked Questions

What can FlowRunner do with Shipday?

FlowRunner agents can run List Orders, Get Order, and Create Order in Shipday, plus 6 more actions.

Does connecting Shipday to FlowRunner require OAuth?

No. Shipday connects to FlowRunner with an API key, no OAuth flow required.

Can Shipday trigger a FlowRunner workflow automatically?

Shipday doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Shipday

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

Start Building Free Talk to us