Repair guides / Webhooks

n8n webhook not working? Start here.

By RelayMend · Published 26 September 2026

First establish whether the event reached n8n. A request that never arrived and a workflow that received the wrong data need different repairs.

1. Check the URL and HTTP method

n8n provides separate test and production webhook URLs. The test URL is used while listening for a test event; the production URL is used with the published workflow. Confirm which URL the sending system actually calls and whether its HTTP method matches the Webhook node.

If a manual test works but the real sender fails, compare those two requests. Do not assume they use the same URL, method or body simply because they represent the same business event. These distinctions are documented in n8n’s official Webhook troubleshooting guide.

2. Separate arrival from processing

Create a small evidence table before making changes. Record the event’s approximate time, a non-sensitive identifier, the sender’s reported response and whether an execution appeared. Avoid copying secret headers or private webhook URLs into a shared support document.

3. Reproduce without side effects

Use a separate test path and fictional data. Disconnect or replace actions that send messages or write to live systems. For example, use a fictional event identifier and a test destination to verify that the expected field arrives. Keep that event identifier stable when testing how repeats are handled.

Do not repeatedly resend a real customer event just to see whether it works. Once delivery is restored, those repeated attempts may become repeated actions. Decide how the receiving system should recognise a repeat before retrying production traffic.

4. Verify the whole handoff

An incoming response alone is not your acceptance criterion. Check the final destination and the fields your business actually uses. Preserve the successful example alongside an invalid example so a later change can be compared with both.

If the event arrives but the CRM output is wrong, continue with our guide to successful executions with incorrect data. If it never arrives, keep the investigation focused on delivery evidence rather than rewriting the downstream workflow.