n8n Shopify Integration: Automate Orders, Inventory and Customer Data

n8n connects to Shopify through two built-in nodes. The Shopify Trigger registers a real Shopify webhook and fires on topics including orders created, paid, updated, cancelled and fulfilled, plus customers, products, carts, checkouts, refunds, collections and locations. The Shopify action node then reads and writes, but only across two resources: Order and Product, each with create, get, get all, update and delete. There is no Customer resource and no Inventory resource on the action node, so customer tagging and stock checks go through the HTTP Request node against the Shopify Admin API, reusing the same credential. Knowing that boundary up front saves an afternoon.

The rest of this guide is the practical part. At a few hundred orders a month manual process is survivable. At a few thousand it is a full-time job nobody budgeted for.

Order data gets copy-pasted into spreadsheets, someone checks inventory by hand every morning, and finance waits until Friday for numbers Shopify already knows in real time.

This is what n8n solves. It is an open-source workflow automation tool that connects Shopify to the rest of your stack (CRM, warehouse system, email platform, Slack, Google Sheets) and acts the moment something happens in your store.

How the N8N Shopify Integration Works

n8n includes native Shopify nodes, so there is no third-party connector to buy. Authentication is an access token from a Shopify custom app (what n8n recommends for a single store) or OAuth2 for public apps. Shopify no longer issues API keys with passwords, so the old API key method is deprecated.

The Shopify node supports two modes:

Trigger Mode (Webhooks)

The Shopify Trigger node registers a webhook with your store, so workflows fire the moment something happens. The topic list includes:

• New order created
• Order updated (status change, fulfillment update)
• Order paid
• Order cancelled or refunded
• New customer created
• Customer updated
• Fulfillment created or updated
• Product created, updated or deleted
• Cart or checkout created or updated (the basis for abandoned checkout work)
• Refund created

Action Mode (API Calls)

The Shopify action node covers two resources. Order: create, get, get all, update, delete. Product: create, get, get all, update, delete. Anything outside those two, customers and inventory levels included, needs the HTTP Request node pointed at the Shopify Admin API. You can select your Shopify credential inside that node, so it is extra configuration rather than extra authentication.

Most useful workflows combine both: a trigger fires, action nodes pull context, logic runs, other systems get updated.

The 7 Shopify Automations Consumer Brands Should Build First

Ordered by time to value:

1. Order Confirmation + Fulfillment Status Routing

The workflow: when a new order is placed → check order value and customer tags → route to the appropriate fulfillment logic → update your 3PL or warehouse system → notify the customer via your preferred channel.

Why it matters: brands doing $10M+ often have several fulfillment paths (standard warehouse, drop-ship suppliers, made-to-order items). n8n routes each order by SKU, geography or customer tier without anyone touching it.

What you connect: Shopify, conditional logic, your WMS or 3PL API (ShipBob, ShipStation, Flexport), then a customer notification by email, SMS or your CX platform.

2. Low Inventory Alerts to the Right People

The workflow: a Schedule Trigger runs every morning, an HTTP Request node reads inventory levels from the Shopify Admin API, an IF node compares each against its threshold, and anything below it alerts the buying team in Slack or email and optionally drafts a purchase order in your ERP.

This one is scheduled rather than event-driven on purpose. The n8n Shopify Trigger has no inventory-level topic, so there is nothing to subscribe to. A daily or hourly poll is the working pattern.

A single stockout on a hero SKU during peak season can cost more than a year of automation infrastructure.

Set different thresholds per SKU category, for example a 30-day buffer for slow movers and a 7-day buffer for fast movers, pulling velocity data from your analytics platform through the same HTTP Request node.

3. Customer Tagging for Segmentation

The workflow: an orders/create trigger fires, a Code node calculates lifetime value and order frequency, an HTTP Request node writes Shopify customer tags (VIP, Repeat, Single-Purchase, Lapsed), and those tags sync to your email platform. The tag write is an HTTP Request node, not the Shopify node, which has no Customer resource.

Most stores sit on segmentation data they never use. This keeps the tags current without anyone running exports.

4. Daily Revenue Report to Slack or Email

The workflow: every morning at 7am → pull yesterday's Shopify orders via API → calculate total revenue, order count, average order value, top SKUs → format a clean summary → post to your #revenue Slack channel.

That replaces the morning ritual of logging in, setting date ranges and screenshotting for standup.

Build it with n8n's cron-based scheduler plus the Shopify and Slack nodes, no code required. Our n8n Slack integration guide has the exact setup.

5. New Customer → CRM Contact Creation

The workflow: a customers/create trigger fires, a lookup checks whether they already exist in your CRM, and if not you create a contact with order context, tags and acquisition source, assigned to an owner by channel or order value.

For brands with a sales or account management motion this keeps the CRM current without manual entry. We have built it for HubSpot; the pattern works with any CRM that has an API. See the n8n HubSpot integration guide.

6. Subscription and Reorder Reminders

The workflow: 30 days after a fulfilled order for a consumable product → check if the customer has reordered → if not, trigger a reorder reminder via your email platform → track whether the reminder converted.

Brands selling consumables leave revenue on the table without a reorder sequence, and this one runs on actual purchase dates rather than guessed timing.

7. Abandoned Checkout Enrichment

The workflow: a checkouts/create or checkouts/update trigger fires, you extract the email and cart contents, enrich with existing customer history, and pass the lot to your email platform for a personalised recovery sequence. Shopify has no dedicated "abandoned checkout" webhook topic; the checkout topics plus your own timing logic are what you build on.

Shopify's built-in abandoned cart emails are generic. n8n lets you pass cart contents, customer tier and purchase history to your email tool, so the recovery message references what they actually left behind and acknowledges a repeat customer.

N8N vs Zapier vs Make for Shopify Automation

All three connect to Shopify. The differences show at volume.

For brands with customer PII concerns, particularly in the EU, self-hosted n8n means order data never transits a third-party automation server.

Setting Up the N8N Shopify Connection

Step 1: Create a Shopify Custom App

1. In your Shopify admin, go to Settings → Apps and sales channels → Develop apps
2. Click Create an app and name it (e.g., "N8N Integration")
3. Under Configuration → Admin API access scopes, enable the permissions you need:
   • read_orders, write_orders for order automation
   • read_customers, write_customers for customer tagging (used by the HTTP Request node)
   • read_inventory for inventory alerts
   • read_products for product lookups
4. Click Save, then Install app
5. Copy the Admin API access token and the API secret key. n8n needs both: the token as Access Token and the secret as APP Secret Key.

Step 2: Connect Shopify in N8N

1. In N8N, go to Credentials → New → Shopify
2. Enter your Shopify store URL (e.g., yourstore.myshopify.com)
3. Paste the Admin API access token and the API secret key
4. Click Test credential. If it returns your store name, you are connected

Step 3: Build Your First Trigger Workflow

1. Create a new workflow in N8N
2. Add a Shopify Trigger node as the starting node
3. Select the topic, for example orders/create
4. Set your N8N instance URL as the webhook endpoint (N8N registers this with Shopify automatically)
5. Add the next node: Slack, HubSpot, Google Sheets, email, whatever you are routing to
6. Use N8N's expression editor to map Shopify fields (order ID, customer name, total price, line items) to the destination

New to n8n? Our first workflow guide covers the canvas, expressions and testing, and the webhook tutorial explains triggers under the hood.

Common Pitfalls (and How to Avoid Them)

Shopify Admin API Rate Limits

Shopify meters the GraphQL Admin API by calculated query cost, in points per second: 100 on standard plans, 200 on Advanced, 1,000 on Shopify Plus and 2,000 on Commerce Components. It is a leaky bucket, so short bursts are absorbed and sustained load is not. During a flash sale a burst of simultaneous orders will hit the ceiling. Build exponential backoff into the workflow; our n8n error handling guide has the pattern.

Note that a cost is per query, not per request, so an expensive query can consume a large share of your per-second budget on its own. Request only the fields you need.

Webhook Deduplication

Shopify occasionally sends duplicate webhook events, especially under load. Add a deduplication check with an IF node: store processed order IDs in a database or Airtable and skip anything already seen.

Test in Staging First

Use a Shopify development store first. n8n's test mode replays real webhook payloads from test orders without touching production.

What $10M+ Consumer Brands Actually Build

The brands that get the most from this do not automate one workflow. They build a connected operations layer.

A typical architecture:

• Orders layer: All new orders → route to 3PL → update ERP → notify customer → tag customer in CRM
• Inventory layer: Daily inventory checks → low-stock alerts → draft POs in ERP → Slack notification to buying team
• Customer intelligence layer: Post-purchase tagging → CRM sync → segmented email platform updates
• Revenue reporting layer: Daily Slack report → weekly Google Sheets digest → monthly data push to BI tool
• Exception layer: Cancelled orders → refund initiation → inventory restoration → customer service ticket creation

Built correctly, the operations team stops logging into Shopify for routine work and only touches exceptions.

The win is usually redeployment rather than headcount cuts: people who were processing orders move onto customer experience work that grows revenue. Our Le Marquier case study covers what that looked like for one consumer brand.

When to Build It Yourself vs. Hire Help

This is well within reach for a technical founder or a developer with a few hours. The first three workflows (order routing, inventory alerts, daily revenue report) are a weekend job.

Where it gets more complex:

• Multi-step conditional routing with edge cases (Shopify Plus with multiple storefronts, international order routing)
• Connecting to legacy ERP systems with non-standard APIs
• High-volume error handling at 10k+ orders per month
• PII compliance and data residency requirements
• Maintaining workflows as your stack evolves

Once operations depend on these running reliably, it is worth having someone build and maintain them properly. Our n8n automation service covers that cycle, and the ROI calculator estimates what it is worth against your current manual spend.

Not sure where to start? The AI readiness assessment takes five minutes.

Ready to Get Started?

Book a free 30-minute discovery call. We'll identify your biggest opportunities and show you exactly what AI automation can do for your business.

Book a Free Discovery Call

Suyash Raj Founder, Voxdonna AI and AiSewak. Writes here about n8n, AI agents, and voice automation.