Get a free Shopify store audit

Shopify Flow Examples: What You Can Automate

Shopify Flow ships hundreds of workflow templates. Here is how triggers, conditions, and actions work, with real examples by category.

Shopify Flow Examples: What You Can Automate — ASSOSIATIX Journal

Shopify Flow examples span hundreds of pre-built workflows in Shopify's own template library, covering categories like inventory, orders, risk, promotions, and B2B. Every one of them — and anything custom you build yourself — is just a trigger, a condition, and an action chained together.

What a Shopify Flow Workflow Is Actually Made Of

Shopify's own reference breaks every workflow into four components:

  • Triggers — an event in your store, at a scheduled time, or in a third-party app that starts the workflow. A new order being created is a trigger.
  • Conditions — if/then checks against the trigger or related objects, like whether an order total is over $200.
  • Actions — changes the workflow makes: tagging an order, holding a fulfillment, sending an email, or sending an HTTP request to an external service.
  • Connectors — actions provided by Flow that reach third-party services, such as posting a Slack message or adding a row to Google Sheets.

Flow itself is a free app on the Basic, Grow, Advanced, and Plus plans. Two features are gated above that: the Send HTTP Request action needs Grow, Advanced, or Plus, and tasks built by custom partner apps need Plus specifically. Usage limits otherwise follow whatever API limits your plan already has.

Real Examples From Shopify's Own Template Library

The template library groups hundreds of examples into named categories, including B2B, buyer experience, custom data, customer, error monitoring, fulfillment, inventory and merch, loyalty, orders, payment reminder, promotion, risk, and workflows with connector apps. A few worth knowing by name:

  • Inventory and merch — "Get notified when product inventory is low," "Hide and republish products based on inventory level," "Merchandise low stock products and hide when out of stock," and "Get notified when demand increases for out of stock products."
  • Risk — built on the Order risk analyzed trigger, which uses results from Shopify's own Risk Analysis only; results from third-party risk apps aren't used. For stores that capture payment manually, the Capture payment action can be set to only capture when risk is low or medium.
  • Promotion — "Recover abandoned checkout," "Welcome new subscribers with a discount email," and "Upsell customers after their first purchase."
  • Orders — "Email logistics team when orders need to be expedited" and "Tag orders paid with gift card."
  • Error monitoring — "Get notified by email when workflow run errors are detected."

The inventory templates rely on a mechanic worth understanding before you build your own version: checking both the current and the prior inventory quantity, so an alert fires only the first time a threshold is crossed. Shopify's own worked example: a store has 7 T-shirts. A customer orders 2, inventory drops to 5, and a reorder email fires. Later, another customer orders 1 more, inventory drops to 4 — and no email fires, because the threshold was already crossed on the first order. Checking only the current quantity would send a duplicate alert on every order after that point.

Risk workflows have a second path worth knowing: if your store automatically captures payments and fulfills orders manually, Flow can't prevent the payment from being captured on a high-risk order, but it can cancel the order outright using the Cancel order action, and you can add a tag or send the cancellation details to an app like Google Sheets or Trello to keep a record.

A separate category — workflows with connector apps — covers automations built around specific Shopify or third-party apps rather than generic store events. The Shopify Collabs app, for instance, has ready-made Flow templates for automatically approving affiliate applicants and exporting accepted creators to Klaviyo. Shopify Messaging connects to templates like emailing waitlisted customers when a product restocks. These aren't generic triggers you'd piece together yourself — they only exist because that specific app shipped a Flow connector.

Scheduled and Advanced Workflows

Not every automation starts with an event. The Scheduled time trigger starts a workflow at a specific time and date instead, and can recur hourly, daily, weekly, or monthly — Shopify states it can run as frequently as every 10 minutes. Because a scheduled workflow doesn't start from an order or customer event, you need a Get data action to pull in whatever records you want to act on; Shopify is explicit that these actions can only run on lists up to 100 items long.

Shopify's own worked example combines both: a workflow runs daily at 5:00 p.m., uses the Get order data action to retrieve orders that weren't fulfilled within a two-day shipping window, uses a For each action to tag all of those late orders, then uses Count and Sum actions to total how many there are and what they're worth before emailing a summary. That's four separate pieces — a schedule, a data pull, a loop, and an aggregation — doing something no single event-based trigger could do on its own.

If you want to see what a similar scheduled, data-pulling workflow looks like end to end, we've documented a Flow workflow built around the Get Analytics Data action in more detail.

Where Flow Hits Its Limits

Flow's no-code model covers a lot of ground, but it has real edges. The Send HTTP Request action and custom partner-app tasks are plan-gated, as covered above. Get data actions cap out at 100 items per list, which matters the moment your daily summary workflow needs to cover more orders than that. And some logic — multi-step branching against data from outside Shopify, or conditions that need to call another system mid-workflow — simply isn't expressible in Flow's trigger-condition-action model, no matter how many templates you combine.

That's the point where it's worth scoping a custom build on top of or instead of Flow, which is exactly the kind of work covered by our Shopify automation service. We've also written about using an AI toolkit to scope Flow automations before you build them, which is worth a look if you're not yet sure whether a given task fits inside Flow at all.

If you're not sure whether your use case fits inside Flow or needs something custom, talk to our team.

Frequently asked questions

What is Shopify Flow and is it free?

Shopify Flow is Shopify's own ecommerce automation platform: it monitors your store for events and runs a sequence of actions in response. It's a free app, available on the Basic, Grow, Advanced, and Plus plans.

What plans can use Shopify Flow?

All four plans — Basic, Grow, Advanced, and Plus — can install and use Shopify Flow. Two specific features are more restricted: the Send HTTP Request action requires Grow, Advanced, or Plus, and tasks built by custom partner apps require Plus.

What's the difference between a trigger, a condition, and an action?

A trigger is the event that starts a workflow, such as a new order being created. A condition is an if/then check against that event, like whether the order total is over $200. An action is what the workflow actually does once the conditions are met — tagging the order, holding fulfillment, or sending an email, for example.

Can Shopify Flow send data to Slack or Google Sheets?

Yes, through connectors — actions Flow provides specifically to reach third-party services. Shopify names Slack messages and Google Sheets rows as examples of what a connector action can do.

How often can a scheduled Shopify Flow workflow run?

A workflow built on the Scheduled time trigger can recur hourly, daily, weekly, or monthly, and Shopify states it can run as frequently as every 10 minutes.

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.