Chat Trigger Node incorrectly calls webhook-test endpoint after upgrade to 2.18.5, breaking GUI testing with access token protection

[Viktor_Tymchynskyi]

Describe the problem/error/question

After upgrading n8n from 2.3.4 to 2.18.5, the Chat Trigger Node started invoking a webhook-test endpoint when sending messages from the n8n GUI chat panel.

This behavior was not present in earlier versions and appears to be a regression. The unexpected call to webhook-test breaks workflow testing in environments where webhook endpoints are protected.

In our setup, both webhook and webhook-test endpoints are secured with external OAuth2, requiring a valid access token. Since the GUI-triggered request does not include authentication, it fails, making it impossible to test workflows via the UI.

---

What is the error message (if any)?

No explicit error is shown in the n8n UI, but in the browser Network tab:

• A POST request is sent to: /webhook-test//
• The request fails due to missing OAuth2 authentication (e.g., 401/403 depending on setup)

---

Please share your workflow

• (Chat Trigger Node → any downstream node)

---

Expected behavior

Sending a chat message from the GUI should:

• Not invoke the webhook-test endpoint, or
• Behave consistently with previous versions where this call was not made

Actual behavior

• A POST request is sent to the webhook-test endpoint when triggering a chat message from the GUI
• The request is visible in the browser Network tab
• Workflow execution depends on this endpoint

Share the output returned by the last node

No output is returned because the request to webhook-test fails authentication and blocks execution.

---

Information on your n8n setup

• n8n version: 2.18.5 (issue), previously 2.3.4 (working)
• Database (default: SQLite): Postgres (default)
• n8n EXECUTIONS_PROCESS setting (default: own, main): default
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
• Operating system: Linux
  
  

[tamy.santos]

Hi @Viktor_Tymchynskyi , welcome to the n8n community
It looks like a regression to me as well. Have you managed to get past it on your side?

As a temporary workaround, you could allow or route /webhook-test/* only in the test environment, or downgrade to the version that was working before. Also, before I forget, it would be important to register this case under the Known Issues category so the n8n team can properly track it.

I saw that you opened the GitHub issue 3 days ago and that it has already been assigned to the relevant team, so now we wait

[Viktor_Tymchynskyi]

Hi @tamy.santos,

Thanks for the reply.
We’ve currently decided to stay on version 2.3.4, as this issue is blocking our upgrade to the latest version.

Could you please advise how to register this case under the “Known Issues” category?

[tamy.santos]

off course!

first you go in categories > all categories

then Known issues