Get a free Shopify store audit

Shopify Flow vs Custom Automation: Which to Build

Shopify Flow's documented limits on data, API calls, and wait time, and the exact signals that mean it's time to build custom automation instead.

Shopify Flow vs Custom Automation: Which to Build — ASSOSIATIX Journal

Shopify Flow vs custom automation comes down to this: Flow is Shopify's free built-in automation tool, and it's enough for most store-native, rule-based workflows — but it has documented ceilings on data volume, external calls, and wait time that push a workflow toward custom automation once you hit them. Here's exactly where that line sits.

How Shopify Flow actually works

Flow workflows are built from three step types. A trigger is the event that starts the workflow — something like an order being created. Conditions evaluate data to decide whether the workflow should continue. Actions are what the workflow actually does, like tagging a customer or sending a notification.

One constraint that trips people up early: each workflow can have only one trigger step. If you want the same logic to run off two different events, you need two workflows, not one workflow with two triggers.

The Scheduled time trigger is a special case worth knowing about. It can run hourly, daily, weekly, or monthly, but unlike event-based triggers, it doesn't hand the workflow any data by default — you have to pair it with a Get data action to actually fetch something for the rest of the workflow to use.

What's gated by plan

Shopify Flow itself is free and available on the Basic, Grow, Advanced, and Plus plans, so installing it costs nothing regardless of plan. But two capabilities inside Flow are plan-gated, and this is usually the first place a Basic-plan merchant discovers Flow's ceiling:

  • The Send HTTP Request action — the action that lets a workflow talk to a server or URL outside Shopify — only works on Grow, Advanced, and Plus. Basic-plan stores don't get it.
  • Tasks built by custom partner apps only run on the Plus plan.

If reaching an external system turns out to be the thing your workflow needs and your plan doesn't support it, that's exactly the kind of gap our Shopify automation service is built to close — whether that means a custom app, an upgrade path, or a different integration approach entirely.

The documented limits that actually push a workflow out of Flow

Beyond plan gating, Flow's own reference docs spell out hard numeric limits on several of its most-used actions. These are the ones that actually force a redesign, not just inconvenience:

Run code. This action runs ECMA2020 JavaScript, but with real restrictions: no NodeJS or CommonJS APIs, no importing modules, and no HTTP calls (`fetch`) — so it can't reach out to anything outside the workflow's own data. Random and clock-based functions aren't allowed either. On top of that, the input data query and the output schema are each capped at 5,000 characters, the output payload plus any `console.log` output together can't exceed 50KB, the code itself can't exceed 50,000 characters, total execution is capped at 5 seconds, and memory usage is capped at 10MB.

Get data actions. These are designed to return a maximum of 100 objects per call. Go over that and Shopify's own documentation says you'll start seeing performance issues. Worse, a Get data action with no query filter at all can mean the underlying API call returns either all matching resources or none — not a safe default to leave unset.

Wait. The Wait action can delay a workflow for a maximum of 90 days. Set a longer delay and the workflow simply can't be activated — Shopify's own fix for anything past that window is to use a scheduled workflow with a Get data action instead.

Send HTTP request. After sending a request, Flow waits a maximum of 30 seconds for a response before closing the connection and retrying later. On a 4XX client error or a 5XX/429 server error, you choose how Flow responds: retry for up to 24 hours until it gets a different response code or times out, fail the workflow run outright, or ignore the error and keep going.

Shopify Flow vs custom automation: when to build custom instead

Lay those limits next to an actual automation task and the decision points get specific rather than vague:

  • You need to process more than 100 records in a single pass. Get data's 100-object cap means a workflow built around fetching more than that per call is fighting the tool, not using it as intended.
  • You need more than one external API call chained together, with real error handling. Flow's Send HTTP Request action handles one request-response cycle with built-in retry/fail/ignore behavior; coordinating several calls with branching logic across systems is a different kind of problem.
  • You need durable state, retries, or reconciliation across systems over time. Flow's Wait action tops out at 90 days and doesn't give you a place to track in-flight state the way a dedicated backend would.
  • You need a human approval step in the middle of the process. Flow's actions run automatically once triggered; there's no built-in pause for a person to review and approve before the workflow continues.
  • You need a reaction faster than Flow's own scheduling floor, or logic Run code's 5-second, 10MB sandbox can't fit. Both are hard ceilings documented by Shopify, not soft guidelines.

Recognizing one of those signals in your own workflow is the actual decision point — at that stage, custom shopify automation built outside Flow is the next step, not because custom code is inherently better, but because Flow's documented constraints no longer fit the job.

A hybrid pattern: Flow for the trigger, custom code for the heavy lifting

Shopify workflow automation doesn't have to be all-or-nothing for an entire store. Flow's own Send HTTP Request action is explicitly designed to hand off to an external service: the service does the complex work and returns a response, which a Run code action can then parse with `JSON.parse` for use in later steps. Shopify's own documentation walks through this exact pattern — a Product status updated trigger firing a Send HTTP Request to an external endpoint, with a Run code step after it to extract fields like `productTitle` and `productStatus` from the response body.

That split keeps the trigger and conditions visible and editable by store staff in the Flow UI, while a custom backend owns the part that's actually complex. For a sense of what Flow alone handles well before you need that handoff, see our Shopify Flow examples. And when the custom side of that split involves AI rather than plain logic, the operational considerations shift again — we cover that in AI workflow automation.

If you're not sure which side of that split your workflow falls on, talk to our team.

Frequently asked questions

Is Shopify Flow free?

Yes. Flow itself is a free app available on the Basic, Grow, Advanced, and Plus plans. What's gated by plan isn't Flow access — it's specific actions: the Send HTTP Request action requires Grow, Advanced, or Plus (not Basic), and tasks built by custom partner apps require Plus.

What's the real difference between Shopify Flow and a custom Shopify app?

Flow is a drag-and-drop trigger/condition/action builder with documented limits on data volume (100 objects per Get data call), execution (Run code's 5-second, 10MB sandbox), and external calls (one request-response cycle via Send HTTP Request, with a 30-second wait and configurable retry behavior). A custom app has none of those built-in ceilings, but you're building and maintaining the logic, state, and error handling yourself instead of configuring it in Flow's editor.

Can Shopify Flow call external APIs, and on which plans?

Yes, through the Send HTTP Request action, but only on the Grow, Advanced, and Plus plans — it's not available on Basic. Once a request is sent, Flow waits up to 30 seconds for a response and lets you configure retry, fail, or ignore behavior for 4XX, 5XX, and 429 errors.

How much data can one Flow workflow process at a time?

Get data actions are designed to return a maximum of 100 objects per call, and Shopify's documentation says exceeding that can cause performance issues. Run code actions have their own separate limits: a 5,000-character input query, a 5,000-character output schema, a combined 50KB cap on output payload plus console.log, and a 5-second execution limit.

When should I stop using Shopify Flow and build custom automation instead?

When your workflow needs to process more than 100 records per run, chain multiple external API calls with real error handling, maintain state or reconciliation over time, pause for human approval, or run logic that doesn't fit Run code's execution and memory sandbox. Any one of those is a documented Flow limit, not a matter of preference.

Sources

Tell us what you're building.

Share a few details and we'll reply within 1–2 business days with questions, a scope and a quote.