Chat Trigger webhook error resolved
Workflows with Chat Triggers and pinned data no longer fail with 'webhook not registered' errors. The fix ensures webhooks always register so chat messages post correctly.
Chat Trigger nodes were failing when workflows had pinned data. The root cause: webhooks weren't being registered in those cases, but the chat SDK always sends POST requests to webhook URLs. This mismatch triggered "webhook not registered" errors whenever a user sent a chat message.
The fix modifies webhook registration logic to always register when a Chat Trigger is present—even with pinned data. Now if a user types in the chat panel, their message flows through the workflow as expected. If Execute Workflow is the trigger instead, pinned data is used normally.
The change is minimal but resolves a real failure mode that was blocking users from testing Chat Trigger workflows in the editor. In the n8n CLI package's workflow execution service, the condition now accounts for active chat sessions alongside pinned data status.
View Original GitHub Description
Summary
When a Chat Trigger node has pinned data, sendi ng a new chat message fails with "webhook not registered". This happens be cause the chat SDK always POSTs to the webhook URL, but webhook registration was skipped when data is pinned.
After the fix:
- If a user types a message in the chat panel, that message will be used in the workflow, ignoring the pinned data and will not throw error.
- If the Chat trigger is the only trigger in the workflow, then Execute Workflow will use the pinned data.
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/NODE-4628/community-issue-chat-trigger-fails-when-workflow-has-multiple-triggers fixes #26491
<!-- Include links to **Linear ticket** or Github issue or Community forum post. Important in order to close *automatically* and provide context to reviewers. https://linear.app/n8n/issue/ --> <!-- Use "closes #<issue-number>", "fixes #<issue-number>", or "resolves #<issue-number>" to automatically close issues when the PR is merged. -->Review / Merge checklist
- PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
- Docs updated or follow-up ticket created.
- Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
- PR Labeled with
Backport to Beta,Backport to Stable, orBackport to v1(if the PR is an urgent fix that needs to be backported)