Telegram node trigger does not work

Questions
1

Telegram trigger not working

Error:
brave_rZjYspv35U
brave_rZjYspv35U327×201 11.3 KB

Bad request - please check your parameters

Telegram Trigger: Bad Request: bad webhook: An HTTPS URL must be provided for webhook

My n8n setup

  • n8n version: 1.111.0
  • Database: default
  • Running n8n via : Docker
  • Operating system: Windows 11
2

Here are some few information that can help you out on the issue your facing

  1. Verify your webhook URL(if it has a unique id at its end)

2.You might have Localhost issue, Telegram will reject it because it is not publicly accessible such as http://localhost/ or http://(your ip)

3.Confirm if n8n is exposed with HTTPS since your running in Docker

3

The error message you’re seeing is very clear:

Root Issue:
Your Telegram trigger is failing because it expects a secure HTTPS webhook URL, but the URL you provided is not valid. Telegram requires only HTTPS endpoints (no HTTP, no local localhost addresses, no IP without SSL).

How to Fix It

1. Use a Proper HTTPS URL

  • If you’re testing locally (e.g., http://localhost:5678/webhook), Telegram cannot reach it.

  • You need to expose your n8n instance with a public HTTPS URL:

    • Use a tunneling service like ngrok, Cloudflare Tunnel, or LocalTunnel.
    • Example: https://your-subdomain.ngrok.io/webhook/telegram

2. Configure the Telegram Trigger Node

  • In the n8n Telegram Trigger node, check the Webhook URL setting.
  • Make sure it is pointing to your secure domain (e.g., https://my-n8n-server.com/webhook/telegram).
  • Ensure your SSL certificate is valid (not self-signed unless proxied).

3. Update Your Bot Settings

  • Use the Telegram Bot API to set the correct webhook:

    https://api.telegram.org/bot<YOUR_BOT_TOKEN>/setWebhook?url=https://yourdomain.com/webhook/telegram

  • Replace <YOUR_BOT_TOKEN> and yourdomain.com with your actual values.

4. Test the Webhook

  • Send a message to your Telegram bot.
  • Check n8n logs or execution history to confirm the workflow is triggered.
4

So how do I make trigger point to my localtunnel

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.