n8n’s e‑commerce integration nodes connect directly to the two most widely deployed storefront platforms — Shopify and WooCommerce — providing real‑time order event triggers, inventory and fulfillment operations, product catalog management, and shipping label generation through a unified resource‑operation model. Shopify offers 57 triggers and 11 actions spanning orders, products, customers, inventory, and drafts; WooCommerce provides dedicated trigger and action nodes for orders, customers, and products. Combined with community shipping nodes for ShipStation and Shippo, these nodes form a complete automation stack for online retail.

What Shopify triggers and actions does the n8n Shopify node provide, and how do you configure them?

The native Shopify n8n integration provides 57 distinct triggers covering every major Shopify event — Order Created, Order Paid, Order Fulfilled, Product Created/Updated/Deleted, Customer Created, Cart Abandoned, Inventory Levels Updated, Refund Created, among others — plus 11 actions for manipulating store data: order CRUD (create, delete, get, get many, update), product CRUD (create, delete, get, get many, update), and draft order creation [1].

To configure the connection, generate a Shopify Access Token by creating a custom app in your Shopify admin under Settings → Apps and sales channels → Develop apps. Configure only the API scopes you actually need — read access for triggers and write access for order fulfillment and inventory updates, following the principle of least privilege. Enter your shop subdomain (yourstore.myshopify.com) and Access Token in n8n’s credential panel, and the node is ready. For fulfillment workflows specifically, note that Shopify heavily utilizes the Fulfillment Order API; you must first fetch the fulfillment_order_id associated with an order before sending the fulfillment command — using the standard Order ID will fail. A production fulfillment workflow chains a Webhook or Shopify Trigger node with a Code node that normalises the payload, then a Shopify Action node or HTTP Request node that sends the tracking number, carrier, and line items to mark the order as fulfilled [5]. For complete e‑commerce pipeline patterns that sync orders, inventory, and customer data across platforms, see the ETL pipeline automation guide.

How do you configure the WooCommerce node and automate order, customer, and product operations?

The WooCommerce node provides dedicated trigger and action nodes for three resource types: Orders (create, get, get many, update, delete), Customers (create, get, get many, update, delete), and Products (create, get, get many, update, delete). To configure the connection, generate REST API keys in WooCommerce under WooCommerce → Settings → Advanced → REST API, then enter the Consumer Key and Consumer Secret in the n8n credential form along with your store domain [2].

The WooCommerce Trigger node fires when a new order is placed, or a customer or product is created or updated. For historical data, the “Get Many” operation on the WooCommerce node pulls past orders in bulk, enabling migrations of historical order records into Google Sheets or a database for reporting. Ensure your n8n version is updated to at least the 2026 release for the smoothest experience with these nodes [10]. A common pattern: a WooCommerce webhook fires on new order, a Code node normalises the payload, and the order is pushed to Slack for real‑time notification and to Google Sheets for archival [6]. For AI‑powered order enrichment — scoring customers by lifetime value or predicting churn risk — connect the WooCommerce node to an OpenAI or Anthropic node, as detailed in the n8n AI Nodes reference.

How do you use ShipStation, Shippo, and HTTP Request nodes for shipping and fulfilment in n8n?

n8n does not ship with native ShipStation or Shippo nodes, but the community has filled the gap. The @velocity-bpa/n8n-nodes-shipstation node provides comprehensive access to 7 ShipStation resources — Orders (create, get, update, delete, mark as shipped, unassign user), Shipments (create label, get, track, void label, get rates), Products, Warehouses, Carriers, Stores, and Customers — all with full CRUD capabilities [3].

For Shippo integration, the community node at NCNodes.com provides parcel creation and label generation for e‑commerce orders. Both ShipStation and Shippo authenticate via API Key and API Secret generated in their respective account settings. The canonical shipping fulfilment pattern chains: Webhook or Shopify Trigger (order created) → Code node (normalise shipping address + package weight) → ShipStation/Shippo node (generate shipping label + tracking number) → Shopify node or HTTP Request (push tracking back to store) → Slack/Gmail node (notify warehouse and customer). A critical implementation detail: when fulfilling Shopify orders, always use the Fulfillment Order ID — not the standard Order ID — as required by Shopify’s Fulfillment Order API [8]. For multi‑warehouse routing, split orders by warehouse location using a Switch node, then send each subset to the corresponding ShipStation warehouse ID for label generation. For the complete production‑grade order‑to‑fulfilment pipeline, see the DevOps monitoring guide.

How do you set up real‑time order event triggers for instant processing and notifications?

Both Shopify and WooCommerce expose order events through their respective trigger nodes. The Shopify node fires 8 distinct order‑related triggers: Order Created, Order Paid, Order Fulfilled, Order Cancelled, Order Updated, Order Edited, Fulfillment Created, and Fulfillment Updated — covering the entire order lifecycle from cart to delivery. The WooCommerce trigger fires on New Order events captured via webhook from the WooCommerce REST API [1] [6].

For immediate Slack or email notifications on high‑value orders, chain a Shopify Trigger (Order Created) → IF node (check order total > threshold) → Slack node (notify #vip-orders channel). For abandoned cart recovery, use the Shopify Cart Create/Update trigger to fire a workflow that waits a configurable duration (e.g., 2 hours), then sends a personalised email via Gmail or SMTP with the cart contents and a direct checkout link. For failed payment alerts, the Order Cancelled trigger can detect cancellations due to payment failure and immediately alert the support team. The n8n blog provides a complete walkthrough for sending Shopify new‑order notifications to Slack [9]. For designing multi‑condition routing — for example, high‑value orders to VIP queue, low‑value to standard queue — see the IF & Switch node branching guide.

How do you manage inventory synchronisation across multiple sales channels with n8n?

n8n’s Shopify integration provides 7 dedicated inventory triggers: Inventory Levels Updated (fires on any stock change at any location), Inventory Levels Connected/Disconnected, Inventory Items Updated/Deleted/ Created, and Location Updated/Deleted/Created — giving you granular control over real‑time stock monitoring across every warehouse location [1].

For multi‑platform stores, set up a dual‑directional sync: a Shopify inventory trigger fires on a stock change, a Code node normalises the quantity and SKU, and a WooCommerce or Google Sheets node pushes the update to the other platform. For multi‑warehouse environments, the Location triggers let you route inventory changes to the correct external warehouse management system. For proactive reordering, add an IF node after the inventory trigger that checks if stock falls below a configurable threshold (e.g., 5 units), then sends a restock alert to Slack and creates a purchase‑order draft using the Shopify Action node. For API‑based inventory syncs that connect Shopify to ERP systems like NetSuite, n8n workflows can push tracking numbers and fulfilment status back to Shopify once the ERP confirms the shipment. For scaling these inventory workflows to handle tens of thousands of SKUs, using the SplitInBatches node for batch processing is recommended, as described in the SplitInBatches loop & batch processing guide.

How do you build a complete order‑to‑fulfilment workflow from webhook trigger to shipping label?

A production‑grade order‑to‑fulfilment pipeline chains six distinct stages: (1) Webhook or platform trigger fires on order creation; (2) Inventory check validates stock levels via an Airtable, Google Sheets, or database node, branching to an out‑of‑stock path when needed; (3) Code node normalises the payload — formatting phone numbers, calculating shipping weights, splitting orders by warehouse location; (4) Shipping node (ShipStation or Shippo) generates the label and returns a tracking number; (5) Platform node pushes the tracking number and fulfilment status back to Shopify or WooCommerce; (6) Notification sends the tracking link to the customer via Gmail and to the warehouse via Slack [8].

For high‑volume operations processing thousands of orders daily, add a SplitInBatches node before the shipping label generation step to batch orders in groups of 10–50, with a Wait node between batches to respect carrier API rate limits. Implement an Error Trigger workflow that catches label‑generation failures and retries with exponential backoff — the shipping API returns 429 (rate limit) or 503 (service unavailable) for transient failures [8]. For multi‑warehouse routing, split orders by location using a Switch node before the shipping step, then send each subset to the ShipStation warehouse ID corresponding to the nearest fulfilment centre. For the complete error handling and retry logic patterns, see the n8n Error Handling nodes guide.