So to make things a bit easier, What happens if you use a normal Webhook node? I can’t see the images properly of what the UI is displaying but I would expect the test URL to be https://app.n8nhost/test/xxxxx and the production url to be https://api.n8nhost/main/xxxx
So the question then is what part isn’t working, The main url would only be on the webhook workers so there could be a routing issue if you are redirecting them to the main instance and the test webhook should go to the main instance.
If you start with a webhook node it might be easier to debug and work out what is going on.
I read the first message, I couldn’t see the URLs in the image to work out what was being set. In theory a normal webhook should work the same way as the Telegram webhook unless the display value is correct and the webhook we send to Telegram is wrong for some reason.
Maybe that is what you were saying… If that is the case we would have to check the code for the node to check what we are sending.
Did this work on a previous version of n8n for you?
I do indeed, So it sounds like the issue might not be version related and instead linked to config, Out of interest what gets sent if you activate the workflow does that then use the correct address and everything works as expected?
I will do some local testing next week to see if I can find any internal issues with it.
Yes, when I activate it, everything works correctly.
I’ve tried replacing the telegram trigger with a webhook by myself by setting the address of this webhook in the telegram bot api - but having any other telegram module in the workflow automatically changes the url of this webhook to incorrect again - when I start testing.