TL;DR: This WooCommerce to n8n migration guide shows you how to move your store automations off a pile of plugins and paid Zapier zaps and into one self-hosted n8n instance. You will connect WooCommerce to n8n, rebuild the core flows (order alerts, low stock warnings, welcome emails, and an abandoned checkout nudge), and end up with a single dashboard that runs every automation for a flat hosting cost instead of per-task pricing.
Most WooCommerce stores do not start with an automation strategy. They start with a problem, install a plugin, and repeat. A year later the average store is running three review plugins, a couple of Zapier zaps, a Mailchimp connector, and a follow-up email tool, each billed separately and none of them talking to each other. Moving all of that into n8n gives you one place to see what runs, what failed, and what it costs. This guide walks through the migration without taking your store offline.
What this migration actually does
A migration to n8n is not a replatform. Your WooCommerce store stays exactly where it is. What changes is where the logic lives. Instead of a dozen plugins each reacting to an order in their own way, n8n becomes the central hub that listens to your store and fans actions out to Gmail, Google Sheets, Slack, Telegram, or any API you already pay for.
The pattern is simple. WooCommerce emits an event such as a new order, a status change, or a low stock signal. n8n catches that event through a webhook or a scheduled poll, runs whatever steps you define, and sends the result wherever it needs to go. Once that pipe is open, every automation you used to rent becomes a workflow you own.
Why it beats the default plugin stack
The default WooCommerce setup spreads your automation logic across tools that never share data. Your review plugin does not know the customer already got a welcome email. Your Zapier zap does not know stock is low. When something breaks, you check four dashboards to find out which one failed.
n8n collapses that into a single execution log. You see every run, the exact data that passed through each node, and the precise step that errored. Pricing also stops scaling against you. Zapier and most WooCommerce automation plugins charge per task or per contact, so your bill grows with your order volume. A self-hosted n8n instance runs on a small VPS for a fixed monthly cost no matter how many orders flow through it. For a store doing a few thousand orders a month, that difference adds up fast.
There is one honest trade-off. n8n asks more of you up front. You build the flows yourself instead of clicking a template, and you maintain the server. If you would rather skip that part, the migration still pays off because the running cost afterward is far lower, and you can have someone set it up once.
What you need before you start
You need a running WooCommerce store on WordPress with admin access, an n8n instance (self-hosted on a VPS or n8n Cloud), and admin rights to generate WooCommerce REST API keys. For the example flows you will also want a Gmail account for transactional email, a Google Sheets file for logging, and a Slack or Telegram channel for internal alerts. None of those are mandatory for the connection itself, but they cover the automations most stores want first.
If you are self-hosting, make sure your n8n instance is reachable over HTTPS. WooCommerce webhooks will not deliver to an insecure or unreachable URL, and a valid certificate saves you a long debugging session later.
Node-by-node overview
The starter migration workflow uses a short, readable chain of nodes. A WooCommerce Trigger node listens for the order.created event and fires the moment a customer checks out. A Set node trims the heavy WooCommerce payload down to the fields you actually use, such as order number, total, customer name, email, and line items. An IF node branches on order value so high tickets can take a different path. A Gmail node sends the customer a branded confirmation. A Google Sheets node appends the order to a running log. A Slack or Telegram node drops an internal heads-up to your team. Every node after the trigger is optional, so you migrate one automation at a time rather than all at once.
Step-by-step build
- In WooCommerce, go to Settings, Advanced, REST API and create a new key with read and write permissions. Copy the consumer key and secret somewhere safe, because the secret is shown only once.
- In n8n, open Credentials, add a new WooCommerce API credential, and paste the consumer key, consumer secret, and your store URL. Save and run the built-in connection test to confirm n8n can reach the store.
- Create a new workflow and add a WooCommerce Trigger node. Select the order.created event. n8n will register a webhook inside WooCommerce automatically, so you do not have to configure one by hand.
- Place a test order on your store, or use an existing order in the trigger’s listen mode, so n8n captures a real payload. Working from real data beats guessing at field names.
- Add a Set node and map only the fields you need. Pull order number, total, currency, billing first name, billing email, and a joined list of product names. This keeps later nodes clean.
- Add an IF node that checks whether the order total is above your VIP threshold. The true branch can route to a priority alert, while the false branch follows the standard path.
- Add a Gmail node on the main path. Compose the confirmation email using expressions to insert the customer name, order number, and items. Send it from your store’s support address.
- Add a Google Sheets node set to append a row. Map each field to a column so you build a live order ledger you can sort and filter without opening WooCommerce.
- Add a Slack or Telegram node that posts a one-line summary to your team channel, for example the order number, total, and customer name.
- Activate the workflow. Place one more real order and confirm the email arrives, the row appears, and the alert fires. Once it does, retire the matching Zapier zap or plugin so you are not running two systems against the same event.
Repeat that last step for every automation you migrate. Move one flow, verify it, switch off the old version, then move the next. A staged migration like this never leaves a gap where orders go unnoticed.
Common mistakes to avoid
The first mistake is migrating everything in one weekend. Move flows one at a time and keep the old tool running until the n8n version proves itself on real orders. The second is leaving both systems active, which sends customers two welcome emails and doubles your alerts. Always switch off the old automation the moment the new one passes its test.
The third is forgetting that WooCommerce webhooks need a reachable HTTPS endpoint. If your trigger never fires, check the webhook status inside WooCommerce under Settings, Advanced, Webhooks before you touch anything in n8n. The fourth is passing the entire WooCommerce payload into every downstream node. It is large and slows reads, so trim it early with a Set node. The last is skipping error handling. Add an error workflow that pings your Telegram so a failed run tells you instead of going silent.
Cost at realistic volume
Take a store handling 3,000 orders a month with a welcome email, a review request, a low stock alert, and an order log. On Zapier those four automations across that volume push you into a paid tier well above 50 dollars a month, and the bill climbs as orders grow. A stack of premium WooCommerce plugins to cover the same ground often runs 15 to 30 dollars each per month.
A self-hosted n8n instance on a small VPS costs roughly 5 to 10 dollars a month and does not care whether you process 3,000 orders or 30,000. Gmail handles transactional volume on a standard Workspace plan, and Google Sheets is free. The migration usually pays for itself inside the first month, and the gap widens every time your order count goes up.
Ready-to-import template
You do not have to build the starter workflow from a blank canvas. Our ready-to-import migration template includes the WooCommerce trigger, the field-trimming Set node, the VIP branch, and the Gmail, Sheets, and Slack steps already wired together, plus a setup guide and a credentials guide that walks through every API key. Grab it from the downloads library and import the JSON straight into your n8n instance.
If you would rather have the whole migration handled for you, our team installs n8n on your server, moves your WooCommerce automations over, and hands you a documented stack. See the done-for-you setup service for what that covers.
Frequently asked questions
Will migrating to n8n take my WooCommerce store offline?
No. The migration only changes where your automation logic runs. WooCommerce stays exactly as it is, on the same hosting, with the same theme and checkout. n8n connects through the REST API and webhooks, so your storefront never goes down during the move.
Do I need to know how to code to migrate to n8n?
Not for the core flows. n8n is visual, and the WooCommerce, Gmail, and Sheets nodes are configured through forms. You will write small expressions to insert order details into emails, but those are short and well documented. Anything heavier can be handled by an imported template.
Can I keep some automations on Zapier during the migration?
Yes, and you should. The safest path is to run both systems in parallel for one automation at a time. Verify the n8n version on real orders, then switch the old zap off. Running them side by side briefly avoids any gap where an order slips through unhandled.
How do I stop customers getting duplicate emails?
Duplicates almost always come from leaving the old plugin or zap active after the n8n flow goes live. Migrate one automation, confirm it works, then immediately disable the matching old version. Keeping a short migration checklist of what you have switched off prevents overlap.
Does this work for a Shopify store too?
The same approach applies. n8n has a native Shopify trigger and Shopify nodes, so you swap the WooCommerce trigger for the Shopify one and keep the rest of the chain. The migration logic, staged cutover, and cost savings are identical for either platform.
Related guides
If you are building out your store automation stack, start with the n8n Shopify automation hub for the full set of store workflows. From there, the real-time order alert and low stock alert guides are the two most stores migrate first. Browse the rest under Shopify and e-commerce automation.