--- title: "ShipBob Integration" description: "Full 3PL automation with 5 real-time fulfillment triggers. Agents respond to shipment events, manage orders, track inventory, process returns, and handle warehouse receiving orders." url: https://flowrunner.ai/integrations/shipbob date_modified: 2026-08-01T02:40:32-07:00 --- # ShipBob [Logistics](https://flowrunner.ai/integrations/category/logistics-fulfillment) Full 3PL automation with 5 real-time fulfillment triggers. Agents respond to shipment events, manage orders, track inventory, process returns, and handle warehouse receiving orders. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 5 triggers · 20 actions · OAuth · available [ShipBob website](https://shipbob.com/) · Capability data verified 2026-08-12 1. On Shipment Exception fires in ShipBob 2. Agent retrieves order details, customer contact info, and exception type 3. Agent sends customer automated address correction form for address exceptions 4. Operations team receives Slack message with order value and resolution options for carrier issues 5. Agent executes selected resolution after manager responds 6. High-value order exceptions paused for operations team to select resolution path ## What This Integration Enables ShipBob integration gives FlowRunner agents both event response and operational control over fulfillment. Agents react to fulfillment events in real time, manage the order lifecycle from creation through cancellation, handle warehouse receiving, track inventory, and process returns. The result: a fulfillment operation that runs autonomously with human escalation only on genuine exceptions. ### Without FlowRunner **Manual exception triage**: Ops team monitors ShipBob dashboard throughout the day for exception flags **Generic customer responses**: All exceptions get the same automated message regardless of type or order value **Returns processed manually**: Returns handling requires staff to check condition, decide on refund, and update inventory ### With FlowRunner **Instant exception response**: Customer notified and options presented within minutes of ShipBob exception event **Exception-type routing**: Address issues get correction forms; carrier issues get human review **Automated returns processing**: Resalable returns trigger refund workflow; damaged items routed for manager decision ## Use Case Scenarios ### Shipment Exception Response On Shipment Exception fires. The agent retrieves the order details, the customer's contact information, and the exception type from ShipBob. If it is an address correction needed, the agent sends the customer an automated email with a form to correct their address. If it is a carrier issue, the agent routes to the operations team via Slack with full context: "Shipment #SB-44221 hit a delivery exception. Customer order value: $340. Here are the resolution options." The ops manager selects the resolution. The agent acts. ### Inbound Inventory Workflow A purchase order is approved in NetSuite. The agent creates a ShipBob WRO for the incoming inventory, sends the supplier the receiving instructions, and creates a task in Asana for the receiving team. When ShipBob confirms receipt of the goods, Get Inventory confirms updated stock levels. The agent updates the product availability in the e-commerce platform and notifies the inventory manager via Slack. ### Returns Processing On Return Completed fires. The agent retrieves the return details: order ID, SKU, condition, reason code. For items in resalable condition, it records the inventory receipt and triggers the refund workflow in Stripe. For items flagged as damaged, it pauses and routes to the operations manager: "Return received for \[SKU\], marked as damaged. Approve refund or initiate damage claim?" The manager decides. The agent processes. ## Human-in-Loop Highlight When a shipment exception involves a high-value order above a configurable threshold, the agent does not send a generic automated response. It routes to the operations team via Slack with the complete picture: order value, customer history, exception type, and recommended resolution options. The team selects the path. The agent executes it. High-value customers get a human decision behind their resolution, not a bot working from a script. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 20 actions ### Order Management 7 - **Create Order** Creates a new order in ShipBob for fulfillment. Used in order management automation: when an order is confirmed in your e-commerce platform or ERP, the agent creates the ShipBob fulfillment order immediately, eliminating the manual order entry step. - **Get Order** Retrieves a specific order with current status and shipment details. Used to check order state in customer service and tracking workflows. - **Get Orders** Returns a list of orders matching filter criteria. Used in bulk processing, reporting, and exception monitoring workflows. - **Cancel Order** Cancels a ShipBob order before it ships. Used in order modification workflows when a customer cancels or changes their order before fulfillment begins. - **Estimate Fulfillment Cost** Returns a cost estimate for fulfilling a specific order. Used in pricing and margin validation workflows before an order is confirmed. - **Batch Cancel Shipments** Cancels multiple shipments at once. Used when a batch needs to be recalled due to product issues or shipping errors. - **Mark Tracking Uploaded** Marks an order as having tracking information uploaded. Used in fulfillment confirmation workflows. ### Product Management 2 - **Create Product** Creates a new product in ShipBob's catalog. Used in product launch workflows: when a new SKU is added to your catalog, the agent creates it in ShipBob simultaneously. - **Get Products** Returns the product catalog. Used in inventory planning and catalog synchronization workflows. ### Inventory and Shipments 3 - **Get Inventory** Returns current inventory levels by product and fulfillment center. Used in stock monitoring workflows: agents check inventory daily and alert when levels fall below reorder thresholds. - **Get Shipment** Retrieves a specific shipment with tracking and status detail. Used in customer service workflows when tracking information is needed. - **Create Return** Initiates a return in ShipBob. Used in returns processing automation: when a customer requests a return in your e-commerce platform, the agent creates the ShipBob return and sends the customer their return label automatically. ### Warehouse Receiving Orders (WROs) 8 - **Create WRO** Creates a warehouse receiving order for inbound inventory. Used in purchase order workflows: when a PO is confirmed with a supplier, the agent creates the WRO in ShipBob so the warehouse is ready to receive the inventory. - **Get WROs** Returns a list of warehouse receiving orders. Used in inventory planning and receiving status workflows. - **Get WRO** Retrieves a specific WRO with box and item detail. Used to track inbound inventory status. - **Get Fulfillment Centers** Returns the list of ShipBob fulfillment centers. Used when agents need to route orders or WROs to specific facilities. - **Get WRO Boxes** Returns the box-level detail for a WRO. Used in receiving verification workflows. - **Get WRO Box Labels** Retrieves printable labels for WRO boxes. Used in warehouse operations automation. - **Cancel WRO** Cancels a pending warehouse receiving order. Used when a purchase order is canceled before the goods are received. - **Set WRO External Sync** Marks a WRO as synced with an external system. Used to prevent double-processing in multi-system inventory environments. ## Triggers 5 triggers ### Event Triggers 5 - **On Order Shipped** Fires the moment ShipBob marks an order as shipped. The most frequent trigger in e-commerce operations. When this fires, agents send shipping confirmation emails with tracking numbers, update the ERP with the shipment record, and log the fulfillment in the CRM deal. - **On Shipment Delivered** Fires when delivery is confirmed by the carrier. Used to trigger post-delivery workflows: request a review, trigger the warranty registration sequence, update customer lifetime value in the CRM. - **On Shipment Exception** Fires when a shipment hits an exception: delivery failure, address issue, carrier problem. This is where the human-in-loop matters most. The agent surfaces the exception immediately with order details, customer contact information, and resolution options. - **On Shipment On Hold** Fires when a shipment is placed on hold in ShipBob. Used to trigger investigation workflows: the agent checks the hold reason and routes to the ops team if action is required. - **On Return Completed** Fires when a return is received and processed at the ShipBob warehouse. Used to trigger refund processing, inventory update workflows, and customer communication. ## Frequently Asked Questions ### What can FlowRunner do with ShipBob? FlowRunner agents can run Create Order, Get Order, and Get Orders in ShipBob, plus 17 more actions. ### Does connecting ShipBob to FlowRunner require OAuth? Yes. ShipBob connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can ShipBob trigger a FlowRunner workflow automatically? Yes. ShipBob supports 5 triggers that can start a FlowRunner workflow automatically. **Work at ShipBob?** This integration exposes ShipBob 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/shipbob. Site index: https://flowrunner.ai/llms.txt