--- title: "Order Desk Integration" description: "Connect AI agents to Order Desk to centralize and route ecommerce orders. Agents create, update, and delete orders, attach shipment tracking, keep inventory items in sync, and read store settings to discover fulfillment folders." url: https://flowrunner.ai/integrations/order-desk date_modified: 2026-08-04T10:04:16-07:00 --- # Order Desk [E-commerce](https://flowrunner.ai/integrations/category/e-commerce) Connect AI agents to Order Desk to centralize and route ecommerce orders. Agents create, update, and delete orders, attach shipment tracking, keep inventory items in sync, and read store settings to discover fulfillment folders. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 12 actions · API key · available [Order Desk website](https://orderdesk.com/) · [Platform Documentation](https://apidocs.orderdesk.com/) · Capability data verified 2026-07-27 1. A new order lands from the storefront with items, addresses, and source metadata 2. Get Store Settings maps folder IDs to their names so routing targets real statuses, not guesses 3. Create Order writes the order with SKU codes, quantities, and shipping address into the intake folder 4. The agent validates the shipping address and flags mismatched country and postal code pairs 5. An ops lead reviews the flagged orders before the folder move that releases them to fulfillment 6. Update Order moves cleared orders into the fulfillment folder the 3PL watches 7. Add Shipment writes the tracking number, carrier, and service level back once the label exists 8. The team channel gets the shipment confirmation with the tracking URL ## What This Integration Enables Order Desk's core idea is the folder: an order is always in exactly one, and the folder is its status. That makes order operations legible to automation in a way most order systems are not, because routing becomes a folder move instead of a status flag buried in metadata. FlowRunner agents work that model directly: they create orders from any source, read and update them, move them between folders as they clear checks, attach shipment tracking, and keep inventory items honest by SKU. - Centralize: pull orders from carts, marketplaces, and wholesale forms into one folder structure - Route: move orders through validation, hold, and fulfillment folders based on checks a person defined - Close the loop: write tracking numbers, carriers, and service levels back onto orders as shipments happen - Reconcile: keep stock counts, prices, costs, and locations in sync with warehouse and supplier systems The [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) line sits exactly where digital becomes physical: the folder move that releases an order to fulfillment is cheap to make and expensive to unmake, so exceptions wait for a person. ### Without FlowRunner **Every cart is its own workflow**: Shopify, Etsy, and wholesale orders each follow a different manual path to the same warehouse **Tracking numbers travel by hand**: Someone copies tracking from the carrier portal into the order record, eventually **Stock counts drift**: The store sells what the warehouse no longer has, and the apology email follows ### With FlowRunner **One switchboard, many sources**: Orders from every channel land in folders that mean something, routed by rules the team wrote **Tracking closes its own loop**: The label purchase writes the shipment record back onto the order the same minute **Inventory syncs on schedule**: Stock counts, prices, and costs update by SKU from the systems that actually know them ## Use Case Scenarios ### Three carts, one fulfillment path Orders arrive from [Shopify](https://flowrunner.ai/integrations/shopify), Etsy, and a wholesale order form. The agent normalizes each into Create Order with the source recorded, SKU codes mapped, and the correct folder assigned from the map read out of Get Store Settings. Unshipped orders from List Orders route to [ShipBob](https://flowrunner.ai/integrations/shipbob) for fulfillment, or to [ShipStation](https://flowrunner.ai/integrations/shipstation) when the item ships from the studio. When the label is purchased, Add Shipment writes the tracking number and carrier onto the order, and the customer-facing systems read it from one place. Three channels, one operational truth. ### Inventory that matches the shelf The warehouse exports a nightly stock file to [Google Sheets](https://flowrunner.ai/integrations/google-sheets). The agent walks it and calls Add Inventory Item per row, which updates the existing item when the SKU code already exists, so the same action handles both new products and count corrections. A morning pass over List Inventory Items flags SKUs below their reorder threshold and posts the shortlist to [Slack](https://flowrunner.ai/integrations/slack) with location and cost attached. Price changes from the pricing sheet flow the same way. The store stops selling inventory the shelf does not have. ### The exception desk that empties itself A scheduled sweep over List Orders in the intake folder runs the checks humans used to do by eye: address completeness, country and postal code agreement, duplicate detection against recent orders by email and item set. Clean orders move to fulfillment through Update Order automatically. Flagged orders post to the ops channel with the evidence, and a person disposes of each: fix the address and release, hold for customer contact, or, for a confirmed duplicate, approve the Delete Order that permanently removes it. The team touches only the orders that need judgment, which on most days is a handful. ## Human-in-Loop Highlight In Order Desk, the folder move is the trigger everything downstream watches: Update Order setting the Folder to fulfillment is the moment a 3PL picks the order, prints the label, and puts a box in motion. A package cannot be un-shipped, and recalling one costs return postage, restocking, and an annoyed customer. So the agent releases only orders that pass every check, and everything flagged, address mismatches, unusually large quantities, suspected duplicates, waits in the hold folder for a person. The same gate covers Delete Order, which permanently removes an order and cannot be undone; an agent may propose a duplicate for deletion with the matching evidence side by side, but a person confirms which order survives before anything is destroyed. 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 12 actions ### Orders 5 - **List Orders** Retrieves orders filterable by folder, source, customer email, and a UTC creation date range, newest first, up to 500 per page. The read behind routing sweeps and exception checks. - **Get Order** Retrieves one order completely: addresses, items, notes, discounts, and shipment records. - **Create Order** Creates an order with items, SKU codes, prices, quantities, weights, and customer and shipping addresses, placed into a chosen folder. - **Update Order** Updates supplied fields on an order, including the Folder that represents its status. The release-to-fulfillment move, and the reason this page has a human gate. - **Delete Order** Permanently deletes an order. Cannot be undone, so it runs only on human confirmation. ### Shipments 2 - **Add Shipment** Attaches a tracking record to an order with tracking number, carrier, and service level, marking items shipped. The tracking URL generates automatically from the carrier. - **List Shipments** Retrieves all tracking records on an order, for notifications, reporting, and customer service lookups. ### Inventory 3 - **List Inventory Items** Retrieves inventory items by free-text search, exact SKU code, name, or warehouse location, with stock counts, prices, costs, and weights. - **Get Inventory Item** Retrieves one item's stock level, price, cost, weight, metadata, and variations. - **Add Inventory Item** Adds an inventory item, or updates the existing one when the SKU code matches. The single upsert that keeps counts, prices, and locations current. ### Store 2 - **Get Store Settings** Retrieves the store configuration including the full folder map of IDs to names. Read this first so every folder move targets a real status. - **Test Connection** Verifies the Store ID and API Key against the test endpoint. The first step of every new deployment checklist. ## Frequently Asked Questions ### What can FlowRunner do with Order Desk? FlowRunner agents can run List Orders, Get Order, and Create Order in Order Desk, plus 9 more actions. ### Does connecting Order Desk to FlowRunner require OAuth? No. Order Desk connects to FlowRunner with an API key, no OAuth flow required. ### Can Order Desk trigger a FlowRunner workflow automatically? Order Desk doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Order Desk?** This integration exposes Order Desk to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/order-desk. Site index: https://flowrunner.ai/llms.txt