n8n - 💡(How to fix) Fix Chat Trigger Node incorrectly calls webhook-test endpoint after upgrade to 2.18.5, breaking GUI testing with access token protection [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#29710Fetched 2026-05-05 06:03:07
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

After upgrading n8n from 2.3.4 to 2.18.5, we encountered an issue with the Chat Trigger Node.

When sending a chat message from the n8n GUI, the workflow now triggers a request to a webhook-test endpoint, for example:

http://localhost:5678/webhook-test/<id>/<sessionId>

This behavior was not present in earlier versions (e.g., 2.3.4) and appears to be a regression.


Error Message

  • error: all

Root Cause

Because of this:

  • The unexpected webhook-test call fails authentication
  • It becomes impossible to test workflows via the n8n GUI without altering the security setup

Fix Action

Fix / Workaround

🐛 Bug: Chat Trigger Node calls webhook-test endpoint after upgrade to 2.18.5, breaking GUI testing with OAuth2

Code Example

http://localhost:5678/webhook-test/<id>/<sessionId>

---

/webhook-test/<id>/<sessionId>
RAW_BUFFERClick to expand / collapse

Bug Description

🐛 Bug: Chat Trigger Node calls webhook-test endpoint after upgrade to 2.18.5, breaking GUI testing with OAuth2

Description

After upgrading n8n from 2.3.4 to 2.18.5, we encountered an issue with the Chat Trigger Node.

When sending a chat message from the n8n GUI, the workflow now triggers a request to a webhook-test endpoint, for example:

http://localhost:5678/webhook-test/<id>/<sessionId>

This behavior was not present in earlier versions (e.g., 2.3.4) and appears to be a regression.


✅ 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

💥 Impact

In our setup, both:

  • webhook
  • webhook-test

endpoints are protected by external OAuth2 authentication.

Because of this:

  • The unexpected webhook-test call fails authentication
  • It becomes impossible to test workflows via the n8n GUI without altering the security setup

🧪 Environment

  • Previous version: 2.3.4 (working as expected)
  • Current version: 2.18.5 (issue introduced)
  • Setup: Localhost with OAuth2 protection on webhook endpoints

🙏 Request

  • Is this behavior intentional or a bug?
  • Is there a way to disable the webhook-test call for Chat Trigger nodes?

Any guidance or fixes would be appreciated.

<img width="3176" height="2344" alt="Image" src="https://github.com/user-attachments/assets/9d49c904-f5ec-4da5-a1b1-72786a88e98b" />

To Reproduce

🔁 Steps to Reproduce

  1. Install and run n8n version 2.3.4

  2. Create a workflow with a Chat Trigger Node

  3. Open the workflow in the n8n GUI

  4. Send a test chat message via the built-in chat panel
    → ✅ Observe: Workflow executes successfully without any webhook-test request

  5. Upgrade n8n to version 2.18.5

  6. Open the same workflow (with Chat Trigger Node)

  7. Open browser Developer Tools → Network tab

  8. Send a test chat message via the n8n GUI chat panel

  9. Observe the following:

    • A POST request is made to:
      /webhook-test/<id>/<sessionId>
    • The request appears in the Network tab
    • If access token protection is enabled on webhook endpoints, the request fails
  10. Result:

  • Workflow testing via GUI is blocked due to failed authentication on webhook-test endpoint

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

Debug Info

Debug info

core

  • n8nVersion: 2.18.5
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: postgres
  • executionMode: scaling (single-main)
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: a2790908-9d67-4d5e-b66a-f529069f804e

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: database

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-05-04T15:27:31.094Z

Operating System

docker image n8nio/n8n:2.18.5

n8n Version

2.18.5

Node.js Version

v24.14.1

Database

PostgreSQL

Execution mode

main (default)

Hosting

self hosted

extent analysis

TL;DR

The issue can be mitigated by disabling the webhook-test call for Chat Trigger nodes or configuring OAuth2 authentication to allow this specific endpoint.

Guidance

  • Investigate the n8n configuration and code changes between versions 2.3.4 and 2.18.5 to understand the introduction of the webhook-test endpoint call.
  • Check if there are any settings or environment variables in n8n that can be used to disable or configure the webhook-test endpoint call.
  • Consider implementing a temporary workaround by configuring OAuth2 authentication to allow the webhook-test endpoint, if disabling the call is not feasible.
  • Review the n8n documentation and release notes for version 2.18.5 to see if this behavior is intended or a known issue.

Example

No code snippet is provided as the issue is related to the n8n configuration and version changes.

Notes

The exact solution may depend on the specific n8n setup and configuration. It is recommended to test any changes or workarounds in a non-production environment before applying them to the production setup.

Recommendation

Apply a workaround by configuring OAuth2 authentication to allow the webhook-test endpoint, as disabling the call may not be feasible without further investigation into the n8n configuration and code changes.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

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

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Chat Trigger Node incorrectly calls webhook-test endpoint after upgrade to 2.18.5, breaking GUI testing with access token protection [1 comments, 2 participants]