Need help with telegram trigger

Hello everyone,
I’m trying to use the Telegram Trigger node in n8n, which I’m running locally using Docker Desktop on Windows. The trigger doesn’t work – Telegram webhooks aren’t being received, and my bot doesn’t respond to messages. When I attempt to activate the trigger, I get the following error in n8n:

Problem running workflow
Bad request – please check your parameters
Telegram Trigger: Bad Request: bad webhook: An HTTPS URL must be provided for webhook

When I check the webhook status using the Telegram Bot API (getWebhookInfo), it shows that “no webhook is currently set”.

Also, in the ngrok logs, I see repeated 404 Not Found errors when Telegram tries to access /webhook.

I have tried using ngrok:

  1. I’m exposing my local n8n instance to the internet using ngrok, which is forwarding it to a ngrok url. https://… .ngrok-free.app → http://localhost:5678

  2. I added this environment variable to the container:

  • WEBHOOK_URL=https://… .ngrok-free.app
  1. I manually set the webhook using:
    https://api.telegram.org/bot/setWebhook?url=https://… .ngrok-free.app/webhook/telegram/

Telegram’s API responds with:
{
“ok”: true,
“result”: true,
“description”: “Webhook was set”
}
But getWebhookInfo still returns:
{
“ok”: true,
“result”: {
“url”: “”,
“has_custom_certificate”: false,
“pending_update_count”: 17,
“allowed_updates”: [“message”]
}
}

In the ngrok console I consistently get:
POST /webhook 404 Not Found

Can someone please help me resolve this issue? (Not with ngrok necessarily)
Thank you

Are you able to reach n8n with that ngrok url youself?

hey @parham you can follow this guide on youtube to correctly setup n8n with ngrok:

if it you solves your problem do not forget mark this response as solution.

No
Shall I keep ngrok’s terminal open?

Thank You
I will reinstall ngrok using the provided YouTube video.
Is ngrok the only method? Or there are easier methods rather than ngrok?

Here is another: npm | n8n Docs

If this response was helpful please mark it as solution.

Thank you for your reply. The YouTube video that you sent earlier completely resolved the issue.

no worries.
keep learning and keep building.