How to test a webhook in n8n?

The simplest way to test a webhook in n8n is to open your workflow, set the Webhook node to Test URL (by switching the workflow to Test mode), copy the Test URL the node shows, and send a real request to it using a tool like curl, Postman, or a browser. n8n will “wait” for the incoming request and show you the data immediately so you can continue building the workflow.

 

What “testing a webhook” really means in n8n

 

In n8n, a Webhook node is a trigger node. That means it only runs when something external sends an HTTP request to a special URL that n8n provides. Because webhooks are event-driven, you cannot simply click “Execute workflow” to test them — n8n needs to receive a real HTTP request.

When the workflow is in Test mode, the Webhook node exposes a temporary URL called the Test URL. This lets you test safely without activating the production version of the URL. When the workflow is Activated, n8n instead exposes a Production URL, which does not accept test executions.

 

Step‑by‑step way to test a webhook in n8n

 

• Open your workflow and click the Webhook node. You will see two URLs: Test URL and Production URL.
• Switch your workflow into Test mode (top-right toggle). n8n is now “listening” for that Test URL.
• Copy the Test URL.
• Send a request to it using a real HTTP client like a browser (for GET), Postman, or curl.
• As soon as n8n receives the request, the workflow will execute and show the incoming JSON/body/headers in the node output.

 

curl -X POST https://your-n8n-domain/webhook-test/abc123 \
  -H "Content-Type: application/json" \
  -d '{"hello":"world"}'

 

After running this, you’ll immediately see the output appear under the Webhook node in n8n. That means the webhook works and your workflow can continue.

 

What beginners often miss

 

• You must be in Test mode to use the Test URL. If you’re not, the request returns an error because n8n isn’t listening for test executions.
• GET vs POST matters. If the webhook is set to POST only, a GET request will not trigger it.
• Query parameters, headers, and body appear in separate fields in the node output: query, headers, body.
• Local vs cloud. If you run n8n locally, external services cannot reach your Webhook URL unless you expose it with something like ngrok.

 

Production‑level testing tips

 

• Always test with the Test URL so you don’t accidentally fire your real production workflow.
• If your service supports retries (e.g., Stripe, Shopify), keep your workflow idempotent — meaning repeating the same payload should not break anything.
• Use an Error Workflow for production so that failed webhook runs don’t silently disappear.
• When debugging signatures (e.g., Stripe HMAC), log the raw body using the Webhook node’s Raw Body option.

If you follow the steps above, you’ll always know exactly how to test and validate any webhook safely before activating the workflow.