How do I test a Shopify Flow workflow without changing live store data?
Use passing and failing events to check logic. Flow stops before modifying actions; verify external results separately.
- When this applies
- You are preparing to activate or change a valid Shopify Flow workflow and need to prove its trigger data, branches, variables, and operators without applying modifying actions. [1]
- When this does not apply
- You need proof that a modifying action or an external service completed after a live run; use the last system's own test or result record for that job. [1]
- Why this matters
- A workflow can follow the expected logic in Flow and still fail at the first modifying or external action, because the simulation stops before completing those actions. [1]
- What to do
- Open Apps > Flow > Workflows, select the workflow, choose Edit, select its trigger, and confirm that Test your workflow opens. [1]
- When you’re done
- The passing and failing events follow the expected branches and Preview shows the expected data. Any unsimulated external action also shows the bounded result in the receiving system. [1] [2]
- What this cannot prove
- A passing Flow simulation does not prove that a modifying action or external service completed, and the test run does not appear in Recent runs. [1]
- Sources checked
- August 22, 2026
Steps
- Open Apps > Flow > Workflows, select the workflow, choose Edit, select its trigger, and confirm that Test your workflow opens. [1]
- Choose Generate events, review the two saved events, and keep one event that should pass and one that should fail using the intended store records. [1] [2]
- Select each saved event and confirm that the highlighted path, Preview values, variables, and operators match the expected result. [1]
- When Flow shows Can't simulate this action, verify one bounded case in the receiving service and observe the intended result there before activating more broadly. [1]
Open the official page, then report your progress
The page you opened and the completion or stop step you report stay only in this browser on this device. AI Commerce Ready and Shopify do not check the result or change your store here.
- Official page
- Shopify admin → Apps → Flow → Workflows → Select the workflow → Edit → Select the trigger → Test your workflow
- Before you act
- The workflow editor opens the Test your workflow dialog with saved events and controls to add, record, create, or generate an event.
- When you’re done
- The passing and failing events follow the expected branches and Preview shows the expected data. Any unsimulated external action also shows the bounded result in the receiving system.
- When to stop
- Stop without activating when a workflow step is invalid, the test data does not represent the intended case, or an external action has no safe test path or reversible bounded case. [1]
When you return: Keep this page open. After each Flow test or external-service check, return to this tab and compare the observed result with the finish condition or Stop Point.
Paid help and free options
- When paid help makes sense
- Paid help is worth it only when the workflow calls a system outside Shopify that has to be validated inside that system, which the Flow test run does not do. [1]
Use Flow’s test to check logic without applying modifying actions. It stops at the first action that changes something, so external results need a separate check.
1. Open the test
Open Shopify admin > Apps > Flow > Workflows > the workflow > Edit. Select the trigger, then Test your workflow.
An incomplete or invalid step must be fixed first. Activating the workflow does not fix it.
2. Create two useful events
Choose Generate events. Sidekick uses existing store data to create one intended passing event and one failing event. Review fields and change any that do not represent your case.
3. Inspect paths and data
Run both events. The passing path must reach the expected action; the failing path must stop at the intended condition.
Open Preview for each condition or action. Check values, variables, operators, and AND/OR. A highlighted path using the wrong records is insufficient.
4. Verify unsimulated actions separately
Flow cannot simulate some external actions, including HTTP requests. When it says Can’t simulate this action:
- Finish the trigger, condition, and payload checks.
- Use the receiving service’s test or sandbox path if available.
- Choose one limited live case whose effects you can identify and undo.
- Confirm the result in Shopify and the receiving system before broader activation.
Finish the simulation when both events follow expected logic and Preview shows expected data. Finish the whole task only when unsimulated actions show the intended result in the final system. Without a safe test or reversible case, keep the workflow inactive. Test runs do not appear in Recent runs.