Start with a decision you can explain
For a first Shopify automation, choose a repetitive task with a clear condition and a named owner. An internal notification or review tag is easier to inspect than a workflow that changes a customer's payment or promise. Describe the expected result before choosing a tool.
This guide combines official Shopify documentation checked on September 6, 2026, with our proposed operating framework. The pilot scenarios are examples, not results from a store installation. If your immediate problem is answering shoppers, start with our AI customer support pilot instead.
Where Flow and Sidekick fit
Shopify Flow runs workflows built from triggers, conditions and actions. The app is free on Basic, Grow, Advanced and Plus. External HTTP requests require Grow or above; usage limits depend on the plan. Shopify Flow overview
Sidekick is the AI assistant inside Shopify admin. It accepts everyday-language requests and presents changes for review. That makes it useful for turning an operational brief into a draft, while the store operator remains responsible for what should happen. Sidekick overview
| Approach | Useful starting job | What to review |
|---|---|---|
| Flow | Apply a rule after a store event | Trigger, conditions and action destination |
| Sidekick-assisted Flow | Draft a workflow from a written brief | Missing exceptions before activation |
| External service through HTTP | Connect an approved outside system | Data sent, credentials, retries and duplicate handling |
| Human review | Resolve an exception or approve a commitment | Owner, evidence and next action |
The suggested jobs and review points are editorial recommendations. AI can help construct a rule-based workflow; that does not mean each later run makes an AI judgment.
Write a one-page operating brief
Record the event, qualifying condition, excluded cases, action, recipient and pause owner. For example: when an order needs special packing, notify the packing lead with the order reference; do not change payment, fulfillment status or customer messages.
State how staff will identify completion. If a tag means “review needed,” assign a separate method for recording “review completed.” Otherwise the same label can be mistaken for both a request and a result. Check other automations that already use the proposed tag.
Choose a starting scope small enough for the owner to inspect every result. There is no universal minimum order count or guaranteed time saving. The useful baseline is your own handling time and correction rate for the same task.
Generate a draft, then inspect the actual steps
Flow workflow generation through Sidekick requires a desktop device. Generated workflows are inactive until manually enabled, and Shopify recommends reviewing and testing the draft for missing business logic. Creating workflows
An example request is: “Draft a workflow that adds a review tag and notifies our operations lead when an order matches our special-packing condition. Leave it inactive. Do not cancel, refund, fulfill or email customers.” Replace the condition and recipient with your approved rules.
Read the resulting workflow independently of the chat summary. Check what the condition compares, what happens on the false branch and which record the action changes. A familiar action name is not enough if it operates on the wrong customer or order.
Three practical pilot choices
Packing or stock notifications: begin with an internal recipient who can confirm the notice arrived and was useful. Flow's Send internal email action uses fixed recipient addresses; it cannot personalize the destination using a variable. Do not treat it as a general customer-email action. Internal email action
Risk review routing: if a workflow depends on order risk, choose the event that provides that result. Shopify documents an Order risk analyzed trigger. Our suggested initial action is to route the case for review, leaving cancellation and payment decisions with the designated operator. Order risk analyzed
External task creation: only add an outside system after the internal pilot works. HTTP requests can time out and retry; the receiving system should recognize duplicate requests. Use Flow secrets for credentials, and agree which fields the recipient actually needs. HTTP action and secrets
Test both the rule and the delivery
Flow tests preview logic without performing live changes, and external HTTP actions cannot be fully simulated there. A passing preview therefore does not prove that an external task or email was delivered. Testing workflows
Prepare cases where the condition is true, false and exactly at its boundary. Include a missing optional field and a repeated event. Write the expected outcome first, then compare it with the preview. For a second stage, run a narrowly scoped live check with an internal recipient and confirm the actual result.
Approval must be an operational boundary, not a sentence in a prompt. If staff approval is required, keep the consequential action out of the first workflow and let the operator complete it through the existing process. Expand only when the approval mechanism is defined and tested.
Measure work completed, then expand
Track eligible events, correct actions, missed cases, duplicates and staff correction time. Flow provides run logs, but completed-run history is retained for 14 days. Review on a schedule that fits that limit and keep your own decision notes. Monitoring workflow runs
Compare total effort, including maintenance, with the manual baseline. Pause if notifications are ignored or corrections erase the benefit. Expand one condition or action at a time so the owner can explain any change in outcomes.
Frequently asked questions
Does Basic include Flow?
Yes. The Flow app is available on Basic, but the HTTP action discussed above requires Grow, Advanced or Plus. Check connector and plan requirements for the exact workflow.
Does Sidekick automatically activate the generated workflow?
No. Shopify documents generated Flow workflows as inactive by default. Review and testing should happen before manual activation.
Should we add an AI chatbot at the same time?
Only if shopper conversations are part of the defined problem. Separate the operational pilot from the conversation pilot so you can measure each. Our Shopify AI chatbot guide explains what to compare.
What if product copy is the first bottleneck?
Start with the Shopify Magic product description workflow. That guide covers approved product facts, drafting, and editorial review.
Related articles
Best AI Customer Support Tools for Shopify: 4 Workflows Compared
Compare Zipchat, Gorgias, Tidio Lyro and Shopify Inbox by operating model, handoff and pilot requirements. A source-based shortlist without invented performance rankings.
Read articleHow to Use AI for Shopify Customer Support: A Practical Pilot
Plan a Shopify AI support pilot with clear knowledge sources, escalation ownership, test cases and outcome measurement. Includes practical launch and expansion decisions.
Read article
AI Chatbots for Shopify: 4 Candidates and a Buyer Scorecard
Compare Zipchat, Gorgias, Tidio and Shopify Inbox by operating model. Build a pilot scorecard for answer quality, human handover, deployment effort and total cost.
Read article