001 — the thesis
Build workflows that trigger on Shopify events, reason with an LLM, write back to the store, and stop for approval before anything risky ships. Every step, every tool call, logged.
002 — anatomy
Every workflow has one trigger and an ordered list of steps. Each step can be an action, a condition, an LLM reasoning call, or a proposal gate.
003 — what people build
trigger: orders/create
An LLM reads the order, scores it, routes anything above a threshold to a review queue. Rules can't read a shipping address like a human can — this does.
trigger: schedule · 24h
Pulls low-stock items, asks an LLM for reorder quantities based on 30-day velocity, drops each recommendation in your Proposals inbox.
trigger: review created
Drafts a tone-matched response, proposes a discount code or refund amount, routes the approval to whoever's on ops rotation.
trigger: schedule · weekly
Finds products with 45+ days of stock, reasons about competing SKUs, proposes a code + a Klaviyo email segment to target.
trigger: orders/create
Simple, but one line of YAML in Flow can't do the downstream: personalized thank-you email and a one-time discount generated per customer.
trigger: inventory_levels/update
When a SKU crosses its low threshold, the workflow emails purchasing with an LLM-drafted PO. The PO only sends after approval.
004 — versus everything else
Shopify Flow
Shopify Sidekick
Zapier/Make with GPT blocks
005 — trust
Proposals inbox
Mark any step as 'requires approval'. The workflow stops, an approval lands in your inbox with the resolved action config, and only then does it run. Reject and the run continues with a skipped step.
Versioned workflows
Every save bumps the version; runs are pinned to the version that executed them. You can see exactly what rule produced a change a month ago.
Tamper-evident audit log
Every write an agent makes lands in audit_log with the actor, tool, args, and result. Your ops team gets a real paper trail.
006 — next