WooCommerce REST API authentication normally uses a consumer key and consumer secret generated for a WooCommerce user. For an HTTPS store, the simplest pattern is HTTP Basic Authentication: send the consumer key as the username and the consumer secret as the password.
WooCommerce REST API Authentication: API Keys, Requests, and TroubleshootingRead More
An n8n MCP server setup can expose selected workflow-backed tools to an AI client without giving that client unrestricted access to your n8n instance. This guide uses n8n’s MCP Server Trigger as the server implementation and Claude Code as the client. The primary deployment model is a running n8n instance reachable by HTTPS; Claude Code connects to the MCP URL that n8n generates.
How to Set Up an n8n MCP Server and Connect It to AI ToolsRead More
When WooCommerce webhooks are not working, start by finding the stage that failed: the event did not trigger, WooCommerce did not create a delivery attempt, the request could not reach the endpoint, or the receiving application rejected it. That sequence prevents a common mistake: changing webhook settings when the actual problem is an unavailable receiver, failed signature check, or firewall rule.
WooCommerce Webhooks Not Working? 10 Things to CheckRead More
The simplest way to connect WooCommerce to n8n for a working test is to send a WooCommerce order event to an n8n Webhook trigger, inspect the order payload, and pass a small set of fields to a safe next step such as an internal log or formatting node.