Having trouble getting the Telegram Trigger node to work

[HiGu]

Hello n8n community !

I’m having trouble getting the Telegram Trigger node to work in my n8n workflow. I’m running n8n on my local machine for testing, using ngrok for a public tunnel. I’ve carefully followed the n8n documentation and troubleshooting steps, but my Telegram Trigger node is not receiving any events, even though the workflow activates successfully.

Here’s what I’ve done:

• Verified Telegram Bot: I’ve confirmed that my Telegram bot is working correctly. Privacy mode is disabled, and I can successfully interact with the bot using the Telegram API.

• ngrok Tunnel Active: My ngrok tunnel is running, and I’ve set the baseUrl in my config.json file to match the ngrok URL:

{
  
  "encryptionKey": "********", 
  "tunnelSubdomain": "******************",
  "baseUrl": "https://[my-ngrok-subdomain].ngrok-free.app/webhook"
}

• Webhook URL Confirmed: The “Webhook URL” in my Telegram Trigger node settings is correct and includes the ngrok URL, /webhook/, and the unique webhook ID.

• Firewall Rules: I’ve added firewall rules to allow n8n through my local firewall.

• Isolated the Trigger Node: I’ve created a minimal workflow with only the Telegram Trigger node, and the issue persists.

Crucially, I have successfully tested webhook delivery using ngrok and a separate Express.js server. I can confirm that Telegram is able to send webhook events to my ngrok URL without any problems. This indicates that the issue lies within n8n’s handling of the webhook.

I’ve spent a considerable amount of time troubleshooting this, but I’m unable to pinpoint the cause within n8n. I would greatly appreciate your assistance in resolving this issue.

n8n Version: 1.53.2 (self-hosted)

• Database (default: SQLite):
• Running n8n via (desktop app):
• Operating system: Windows11 Pro

Thank you for your time and support!

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[Jon]

Hey @HiGu,

Welcome to the community

Can you provide some information on the actual error you are seeing? I have just given a Telegram bot a quick test and it is working as expected for me.

[HiGu]

Hi Jon, Thank you for your response!
This is the error occurred when I tried to activate the workflow.

if you need something else please let me know.
Thank you.

[Smacktur]

Hi! I have a similar problem. I have access to the network. Version n8n: 1.54.3. Linux. Self-hosted. Docker.

UPD:
This topic helped me, but still have a problem getting the data =(

Telegram triggers dont work

@Jon Hi! Can you tell me what else the problem could be? I added the command “start --tunnel” to docker-compose.yml and the module started listening. But the trigger doesn’t work even for Production URLs https://api.telegram.org/botХХХХХХХХ/setWebhook?url=https://dvov7cjeoz5sqtuoty60fnve.hooks.n8n.cloud/webhook/ХХХХХХХ/webhook [image] https://api.telegram.org/botХХХХХХХХ/getWebhookInfo [image] [image] [image] [image]

[Jon]

Hey @HiGu,

Looking at the error coming back from Telegram you likely don’t have the WEBHOOK_URL environment option set to use HTTPS which is a requirement for Telegram.

[HiGu]

Thank you so much for your support.
Now it is working.

[brauliodiasribeiro]

I have a problem with Telegram and I believe it may be the Nginx Proxy Manager.

My installation is self-hosted.
I have the WEBHOOK_URL with my website “https://n8n.mysite.com”
In Nginx Proxy Manager I have a valid certificate and I needed to configure it to work on my domain. Here it is:

location / {
proxy_pass http://192.168.10.254:5678;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “Upgrade”;
proxy_set_header Host $host;
chunked_transfer_encoding off;
proxy_buffering off;
proxy_cache off;
}

I don’t receive a message in the Telegram trigger, and when I click to activate flow, this error appears too.

Workflow could not be activated:
Can’t connect to n8n.