I’m using the WooCommerce Trigger node to listen for the order.created event, but the workflow never runs — even when new orders are placed. No webhook seems to be created in WooCommerce, and n8n doesn’t receive any data.
I expected the WooCommerce Trigger node to register a webhook automatically when I activated the workflow, but it’s not happening.
What is the error message (if any)?
No error messages — the node executes without issue in test mode and the workflow activates successfully. But nothing happens when orders are placed.
Please share your workflow
Share the output returned by the last node
No output is returned because the node never fires.
This is a very common issue with the WooCommerce Trigger node, and it’s a great question to help the community. The problem you’re describing is almost always related to how the webhook is registered, which can be an external issue from n8n itself.
Here are a few things to check that are common culprits:
Server and Firewall Issues: The most frequent cause is that your server’s firewall or hosting provider is blocking incoming requests from n8n’s webhook. N8n’s webhook URL needs to be publicly accessible for WooCommerce to send data to it. The fact that no webhook is created suggests the initial registration request from n8n to WooCommerce is being blocked.
SSL/TLS Certificate Problems: WooCommerce requires a valid SSL/TLS certificate to register webhooks. If your site’s certificate is expired, self-signed, or has configuration issues, it can prevent the webhook from being created.
Permissions and API Keys: Double-check your WooCommerce API keys. The keys need to have “Read/Write” permissions to allow n8n to create and manage webhooks. A “Read” only key will not be sufficient.
Incorrect URL/Base URL: For n8n Cloud, the webhook URL is handled automatically. However, you should ensure there are no URL redirects or misconfigurations on your WooCommerce site that might prevent it from correctly sending data to the n8n webhook URL. This is less common but still worth checking if other solutions fail.
WooCommerce Site Health: Go to your WooCommerce settings and check the “System Status” or “Site Health” page. Look for any warnings or errors that might be preventing webhook creation.
The issue is likely not with the n8n node itself, but with the communication between your n8n instance and your WooCommerce store.
Thank you for your reply! I am still looking into this and have hired someone at this point to investigate further. I’ll be sure to update here one I figure out why the woocommerce order.created node was not working.
I wasn’t ever able to get the woocommerce order.created trigger node to work. Even after hiring 2 different n8n specialist. We ended up using a webhook trigger instead. Hoping that this issue gets fixed eventually.