Playbook · Shopify Flow trigger not firing on order/create/inventory
Shopify Flow workflow trigger not firing on order/create/inventory events.
Written for a Shopify owner or ops lead whose Shopify Flow workflow never starts a run when an Order created, Order paid, or Inventory quantity changed event happens — Active workflow, empty run history, proven admin event. DIY-first: prove the event timestamp vs Flow run history; fix wrong trigger type, Draft/paused, Flow app/plan gate, and event-before-Active timing. Distinct from Flow inventory not updating, webhooks not delivering, and bulk operations stuck. No earnings claims, no invented case studies.
Nico at Latch AI Ops · Sep 10, 2026 · ~11 minute read
Buy the 72-hour install — $997Flow not triggering (broader)Flow inventory actionsMerchant FAQ
01
Flow trigger silence on order/create/inventory — not inventory actions, app webhooks, or bulk ops.
Several automation bugs look like “Flow never ran.” They do not share one engine. This page is only when Apps → Flow has a workflow whose Order created, Order paid, or Inventory quantity changed trigger never starts a run after you prove the admin event — empty run history, wrong trigger type, Draft/paused, Flow app/plan gate, event created before the workflow was Active. When the trigger fires but inventory conditions/actions do not change Available / inventory_levels, open Flow inventory not updating. When a custom app webhook HTTPS endpoint fails HMAC / retries, open webhooks not delivering. When GraphQL bulkOperationRunQuery never completes, open bulk operations stuck. Broader condition-not-met / permission silence is Flow not triggering. This page is only: Shopify Flow workflow trigger not firing on order/create/inventory events.
Six ordinary reasons the trigger stays silent: Order created selected when the shop only emits Order paid (or the reverse); Inventory quantity changed watching the wrong location/variant; workflow Draft or paused while you test; Shopify Flow uninstalled, scopes revoked, or plan no longer includes Flow; the order/inventory change happened before the workflow was turned Active (no backfill); or you are reading app webhook Delivery logs / bulk operation status instead of Flow run history. Walk them in that order. You already pay for Shopify. You do not need another automation SaaS to prove Order created equals a Flow run row.
02
Prove the admin order/inventory event and that Flow run history stayed empty.
Open Apps → Flow → the workflow and confirm status is Active. Note the exact trigger name (Order created, Order paid, Inventory quantity changed). Create a new paid test order or adjust inventory quantity at a tracked location — screenshot the Admin order / inventory timestamp. Immediately open Run history for the same window.
If run history is empty after a proven event, stay on this page. If runs appear with “condition not met,” leave for Flow not triggering condition debugging. If runs reach inventory actions but Available stock does not change, open Flow inventory not updating. If only Settings → Notifications → Webhooks (or an app’s webhook Delivery log) failed, open webhooks not delivering. If a bulkOperationRunQuery is stuck, open bulk operations stuck.
03
Fix wrong trigger type, Draft/paused, Flow app/plan gate, and event-before-Active timing.
Match the trigger to the event you proved: Order created vs Order paid (manual / pending payment orders often never hit “paid”), or Inventory quantity changed for the location and variant you adjusted. Turn the workflow Active — Draft and paused workflows never start runs. After editing the trigger, save and confirm Active again.
Reinstall or reconnect Shopify Flow if the app is missing, scopes were revoked, or staff cannot open Flow. Confirm the shop plan still includes Shopify Flow. Retest with a new order or inventory change created after Active — Flow does not backfill historical events. Do not treat a green custom-app webhook Delivery or a finished bulk operation as proof the Flow trigger fired.
04
Checklist and how to prove Order created / Inventory quantity changed starts a run.
Checklist: (1) screenshot workflow Active + exact trigger name, (2) prove a new Order created / Order paid / Inventory quantity changed in Admin with timestamp, (3) open Flow run history for that window, (4) fix wrong trigger type if empty, (5) un-pause / republish Draft, (6) reconnect Flow app / plan gate, (7) retest only with events after Active, (8) if runs appear but inventory stock / webhooks / bulk ops remain wrong, switch playbooks.
Prove it: after a new paid test order (or inventory adjust), Flow run history must show a started run for that workflow within minutes. If the run starts and conditions pass but Available stock is unchanged, open Flow inventory not updating. If you only care about app webhook HTTPS delivery, open webhooks not delivering.
05
You tested Flow inventory actions, app webhooks, or GraphQL bulk operations instead.
Flow inventory quantity conditions/actions not changing stock is Flow inventory not updating. Custom app webhook HTTPS / HMAC / retry failures are webhooks not delivering. GraphQL bulkOperationRunQuery never completing is bulk operations stuck. Broader condition-not-met / permission silence is Flow not triggering. None of those fix Order created / Inventory quantity changed trigger silence with empty run history.
Finish prove admin event + empty run history → match trigger / Active / Flow app → new-event proof first. Only then open the related playbook that matches the remaining symptom.
06
When to stay DIY vs pay $997.
Stay DIY if you can spend one afternoon on the list above: prove Order created / Inventory quantity changed vs empty Flow run history, match trigger type, turn Active, reconnect Flow, retest with a new event, and stop treating inventory actions / app webhooks / bulk ops as the same bug. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: Flow inventory, Webhooks, Bulk ops, Flow not triggering.
Pay $997 when the gap is wiring — lead capture, ops alerts, and a checkout-ready workflow on the stack you already pay for, including Flow order/create/inventory trigger silence exceptions landing in a channel you already check. Clock starts when collaborator access is in. 72 hours. One live store. Latch does not sell an earnings or ops-efficiency number. No invented case studies.