I got this when I try to create a webhook, why do I need to register a webhook?
{
"code": 404,
"message": "The requested webhook is not registred."
}
Because if none is registered it does not exist and can so not be used.
A test Webhook is only registered in the time between executing a workflow via the UI (when it displays âwaiting for Webhook callâ till the first call gets made.
A production Webhook is only registered when a workflow got activated (via the switch on the top right of the page).
1 Like
Hi Jan, my workflow is activated and I still get this error message. Is there something else Iâm missing?
Error message:
{âcodeâ:404,âmessageâ:âThe requested webhook âGET 2/telegram%20trigger/webhookâ is not registered.â,âstackâ:âResponseError: The requested webhook âGET 2/telegram%20trigger/webhookâ is not registered.\n at ActiveWorkflowRunner.executeWebhook (/usr/local/lib/node_modules/n8n/dist/src/ActiveWorkflowRunner.js:51:19)\n at /usr/local/lib/node_modules/n8n/dist/src/Server.js:672:60\n at Layer.handle [as handle_request] (/usr/local/lib/node_modules/n8n/node_modules/express/lib/router/layer.js:95:5)\n at next (/usr/local/lib/node_modules/n8n/node_modules/express/lib/router/route.js:137:13)\n at Route.dispatch (/usr/local/lib/node_modules/n8n/node_modules/express/lib/router/route.js:112:3)\n at Layer.handle [as handle_request] (/usr/local/lib/node_modules/n8n/node_modules/express/lib/router/layer.js:95:5)\n at /usr/local/lib/node_modules/n8n/node_modules/express/lib/router/index.js:281:22\n at param (/usr/local/lib/node_modules/n8n/node_modules/express/lib/router/index.js:354:14)\n at param (/usr/local/lib/node_modules/n8n/node_modules/express/lib/router/index.js:365:14)\n at Function.process_params (/usr/local/lib/node_modules/n8n/node_modules/express/lib/router/index.js:410:3)â}
Hey @ricardo8c, welcome to the community.
There is a good tutorial that explains the use of the webhook node here Learn how to use webhooks with Mattermost slash commands đŚ | by Tanay Pant | n8n.io. If you do not find the answer there simply get back to us.
1 Like
Ok. I noticed that is mandatory to use the test url before production!
Thanks
1 Like
@ricardo8c Glad, you found the solution. Have fun. Letâs know if you have any further questions.
Hi, I have the same issue, the webhook works on test but even if it is active it say that is not register, any idea?
Welcome to the community @Msaustral!
Are you using the production URL? Because it is different to the test URL.
Hi yes I am, it is not working on production server neither on local machine.
To test I made 2 webhook with different method ( post and get) as you suggest in other post, same issue
Leaved only post or only get, nothing
It is fresh installation with no tunneling
What I mean if you are using the correct URL. If you test (via the UI), you have to use the URL underneath âTestâ (this URL only works for one call after you pressed âExecute Workflowâ and you will see the data in the Editor-UI):
If you have the workflow activate and want to run it in production mode, you have to use the URL underneath âProductionâ (this URL only works if you have the workflow activated and you will not see the data in the Editor-UI).
Hi Jan, as we mention, It does work with the test URL, we activate the workflow and change the URL for the production Webhook and allays get âcodeâ:404,âmessageâ:"The requested webhook is not registered
we try on â
local machine â ters URL works, production donât
production server â ters URL works, production donât
n8n.cluod â does not work test url neither production
we did open a trial account on n8n.cloud, import the work flow and test it with the same result
strange solution:
we create a new workflow, without import it from local machine , insert only a webhook and it works!
we do not know why!
Yes, you mentioned that it works with test but none of your answers made clear that you understood that they are different URLs for test and production. Especially not your last one where I asked specifically about that. For that reason do I have to make sure that this is clear. Because since the existence of n8n did I never come across a case where problems regarding the Webhook got caused by technical issues, it had always to do with some kind of misunderstand how the Webhook Node behaves. But not saying that there is no way that could be the case is just much much less likely.
Anyway great to hear that it works now.
Hi Jan, thank you for your fast response,
To be more specific and clear â YES we do know that production and test have different URL.
Also we hope that you got the issue (bug) that has the app when you import workflow â production webhooks are not register.
Hi Jan, we were unable to do another reply, these are the steps:
-on local machine we made the workflow, test it, save it, activate it
-then export as a file test.json
-then import it as a file on production or cloud
test.json
{
ânameâ: âtestâ,
ânodesâ: [
{
"parameters": {},
"name": "Start",
"type": "n8n-nodes-base.start",
"typeVersion": 1,
"position": [
250,
300
],
"retryOnFail": true,
"maxTries": 5,
"continueOnFail": true
},
{
"parameters": {
"authentication": "basicAuth",
"httpMethod": "POST",
"path": "=bdfc4421-8e5d-4271-b09e-14e21be05c05",
"options": {
"responseData": "\"hola\""
}
},
"name": "Webhook",
"type": "n8n-nodes-base.webhook",
"typeVersion": 1,
"position": [
440,
300
],
"webhookId": "bdfc4421-8e5d-4271-b09e-14e21be05c05",
"credentials": {
"httpBasicAuth": "piwen"
}
}
],
âconnectionsâ: {
"Webhook": {
"main": [
[]
]
}
},
âactiveâ: true,
âsettingsâ: {
"timezone": "America/Santiago",
"executionTimeout": -1,
"errorWorkflow": "2"
},
âidâ: â2â
}
Does not look like it:
- Did export the workflow as file, and imported it into local version (and n8n.cloud), saved the workflow, activated the worfklow and called the URL â All worked fine
- Did select the webhook node, copied it, pasted into local version (and n8n.cloud), saved the workflow, activated the workflow and called the URL â All worked fine
Again is very unlikely that there is a bug. No changes have been made there for a while and nobody else reported any issues. So if there is an issue it must be some edge-case. But to be able to fix it, do we have to be able to reproduce it. So please share the workflow with us which does also not work for you on cloud, that we can see if we can reproduce it there. Thanks.
I too ran into a similar issue
The node is executed and waiting, if i just paste the webhook URL into the browser it works and the node picks it up {âmessageâ:âWorkflow got started.â}
If i send a payload to the same URL i get
Exception: Request failed for https://n8n.xxx.com returned code 404. Truncated server response: {âcodeâ:404,âmessageâ:âThe requested webhook âPOST fb-leads-sheets-owner-contactedâ is not registered.â,âhintâ:"Click the âExecute workflowâ butt⌠(use muteHttpExceptions option to examine full response)
Workflow is executed
I made a new workflow to test and same issue (saved and active and posting to the production url) still get the 404
Existing webhooks in other workflows work fine
OK figured it out my node was set to GET and I was using POST to send data 
1 Like
i have a similar issue, was an imported flow. but I deleted the original webhook and added a new one in case that was the issue but it hasnât helped. Iâm using GET on all places so thatâs not the issue
{"code":404,"message":"The requested webhook \"GET xx-xx-xx-xx-xx\" is not registered.","hint":"The workflow must be active for a production URL to run successfully
code":404,"message":"The requested webhook \"GET xx-xx-xx-xx-xx\" is not registered.","hint":"Click the 'Execute workflow' button on the canvas, then try again
flow is active, test and prod URLs both show the same issues. not sure what else to try?
using the latest version pulled on docker
I had the same issue using POST requests. In my case, I had duplicated a webhook and used the new webhook trigger link in a different context. It only worked when I copied the nodes directly into a brand-new webhook. The new link worked perfectly. The topic is old, but I hope it helps someone.