Shopify Sidekick can now generate Flow automations from a plain-English prompt, and nearly half of Q1 2026's Flows were built this way per Shopify's Q1 earnings. Here's how to use Shopify Flow AI to create workflows in the current Sidekick interface, and the point where store-ops automation stops being the right tool for customer-lifecycle marketing.
Shopify Flow used to require dragging trigger, condition, and action blocks by hand. Now Sidekick generates Flow automations from a plain-English prompt. Here's how to use Shopify Flow AI to create workflows in the current Sidekick interface, what Flow v4 actually adds, and the point where store-ops automation stops being enough for lifecycle marketing.
What Changed
- Shopify fine-tuned a tool-calling agent (Qwen3-32B) that generates Flow automations from natural language, 2.2x faster and 68% cheaper than the frontier model it replaced, per Shopify Engineering's 2026 post.
- Nearly half of all Shopify Flows generated in Q1 2026 came from Sidekick, not the manual builder, per Shopify's Q1 2026 earnings call.
- You create a Flow with Sidekick by opening Flow, clicking the Sidekick icon, and describing the automation in plain English, per the Shopify changelog.
- Flow's Wait action now supports a maximum duration of 30 days, per the Shopify changelog, enabling delayed follow-ups that used to require an external scheduler.
The practical effect of the Sidekick shift is who can now build a Flow automation, not just how fast. The old visual builder required understanding trigger/condition/action logic well enough to wire it correctly, which kept Flow-building concentrated among ops-savvy store admins. A prompt-based agent that gets the logic right most of the time opens that same automation up to anyone who can describe what they want in a sentence. That's a real access shift, not just a speed one, and it's the actual reason nearly half of Q1 2026's Flows came from Sidekick rather than the manual builder - the bottleneck wasn't the tool, it was who could operate it.
How to Use Shopify Flow AI to Create Workflows: Step-by-Step
- Open Shopify Flow from your admin. Flow is included free on all Shopify plans, so if it's not already installed, add it from the Shopify App Store first.
- Click the Sidekick icon in the Flow editor to open the AI prompt bar. This is the entry point for AI-generated workflows - the manual visual builder is still available in the same view if you want to fall back to it.
- Describe the automation in plain English. Be specific about the trigger event, the condition, and the action. Example: 'When an order over $500 is placed by a first-time customer, tag it VIP-first-order and send me a Slack notification.' Vague prompts produce vague flows.
- Review the generated workflow. Sidekick returns a Flow with the trigger, conditions, and actions filled in. Check that the trigger event matches what you meant, the conditions evaluate in the right order, and the actions target the correct fields (order tags vs. customer tags, notification channels, etc.).
- Adjust anything wrong in the visual editor. Sidekick isn't one-shot correct on every prompt, and the visual editor is still where you clean up branches, add a Wait step (up to 30 days), or slot in a Flow v4 LLM action like Summarize or Categorize.
- Turn the workflow on and test it against a real event before leaving it running unattended. A misfired ops flow at scale is a customer-experience incident, not a small bug.
When Flow Fits, When You Need a Lifecycle Tool
| Question | Shopify Flow fits | Lifecycle marketing tool fits |
|---|---|---|
| Trigger type | Store event (order placed, inventory threshold, tag applied) | Customer behavior over time (signup, browse abandonment, days since last purchase) |
| Action count | One action or a short branch | Multi-touch sequence across days or weeks |
| Channels | Store-internal actions (tags, notifications, fulfillment) | Email, SMS, push, coordinated across channels |
| Branching logic | Multi-branch conditions for ops decisions | A/B-tested branches tied to marketing intent and audience |
| State it needs | The current order or product | Full customer profile, history, and segment membership |
A Quick Test for Which Job You Actually Have
Three questions settle it faster than comparing feature lists:
- Does the trigger fire on a store event (order placed, inventory threshold, tag applied) or a customer-behavior event (signup, browse abandonment, days since last purchase)? Store event = ops, Flow's job. Behavior event = lifecycle marketing, a different tool's job.
- Does the automation end in one action, or does it need to branch and re-engage over days or weeks based on what the customer does next? One action = ops. A multi-touch sequence with branches = lifecycle marketing.
- Does it need to run across channels (email and SMS together, coordinated) or stay inside store-internal actions? Cross-channel = lifecycle marketing, not something Flow's operations scope covers regardless of how capable its AI gets at ops tasks.
Most teams end up running both, Flow for the operational plumbing, a lifecycle tool for the customer-facing journeys, because they're genuinely different jobs rather than the same job at two maturity levels. Knowing how to use Shopify Flow AI to create workflows quickly is the easy half - knowing which of those jobs a given automation belongs to is the harder half, and the one worth getting right.
Frequently asked questions. Answered.
Yes. Shopify fine-tuned a tool-calling agent (Qwen3-32B) that turns natural language into Flow automations inside Sidekick, per [Shopify Engineering's 2026 post](https://shopify.engineering/fine-tuning-agent-shopify-flow). The fine-tuned model is 2.2x faster and 68% cheaper than the frontier model it replaced.
