--- title: "Shopify Integration" description: "Manage Shopify orders, products, collections, customers, multi-location inventory, and Shopify Payments from automated flows. Agents retrieve and refund orders, curate collections, sync stock across locations, and react in real time to new orders, customers, products, and disputes." url: https://flowrunner.ai/integrations/shopify date_modified: 2026-08-07T17:20:23-07:00 --- # Shopify [E-commerce](https://flowrunner.ai/integrations/category/e-commerce) Manage Shopify orders, products, collections, customers, multi-location inventory, and Shopify Payments from automated flows. Agents retrieve and refund orders, curate collections, sync stock across locations, and react in real time to new orders, customers, products, and disputes. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 6 triggers · 25 actions · OAuth · available [Shopify website](https://shopify.com/) · [Platform Documentation](https://shopify.dev/docs/api/admin-rest) · Capability data verified 2026-07-04 1. Shopify fires On New Order when a customer checks out 2. Agent reads the line items, shipping address, and order total 3. Agent validates inventory availability per SKU across store locations 4. Agent checks the order against fraud signals and high-value thresholds 5. Agent tags the order and hands it to the fulfillment flow 6. Operations channel gets the order summary and the routing decision 7. Orders that trip a fraud signal or the high-value threshold get routed to ops for a hold-or-release call ## What This Integration Enables The Shopify integration gives agents read and write access across orders (retrieve, filter, and refund), products and collections (browse the catalog and curate collection membership), customers (create, update, and delete), multi-location inventory (read levels, adjust by a delta, or set absolute quantities), and Shopify Payments (shop balance, payouts, and disputes). Add and remove tags on any resource to drive downstream routing. Six triggers fire on new orders, order updates, new and updated customers, new products, and new disputes. The connector covers the storefront surface an operations flow needs; the surrounding flow decides what runs unattended and what stops for a person. ### Without FlowRunner **Manual order triage**: New orders wait in the admin queue until someone opens the dashboard and routes each one **Refunds without a paper trail**: Refund decisions get made in DMs, then keyed into Shopify with no consistent record of who approved what **Inventory drift across locations**: Stock counts fall out of sync between the storefront and the warehouse feed, and oversells surface at fulfillment ### With FlowRunner **Routing on checkout**: Orders are validated, tagged, and routed the moment they are placed **Refunds with approval on record**: Every refund is quoted with full context and issued only after a named approver signs off **Inventory reconciled continuously**: Stock levels sync from the supplier feed into each location as counts change ## Use Case Scenarios ### Order Triage and Fulfillment Handoff A customer checks out and Shopify fires On New Order. The agent reads the line items, checks inventory availability per SKU across locations, and scores the order against fraud signals and a high-value threshold. For a clean order it tags the order, hands it to the fulfillment flow, and emails the customer a confirmation. For a flagged order it stops, posts the case to the operations channel with the order context, and waits for a hold-or-release decision before anything ships. ### Inventory Sync From a Supplier Feed A supplier restock feed lands in a spreadsheet on a schedule. The agent reads each row, matches it to the Shopify SKU, and calls Set Inventory Quantities for the right location so the storefront reflects what is actually on the shelf. When a count would drop a variant below its reorder threshold, the agent posts a low-stock note to the operations channel so buying sees the dip when it happens instead of at the next stockout. ### Dispute Response Before the Deadline Shopify fires On New Dispute when a cardholder challenges a charge. The agent pulls the order, the customer, and the payout context, then posts a summary to the finance channel with the dispute amount, reason, and evidence deadline. The agent assembles the evidence a human would otherwise gather by hand. The person reviewing decides whether to submit or accept, and the agent keeps the record of what was sent and when. ## Human-in-Loop Highlight A refund above a configurable amount is a moment that needs a person, so the agent prepares everything and stops short of moving the money. When a return or dispute flow reaches a refund decision, the agent gathers the order, the amount, the restock intent, and the reason, then posts to the operations channel: "Refund requested for order \[number\], customer \[name\], amount $\[total\], restock \[yes/no\]. Reason: \[reason\]. Approve to issue?" The agent has done the math and the documentation. The named approver owns the call, and only after they approve does the agent call Create Refund. This is [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop): the agent pauses on its own, assembles the context and the choices, routes to the approver through the channel they already use, and resumes the instant they respond. 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 25 actions ### Orders 3 - **Get List of Orders** Retrieves a list of orders with optional filtering and pagination. Used to pull recent sales, reconcile against accounting, or find the orders a follow-up flow acts on. - **Get Order** Retrieves a single order by its ID with full details including line items, customer, and addresses. Used when a flow needs the complete context of one order. - **Create Refund** Creates a refund for an order. This is the money-movement step a human-in-loop approval gate sits in front of, so a person owns the issue-or-deny call. ### Products and Collections 6 - **Get List of Products** Retrieves a list of products from your Shopify store with optional filtering and pagination. - **Get Product** Retrieves a single product by its ID with full details including variants, images, and options. - **Get List of Collections** Retrieves a list of collections from your Shopify store. - **Get Collection** Retrieves a single collection by its ID with product list. - **Add Products to Collection** Adds products to a collection. - **Remove Products from Collection** Removes products from a collection. ### Customers 5 - **Get List of Customers** Retrieves a list of customers from your Shopify store. - **Get Customer** Retrieves a single customer by their ID with full details including addresses and order history. - **Create Customer** Creates a new customer in your Shopify store. - **Update Customer** Updates an existing customer in your Shopify store. - **Delete Customer** Deletes a customer from your Shopify store. ### Inventory 6 - **Get List of Locations** Retrieves a list of store locations. - **Get Location** Retrieves a single location by its ID with inventory levels. - **Get List of Inventory Levels** Retrieves inventory levels for a specific location. Used to check availability before promising fulfillment. - **Adjust Inventory Levels** Adjusts inventory for an item at a location by a delta. Used in return, shrinkage, and partial-receive flows. - **Set Inventory Quantities** Sets the absolute inventory quantity for an item at a location. Used to sync counts from a WMS or supplier feed. - **Update Inventory Item** Updates an inventory item's properties. Used when SKU-level attributes change upstream. ### Payments 3 - **Get Shop Balance** Retrieves the shop's Shopify Payments account balance. Used in finance reporting and reconciliation flows. - **Get List of Payouts** Retrieves payouts from the Shopify Payments account. Used to reconcile deposits against orders. - **Get List of Disputes** Retrieves payment disputes from Shopify Payments. Used to start a dispute-response flow before the evidence deadline. ### Tags 2 - **Add Tags** Adds tags to a resource (order, customer, product, etc.). - **Remove Tags** Removes tags from a resource (order, customer, product, etc.). ## Triggers 6 triggers ### Event Triggers 6 - **On New Order** Fires when a new order is placed. Initiates fulfillment routing, fraud review, and customer-confirmation flows. - **On Order Updated** Fires when an existing order changes. Used to keep downstream systems in step with the order's lifecycle. - **On New Customer** Fires when a new customer record is created. Used to mirror the customer into the CRM and start a welcome flow. - **On Customer Updated** Fires when a customer record changes. Used to keep CRM and marketing records consistent with the storefront. - **On New Product** Fires when a new product is added to the catalog. Used to propagate SKUs into PIM, marketing, or merchandising systems. - **On New Dispute** Fires when a new payment dispute is opened in Shopify Payments. Used to start an evidence-gathering flow and alert finance before the deadline. ## Frequently Asked Questions ### What can FlowRunner do with Shopify? FlowRunner agents can run Get List of Orders, Get Order, and Get List of Products in Shopify, plus 22 more actions. ### Does connecting Shopify to FlowRunner require OAuth? Yes. Shopify connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Shopify trigger a FlowRunner workflow automatically? Yes. Shopify supports 6 triggers that can start a FlowRunner workflow automatically. **Work at Shopify?** This integration exposes Shopify 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/shopify. Site index: https://flowrunner.ai/llms.txt