Shopify handles the store, but a lot of the work around it still happens by hand: forwarding orders, checking stock, updating the CRM, chasing reviews, pulling reports. Combining Shopify n8n workflows lets you automate those jobs without building a full application. n8n is a workflow automation tool with a visual editor, a Shopify node, webhook triggers and the option to run custom code where needed. Below are practical workflows, plus the hosting and technical points worth understanding first.
Why n8n fits Shopify stores
Shopify Flow already covers many automations inside Shopify, and it is a good place to start for simple rules that stay within the store. n8n becomes useful when workflows reach outside Shopify: into your CRM, accounting tool, warehouse, spreadsheet, messaging app or internal database.
- It connects to many services and any tool with an API.
- It handles branching logic, loops and data transformation visually.
- It can be self-hosted, which keeps customer data on infrastructure you control.
- You can drop into JavaScript for the parts that need custom logic.
If you are still comparing tools, our breakdown of n8n vs Make vs Zapier covers the differences in pricing model, flexibility and hosting.
Seven practical Shopify n8n workflows
1. Order routing
When a new order arrives, check the shipping address, product types and stock location, then send it to the right warehouse, supplier or fulfilment partner by API or email. Flag orders that need manual review, such as high-value orders or mismatched addresses.
2. Low-stock alerts
On a schedule, read inventory levels, compare them against reorder thresholds you keep in a sheet or database, and post an alert to your team chat with the product, current stock and suggested reorder quantity.
3. Customer tagging into a CRM
When a customer places an order, create or update their record in the CRM, add tags based on what they bought or how much they spent, and update their lifecycle stage. Marketing can then segment without exporting spreadsheets.
4. Fulfilment updates
When a warehouse marks an order as shipped, update the order in Shopify with the tracking number so the customer is notified, and log any delays in a shared tracker.
5. Review requests
A set number of days after delivery, send a review request by email or message, skip customers who have opened a support ticket, and record who responded.
6. Daily and weekly reporting
Pull orders, refunds and top products every morning, calculate totals, and post a short summary to your team chat or write it to a dashboard data source.
7. Support triage
When a customer emails about an order, look up the order by email address and attach order status and history to the support ticket automatically, so agents see context immediately.
Self-hosted vs cloud n8n
| Factor | n8n Cloud | Self-hosted n8n |
|---|---|---|
| Setup | Sign up and start | Server, database, updates needed |
| Maintenance | Handled by n8n | Your team or partner |
| Data location | n8n’s infrastructure | Your own servers |
| Flexibility | Standard features | Custom nodes and full control |
| Best for | Teams without ops capacity | Teams wanting control or data residency |
Self-hosting is a good choice when data control matters or workflow volume is high, but it brings real responsibilities: backups, security updates, monitoring and secure credential storage. Our guide to self-hosting n8n safely walks through what that involves.
Webhooks and rate limits, explained simply
Webhooks
A webhook is Shopify calling your n8n workflow when something happens, such as an order being created or a product being updated. It is faster and more efficient than asking Shopify every few minutes whether anything changed. Two practical rules apply: respond quickly so Shopify does not treat the delivery as failed, and design workflows so that processing the same event twice causes no harm, because duplicate deliveries can happen.
Rate limits
Shopify limits how many API requests an app can make in a given period. A workflow that loops through thousands of products and updates each one can hit that limit and start failing. The fixes are simple: batch requests, add short waits between calls, use bulk operations for large jobs, and retry with a delay when a limit response comes back.
Choosing your first workflow
It is tempting to automate everything at once. A better approach is to pick one workflow, run it for a while, and learn from it. Good first candidates share a few traits:
- The task happens many times a week, so the time saved is visible.
- The rules are clear enough to write down in a few sentences.
- A mistake is easy to spot and cheap to fix.
- One person owns the process and can judge whether the automation works.
Low-stock alerts and daily reports often fit this description well, because they read data without changing anything in Shopify. Once the team trusts those, move on to workflows that write data, such as CRM tagging or fulfilment updates. Order routing usually comes later, since a wrong route affects customers directly and needs careful testing with real order variations.
Before building, write a one-page description of each workflow: the trigger, the steps, the systems touched, what counts as an error, and who is notified. That page becomes the specification for the build and the reference when something needs to change months later.
Making workflows reliable
A store depends on these workflows, so treat them like software:
- Give every workflow an error path that notifies a named person.
- Log key steps so you can trace what happened to a specific order.
- Store thresholds and routing rules in a sheet or table, not hardcoded in nodes.
- Test with a development store before switching on in production.
- Review workflows when you add new apps, channels or shipping methods.
Silent failures are the biggest risk in any automation. Our article on automation error handling best practices explains how to catch them.
Frequently asked questions about Shopify n8n
Is there a Shopify node in n8n?
Yes. n8n includes a Shopify node for common actions such as reading orders, products and customers, plus a trigger that responds to Shopify events. For anything the node does not cover, the HTTP Request node can call Shopify’s API directly.
Should I use Shopify Flow or n8n?
Use Shopify Flow for automations that stay inside Shopify, such as tagging orders or hiding out-of-stock products. Use n8n when workflows need to reach other systems or need more complex logic. Many stores use both side by side.
Can n8n handle high order volumes from Shopify?
It can, with the right setup. Self-hosted n8n can run in queue mode with multiple workers, and workflows should batch API calls and respect rate limits. For very high volumes or critical flows, a dedicated integration service may be the better fit.
Automate your store with confidence
SiteWright Technologies builds and maintains n8n workflows and custom integrations around Shopify, from a single order-routing flow to a full back-office setup. Learn more about our automation solutions, or get in touch with a list of the tasks you want off your team’s plate.


