Automate repetitive store tasks with Shopify Flow, no code needed: the trigger-condition-action model, plan requirements, limits, performance rules and when to move to a custom integration.
Tagging orders, holding risky ones and notifying the team are repetitive store tasks that often turn into one person's daily routine. Shopify Flow lets you automate them without writing code. This article explains how Flow works, which jobs it suits, where its limits are and when you should move to a custom integration.
What Is Shopify Flow?
Shopify's help centre describes Flow as an ecommerce automation platform for automating tasks and processes in your store. Flow watches for an event in the store and, when it happens, runs the steps you defined in order. It is a free app installed from the Shopify App Store.
According to Shopify's documentation, Flow is available on the Basic, Grow, Advanced and Plus plans, and most features work on every plan. There are two exceptions: the "Send HTTP request" action, which sends requests to external services, is available on Grow, Advanced and Plus, and custom tasks from partner apps are available on Plus only. Plan-based API limits also affect Flow's usage limits. In other words, the same workflow can run smoothly in a small store and hit a rate limit on a busy campaign day, so it pays to design for volume from the start.
Anatomy of a Workflow
Every workflow is built from three building blocks:
- Trigger: The event that starts the workflow, for example "Order created", a set date and time, or an event from an external app. Each workflow has exactly one trigger.
- Condition: The criterion that decides whether an action runs. It looks at the trigger event or related order, product and customer data.
- Action: A step that changes the store, modifies workflow data or talks to an external service. "Add order tags", "Hold fulfillment orders", "Send email" and "Send HTTP request" are examples.
In addition, connectors provide ready-made actions for third-party services, such as sending a Slack message or adding a row to Google Sheets. You can start from scratch or adapt a ready-made template. Field names follow the Shopify Admin GraphQL API; you can use the data preview to see what a field returns.
Which Jobs Is It Good For?
Flow is ideal for jobs with a clear rule that run the same way every time. The examples below can be built with the trigger and action types documented in the help centre:
- Tagging and routing orders: The "Order created" trigger, a condition on amount or product, and the "Add order tags" action. The warehouse or customer service filters by that tag.
- Holding orders that need a manual check: When the condition is met, the "Hold fulfillment orders" action runs and an email goes to the team. Packing does not start until the review is done.
- Team notifications: Using the Slack connector to post selected orders to the right channel.
- Record keeping: Using the Google Sheets connector to add order or stock events as rows in a spreadsheet.
- Notifying an outside system: Using "Send HTTP request" to pass an order event to your own system or ERP (Grow and above).
- Scheduled checks: Using a scheduled-time trigger with a "Get data" action to scan a list in bulk.
Be careful on the marketing side: Flow's error guide notes that if a customer has not agreed to marketing emails, the workflow fails with a "Marketing email rejected" error. Consent for commercial messages is also a legal topic of its own; we covered it in our İYS (Turkey's commercial message management system) article.
Limits: Where You Will Get Stuck
Flow offers a cheap and fast start, but it is not unlimited. Shopify's usage limits page lists these figures:
- A store can have at most 1000 workflows (active and inactive combined). If you are over, existing ones keep running but you cannot create, duplicate, import or install new ones.
- A workflow can have at most 40 wait steps, and the total wait time cannot exceed 90 days.
- Each workflow section has a combined run limit of 36 hours; wait steps split a workflow into sections.
- Config field values must be under 50 kB.
- If more than 10 active workflows share the same trigger, Shopify shows a warning on activation, because every trigger event processes all of them.
- The "Get data" action returns at most 100 objects per workflow.
Errors come in three kinds. Transient errors (a step timing out, a 5XX response, GraphQL throttling) are retried until they succeed or the 36 hours run out. Permanent errors (an empty required resource, a deleted resource, a Google Sheets permission error) are not retried and the run is marked "failed". The third group is run-time rate limiting problems. The error message of a failed run appears in the run details; after fixing the workflow you can retry past runs manually.
Five Rules for Performance
Shopify's optimisation guide stresses that a workflow's cost grows with volume: an inefficiency goes unnoticed in a workflow that runs a few times a year, but on a trigger that fires thousands of times a minute it drains your API quota. The practical rules from the guide are:
- Do not fetch lists you do not need. Flow fetches every object in a list. Choose the right path; for example, order line items > product > tags is lighter than order > publication > products > tags.
- Always add a query filter to "Get data". Without a filter the API may return all resources or none. A wrong filter syntax can make the whole query be ignored; test it with the "Log output" action.
- Review workflows on the same trigger. They run in parallel and can compete for API requests. Combine them if they fetch the same data; keep them separate if they fetch a lot of different data.
- Put heavy queries after a wait step. Each wait step splits the workflow into sections, and data is fetched again in each. Place complex data fetching and logic after a condition and wait pair.
- Use the single metafield object. When values are large (HTML, for example), go to the one metafield you need instead of looping over the whole metafields list.
Where Flow Ends: When Do You Need a Custom Integration?
Flow is strong at reacting to events inside Shopify. You reach its edge when the business logic is highly branched and data-heavy (the 100-object limit and timeout risks), when stock or price must flow continuously and event-based from an ERP, or when the other system needs its own error handling, reconciliation and monitoring. The "Send HTTP request" action works as a bridge, but you still have to build the system on the other end. For this decision, see the method selection in our API integration article, our stock and price synchronisation article for multichannel flows and our shipping and e-invoicing integration article for the invoice and shipping chain. In practice the healthiest approach is to keep simple, Shopify-internal jobs in Flow and move only the flows that involve external systems to custom software.
Cost and Benefit: A Hypothetical Example
Hypothetical example
Assume you receive 40 orders a day and that tagging, routing and notifying each one by hand takes an average of 1.5 minutes. That is 40 × 1.5 = 60 minutes a day, or 22 hours over 22 working days. If Flow takes over 80% of this work, 22 × 0.8 = 17.6 hours a month are freed. At an assumed hourly cost of 400 TL, the monthly gain is 17.6 × 400 = 7,040 TL. Because the Flow app is free, the only costs on the other side are your setup and maintenance effort and any plan requirement (for example Grow or above for HTTP requests). The figures only illustrate the logic; recalculate with your own order volume and times.
Checklist Before You Start
- Write the job in one sentence: "When this event happens, under this condition, do this."
- Check whether the trigger provides a Shopify object; if not, you need "Get data".
- If you work on lists, plan the "For each" loop and the query filter.
- Look at how many active workflows share the trigger and try to stay at 10 or fewer.
- Consider that a resource may be deleted after a wait step (a cause of permanent errors).
- Set up an error notification workflow with the "Workflow error occurred" trigger.
- Run it with a real test order and inspect the run details.
- Give workflows clear names and an owner; management gets harder as the count grows.
- For workflows that involve marketing, verify customer consent separately.
Conclusion
Shopify Flow is the fastest way to automate repetitive, clearly ruled store jobs: it is free, code-free and works on most plans. As volume grows, though, the design of filters, lists and wait steps decides performance, and when you need a continuous, verified data flow with outside systems, a custom integration should take over. Start with one small workflow, set up error notification and measure the results.
Sources: Shopify Help Center: Shopify Flow, Shopify Flow reference, Creating workflows, Optimizing your Shopify Flow workflows, Troubleshooting errors in Shopify Flow (usage limits) (2026). The worked example is hypothetical.