FlowRunner
Pricing
Theme

Shopify

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.

6 triggers 25 actions available
Shopify fires On New Order when a customer checks out
Agent reads the line items, shipping address, and order total
Agent validates inventory availability per SKU across store locations
Agent checks the order against fraud signals and high-value thresholds
Agent tags the order and hands it to the fulfillment flow
Operations channel gets the order summary and the routing decision
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](/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

17 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

3
  • Get List of Products / Get Product Browse the catalog or pull one product's full details including variants, images, and options. Used to look up a SKU before acting on it or to feed catalog data downstream.
  • Get List of Collections / Get Collection Read the store's collections and a single collection's product list. Used in merchandising and reporting flows.
  • Add Products to Collection / Remove Products from Collection Curate collection membership. Used to run seasonal merchandising or promote and retire products on a schedule.

Customers

2
  • Get List of Customers / Get Customer Read customers in bulk or pull one customer with addresses and order history. Used to look up a buyer or mirror records into a CRM.
  • Create Customer / Update Customer / Delete Customer Full customer lifecycle. Used to keep the storefront in step with the CRM and correct records before fulfillment.

Inventory

5
  • Get List of Locations / Get Location Read the store's locations and one location's inventory levels. Used to route stock decisions to the right warehouse.
  • 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

1
  • Add Tags / Remove Tags Add or remove tags on a resource such as an order, customer, or product. Used to drive routing, segmentation, and downstream filtering.

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.

Start building with Shopify

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