How can I consolidate n8n’s webhook endpoints into a single URL?

The behavior you're experiencing is due to how n8n is designed to work: one endpoint is for manual testing/editing (the test endpoint) and one is for production execution. Currently, n8n does not provide an officially supported configuration to disable the test endpoint and use a single endpoint for both purposes. In other words, even if you set

YAMLCopied
- N8N_ENDPOINT_WEBHOOK=webhook
- N8N_ENDPOINT_WEBHOOK_TEST=webhook
- N8N_ENDPOINT_WEBHOOK_WAIT=webhook

n8n still relies on the dual-endpoint concept (with test used in the Editor UI to capture data) and will route requests accordingly. This means that for proper functioning of the Editor (which helps capture data structure) while executing flows via production, both endpoints need to exist as designed.

If you’re forced into a scenario where your integrated app can only save one static URL, you might consider these workarounds:

• Use a reverse proxy or route mapper: Route incoming requests to both endpoints behind the scenes even if the URL is static externally. That is, have your proxy forward GET requests (or the ones your remote app uses) to the appropriate endpoint based on the request type.
• Employ a custom endpoint layer: Build a small external service (or use a serverless function) that receives the single incoming URL and then internally makes requests to the proper n8n endpoints depending on whether it’s for testing (capturing webhook data) or execution.

While these workarounds could help in your integration scenario, n8n itself does not offer a configuration to completely merge the test and production endpoints into one without switching between different Docker Compose setups.

For more details, please refer to our Webhook node common issues documentation which outlines the separation between the test and production endpoints in n8n.