Hi,
i use a chat trigger (“when chat message received” trigger) on my slef hostet Hostinger N8N VPS. In on e of my workflows, this works well and the node returns output data.
in another workflow, it does not work and the node returns an empty JSON and the error “The requested webhook is not registered”.
I tried with activated and deactivated workflows, but no matter how, the first works, the second doesnt..
Do you have any idea on how to solve this issue?
Thanks! Andi
Describe the problem/error/question
What is the error message (if any)?
Please share your workflow
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
Share the output returned by the last node
Information on your n8n setup
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
1 Like
@andikoler Try moving to a new workflow and adding a new chat trigger node.
Hi @andikoler ,
Compare the chat trigger node in both workflows and see if the webhook urls are identical, if yes, delete the When chat message received node in the broken workflow and add a fresh one, reconnect it and reactivate.
As a general rule on self-hosted n8n: always delete and re add trigger nodes after duplicating a workflow rather than reusing the copy.
Let me know if that resolves it! 
1 Like
Hi @andikoler Welcome! I recommend upgrading/restarting your n8n instance, i was also facing this kind of issue which got resolved when i have restarted my instance.
HI, i am not sure where to find the webhook urls. My node looks like this:
{
“nodes”: [
{
“parameters”: {
“options”: {}
},
“type”: “@n8n/n8n-nodes-langchain.chatTrigger”,
“typeVersion”: 1.4,
“position”: [
-2864,
1200
],
“id”: “b0647b4d-efc2-419e-aff8-5b609b8a5fb4”,
“name”: “When chat message received”,
“webhookId”: “952edd5b-f7a9-4599-b932-1e480958a8dd”
}
],
“connections”: {
“When chat message received”: {
“main”: [
]
}
},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “73ffbb1933b22eda86ea4199837019f89c7f8dac33e9bb18b392eab14efb9223”
}
}
Hey @andikoler , do the same thing for the working workflow, select the chat trigger node, copy the JSON and paste it here. We need to compare the webhookId field in both. If they’re identical that confirms the collision and the fix is just deleting and re adding the trigger node in the broken one.
the funny thing is that in a new workflow where i just add my chat message received trigger and enter a message, it works (means i get a output JSON that includes sessionId and message). If add the rest of the workflow by copy and paste and connect that to the chat trigger, it is not working anymore…
Any ideas?
1 Like
Just copy paste your complete flow and only delete the chat trigger and add that again.
this is the working node (but be aware that that only works as liong as i do not copy the rest of my workflow to it):
{
“nodes”: [
{
“parameters”: {
“options”: {}
},
“type”: “@n8n/n8n-nodes-langchain.chatTrigger”,
“typeVersion”: 1.4,
“position”: [
-12128,
-288
],
“id”: “aa0c2fe3-5a64-4670-9e77-7c49a4a6d85a”,
“name”: “When chat message received”,
“webhookId”: “dbb9bc09-da20-4f7b-af54-4a3d6f409f76”
}
],
“connections”: {},
“pinData”: {},
“meta”: {
“instanceId”: “73ffbb1933b22eda86ea4199837019f89c7f8dac33e9bb18b392eab14efb9223”
}
}
ok i experimented a little and found out that the problem seems to be that I have two seperate Parts in one workflow: One os the RAG Agent and the other one is the datapipeline. if I delete the whole pipeline (which can only be triggerd manually) the agent seems to work. Is that a common thing? It used to work perfectly in the n8n Cloud, but throws the error mentioned above in the self hosted environment…
hey @andikoler, try this
Deactivate the broken workflow, save it, then fully restart your n8n instance, then reactivate the workflow. There’s a known issue where webhook registration can silently fail on activation.
check the issue here: n8n webhook can not be activated · Issue #21565 · n8n-io/n8n · GitHub
Let me know if the n8n instance restart worked !!
What you found is actually the key insight here. When you have two separate flow sections in the same workflow — one being the RAG agent (triggered by chat) and another being the data pipeline (triggered manually) — you can end up with a webhook conflict.
Here’s what’s likely happening:
The Chat Trigger node registers a webhook when the workflow is activated. If your data pipeline section has any nodes that affect the workflow’s activation state (like another trigger node, even if it’s just sitting there), n8n can get confused about which webhook path to register for the chat trigger.
The fix that works:
Split the RAG agent and the data pipeline into two separate workflows. The data pipeline should be its own workflow, triggered manually or on a schedule. The RAG agent stays in its own workflow with just the chat trigger.
This isn’t just a self-hosted quirk — it’s actually a best practice. n8n’s chat trigger has a single webhook per workflow activation, and having two conceptually different processes in one workflow creates unnecessary complexity and this exact kind of ghost registration issue.
Why it worked in cloud but not self-hosted:
n8n Cloud handles workflow state differently and has better cleanup of stale webhook registrations. Self-hosted instances sometimes get a corrupted state in the webhook table when workflows are edited and re-activated repeatedly. The restart/reactivation fix @houda_ben mentioned can clear this, but splitting the workflows permanently prevents it from coming back.
After splitting, try deactivating both workflows, restarting n8n, then activating them separately — and it should stay stable.