Shopify Flows vs. Custom Automation: What Makes Sense When

Ever since Shopify Flow became available on smaller plans, I hear this a lot: "do we even need external tools any more?"

Short answer: it depends. Here is the long answer.

What Shopify Flow can do

Shopify Flow is Shopify's native automation. You build workflows with:

• Trigger: what starts the workflow?
• Condition: which conditions have to be met?
• Action: what should happen?

Examples:

• Order over 500€ → add tag "VIP"
• Inventory under 10 → email to you
• Customer buys for the 3rd time → loyalty programme tag automatically

What Shopify Flow can NOT do

This is where it gets interesting:

1. Connect external systems

Flow only works with Shopify data and a few partner apps. Your fulfiller, your CRM, your bookkeeping tool? Not directly.

2. Complex logic

Nested conditions, loops, transforming data? Hard to impossible.

3. HTTP requests

You cannot call arbitrary APIs. You are limited to what Shopify offers. What APIs even are and why that matters is explained in API basics for e-commerce founders.

4. Aggregate data

Summarise and analyse "all orders from the last week"? Not possible.

When Shopify Flow is enough

✓ Yes, use Flow when:

• Everything stays inside Shopify
• Simple if-then logic
• It is about tags, notes, internal workflows
• You want to ship something fast

In practice:

• Automatic customer segmentation
• Internal alerts on certain events
• Setting simple order attributes

When you need external tools

✓ Use n8n/Make when:

• You have to connect external systems
• The logic gets complex
• You combine data from several sources
• You need full control

In practice:

• Shopify → fulfiller → tracking → customer
• Order data → ERP/bookkeeping
• Multi-channel synchronisation
• AI-powered processing

An example from practice: our WISMO requests ("where is my order?") make up around 40 percent of all support tickets. The automation for that needs Shopify data, tracking data from the carrier and the helpdesk. Three systems that Flow cannot connect. In n8n it is one workflow. The details are in Automating WISMO requests.

Our hybrid approach

At our own brands we use both:

Shopify Flow for:

• Customer tags (VIP, first-time buyer, etc.)
• Internal alerts ("high-value order!")
• Simple product rules

n8n for:

• Fulfillment integration
• Customer service automation
• Reporting and analytics
• Anything that needs external APIs

The best of both worlds. That is how we run 3 brands with 2 people on the operational side: Flow handles the small things in the store, n8n handles everything in between.

Decision tree

Ask yourself:

1. Does everything stay in Shopify?

• Yes → Flow is probably enough
• No → external tool

2. How complex is the logic?

• Simple (if X then Y) → Flow
• Complex (loops, conditions, transformations) → external tool

3. Do you need HTTP requests?

• Yes → external tool
• No → Flow can work

4. How critical is the process?

• Nice to have → Flow (faster setup)
• Business critical → external tool (more control)

Cost comparison

Whether you should self-host n8n or use the cloud version is a decision of its own. You will find the trade-off in n8n self-hosting vs. cloud.

One concrete first step

Before you set up any tool: write down your three most annoying recurring tasks. For each one, check whether all the data involved sits in Shopify.

• All data in Shopify? Build it in Flow today. Takes 15 minutes.
• External systems involved? Put it on the n8n list.

That way you avoid the most common mistake: investing weeks in a tool before it is clear which problems it should solve.

My recommendation

For most e-commerce brands:

1. Start with Shopify Flow for simple internal automations

2. Add n8n/Make as soon as you need external integrations

3. Migrate critical flows to n8n when reliability becomes important

You do not have to choose. The tools complement each other.

Specific questions about your setup? benedikt@flowhouse.ai