Hey,
I somehow cant use the telegram nodes which react to a message. It always tells me something about a bad request and I need a HTPPS URL. In every video online it seemed so easy, I just needed to enter the access token. I would be so thankful for help
hi @Aryan_k
Hope you’re doing well!
This is expected behavior.
Telegram message-based nodes require a public HTTPS webhook.
If you’re running n8n locally, you must expose it via HTTPS (ngrok/Cloudflare) or use n8n Cloud. Just adding the bot token isn’t enough for webhook-based Telegram triggers.
If you need more help, please share the workflow and more details so we can take a closer look.
Thanks for your answer. Hope you’re doing good as well.
I just started with N8N and this was a bit of a bummer. But okay, I’m using it on a hostinger server in a docker container. Then I guess I would install ngrok in another container and use its https domain as webhook URL?
Best,
Aryan
You’re running n8n on a Hostinger server inside Docker. That means you already have a public server, so you don’t need ngrok if you configure HTTPS correctly.
Set up HTTPS directly on your domain
If you have something like:
https://automation.yourdomain.com
Just make sure:
The domain points to your server, n8n is properly exposed (port 5678 via reverse proxy), HTTPS is active (Let’s Encrypt, for example), and n8n knows what the public URL is.
In your n8n container, set:
N8N_HOST=automation.yourdomain.com
N8N_PROTOCOL=https
WEBHOOK_URL=https://automation.yourdomain.com
After that, just use the Telegram Trigger, provide your Bot Token, and the webhook will be created automatically.
This is the most stable and recommended approach for production.
Hi @Aryan_k Welcome!
Please try revoking your access token in the telegram and that would make it work most of the times the access token or the trigger is not configured correctly, let me know if the issue persists, please be aware of such AI generated responses they might harm your system or current n8n setup do not run commands suggested by some spammer , hope this helps.
Hello @Anshul_Namdev,
You mean it should work by just rewoking the access token? Just to be clear.
Thank you for your advise yeah AI is hmmm complicated.
Best,
Aryan
@Aryan_k Try revoking the token and if it does not work just restart your instance and if the issue persists please share your workflow and we will help you out!
you can imagine my workflow as a new telegram get message node. Everything was just set up yesterday. That makes it so weird.
Best
Aryan
hey @Anshul_Namdev , sadky didnt work. Here ist my workflow, censored the important facts
{
“name”: “Telegram Bot Webhook Test”,
“nodes”: [
{
“parameters”: {
“updates”: [
“message”
],
“additionalFields”: {}
},
“type”: “n8n-nodes-base.telegramTrigger”,
“typeVersion”: 1.2,
“position”: [
80,
224
],
“id”: “telegram-trigger-node”,
“name”: “Telegram Trigger”,
“webhookId”: “WEBHOOK_ID_PLACEHOLDER”,
“credentials”: {
“telegramApi”: {
“id”: “CREDENTIAL_ID_PLACEHOLDER”,
“name”: “telegram-bot-credential”
}
}
}
],
“pinData”: {},
“connections”: {},
“active”: false,
“settings”: {
“executionOrder”: “v1”,
“binaryMode”: “separate”,
“availableInMCP”: false
},
“versionId”: “VERSION_PLACEHOLDER”,
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “INSTANCE_ID_REMOVED”
},
“id”: “WORKFLOW_ID_PLACEHOLDER”,
“tags”:
}
Hi @Aryan_k
The workflow is correct and the error is not caused by the node or the token. The problem occurs because the Telegram Trigger requires a webhook with a public HTTPS URL, and n8n is not correctly configured with a valid HTTPS URL.
https://automation.yourdomain.com, with a valid SSL certificate).N8N_HOST=automation.yourdomain.com
N8N_PROTOCOL=https
WEBHOOK_URL=https://automation.yourdomain.com
After this, Telegram will accept the webhook and the node will start receiving messages normally.
@Aryan_k Your workflow JSON is invalid i cannot paste it, in the mean time consider restarting your n8n instance and check that is it the trigger which is not working or the complete SET of telegram nodes or any node which are API enabled Trigger nodes, and let us know. Please be aware of these AI spammers these do not know what they are copy pasting so please before considering any change in configuration review it yourself, hope this helps.
Hey @Anshul_Namdev,
thanks for your help. Maybe it doesn’t work bc I censored it. Can you maybe send me a working json with the node? Would be very thankful for that.
Best,
Aryan
@Aryan_k Did you mean a telegram node trigger? Like for the issue i highly advice consider using different app’s nodes as triggers and if they persistently fails then let me know cause currently just restart your n8n instance and make sure to use a valid telegram access token. Hope this helps.
@Anshul_Namdev i already restarted everything and added a new fresh token from a new bot. Nothings helping here
In order for the Telegram “get message” or trigger nodes to work, n8n must be reachable publicly via a valid HTTPS webhook URL. Therefore, please configure HTTPS, and set your WEBHOOK_URL/host values correctly (or use a service like ngrok/n8n Cloud) so that Telegram can send updates to n8n.
hey guys,
it worked. For not just leaving without telling the answer, I needed an SSL certificate on my n8n
thanks,
best,
Aryan
Oh, that’s great @Aryan_k !
See who helped you and mark the response as the solution, this helps the community and the supporters too 