E-shop Automation with n8n: WooCommerce Webhooks and API
A concrete overview of how WooCommerce sends events and where things can go wrong. The technical details come from the official documentation; the reasoning about what is worth doing is mine.
With WooCommerce, a webhook event is what triggers a workflow: the shop sends a notification to an address you choose whenever an order, product, customer or coupon is created or changed. The Webhook node in n8n is designed to receive such notifications from apps and services; I did not verify the specific WooCommerce setup. For reading and writing data there is the REST API, an interface through which other programs communicate with the shop; access is controlled by keys.
It is worth connecting recurring processes where someone currently copies data from one system to another. If you have few such processes, automation will probably not pay off.
Which e-shop processes are worth connecting
I look for processes with three traits: a clear event triggers them (a new order, a product change), they are always done the same way, and someone currently does them by hand. This is my working method, not a rule from the documentation. Candidates:
- New order → team notification, entry in a spreadsheet or internal system.
- New customer → entry in a CRM or email tool.
- Product change → synchronization with another system, for example inventory.
- New coupon → a notification or entry wherever you keep track of coupons.
I don't cover invoicing and chatbots here; they have their own articles: invoicing automation and AI chatbot for an e-shop. An overview of the service is on the E-shop automation page.
WooCommerce: webhooks as a workflow trigger
A webhook is a notification about an event that the shop sends to an address you choose. According to the WooCommerce documentation, webhooks are useful for connecting the shop with external services and APIs that support them (webhooks documentation). They can be triggered by creating, updating or deleting orders, products, coupons and customers.
The basic topics (event names) are order.created, order.updated, order.deleted and the same triplets for product, customer and coupon.
The Webhook node in n8n creates webhooks that can receive data from apps and services when an event occurs. It is a trigger node that can start a workflow. It supports basic authentication, header authentication, JWT or none, and the maximum payload size (the content of a single message) is 16 MB (n8n documentation). I did not verify the specific setup for connecting WooCommerce to n8n for this article.
The payload is in JSON, and for orders, products, customers and coupons the response is the same as if you had requested it via the REST API.
WooCommerce REST API: keys and permissions
When a workflow needs to read data from the shop or write it, the REST API is used. It is an interface through which another program sends requests to the shop and receives responses. Most integrations require you to generate API keys in WooCommerce and enter them in the external service (REST API documentation). I did not verify the specific way of connecting n8n in this article.
- Check that WordPress permalinks are not set to Plain (Settings > Permalinks). Default permalinks do not work with the API.
- Generate an API key and choose the permission according to the table below.
- Copy the Consumer Key and Consumer Secret. The Secret is shown only once.
- Enter the keys in the external service you are connecting.
| Permission | What it allows the application to do |
|---|---|
| Read | retrieve data from the shop |
| Write | create and update data |
| Read/Write | both read and write |
I recommend giving the key only the permission the workflow needs. According to the REST API documentation, each key is linked to a WordPress user and permissions can be chosen according to the application's needs. If the workflow only reads data, the Read permission is enough.
Technical requirements according to the documentation: WooCommerce 3.5+, WordPress 4.4+ and pretty permalinks. HTTPS is recommended. Requests returning multiple items are paginated by default at 10 items, and the site administrator can change this.
Where WooCommerce webhooks break
- Automatic disabling. The developer documentation states that a webhook is deactivated after 5 consecutive failed deliveries, and to re-enable it you must edit the webhook via the REST API. The user documentation speaks of disabling after more than five errors. The sources disagree on this point. It is just my caution: I would assume it gets disabled after five errors.
- What counts as an error. The user documentation says an error is a response that is not 2xx, 301 or 302. The developer documentation defines failure as a response without a 2xx code. It is not clear from it how 301 and 302 are counted. I recommend that the address respond with a 2xx code.
- Background delivery. Webhooks are sent by default via wp-cron, the task scheduler in WordPress.
- Short history. Only the last 25 delivery records are kept.
In practice: after deploying a workflow, check whether the webhook in WooCommerce is still active. A disabled webhook is one possible reason why automation stops working.
When it is not worth connecting an e-shop
This is my line of reasoning, not a claim from the documentation:
- The process is rare. If a task takes little time, setting up the workflow may cost more than you save. How to calculate it is described in the article on the return on automation.
- The process is not settled. If the rules change often, settle them first and automate afterwards.
- Nobody is there to supervise. A webhook can get disabled and an API key has to be managed. Without someone monitoring it, automation may stop working.
What to start automating first is covered in the article What to automate in a company.
What about Make.com instead of n8n
WooCommerce can also be connected in Make.com. According to the Make documentation, you need an account, an installed WooCommerce plugin, SSL enabled and pretty permalinks (Make: WooCommerce). The differences between the tools are covered in the article n8n vs Make.com.
Frequently asked questions
Do I need a programmer to connect WooCommerce with n8n?
Webhooks can be managed in the WooCommerce settings or via the REST API. The documentation states that a webhook can be configured by the shop owner or their developer. Whether you will need a programmer depends on the specific task, and I did not verify that for this article. The procedure is in the webhooks documentation.
Why have orders stopped arriving in n8n?
One cause may be a disabled webhook. WooCommerce automatically deactivates it after repeated failed deliveries. According to the developer documentation, re-enabling is done by editing the webhook via the REST API. Check its status in the shop and first remove the cause of the errors.
What permission should I give a WooCommerce API key?
The documentation lists Read (reading), Write (creating and updating) and Read/Write. I recommend choosing the smallest one the workflow needs. The Consumer Secret is shown only once, so save it right away.
Can WooCommerce be connected in a way other than n8n?
According to the Make.com documentation, Make has a module for WooCommerce. It requires an account, the WooCommerce plugin, SSL and pretty permalinks. I described the differences between the tools in the article n8n vs Make.com.
Sources
- WooCommerce REST API Documentation — checked 30 September 2026
- WooCommerce REST API — checked 30 September 2026
- Webhooks | WooCommerce developer docs — checked 30 September 2026
- Webhooks Documentation — checked 30 September 2026
- Webhook | Nodes — checked 30 September 2026
- WooCommerce - Apps Documentation — checked 30 September 2026
Related services
Related articles
Not sure which processes in your e-shop to connect?
Describe what you do by hand today, and we'll discuss whether it can be connected and whether it's worth it. My work starts at €390; for pricing details see the article How much AI automation costs.
Write to me →