Telegram Trigger not working, but Chat Trigger does (v1.102.4, PM2)

Questions
1

Hi team,

I’m facing an issue with the Telegram Trigger node in n8n.

  • n8n version: 1.102.4
  • Deployment: local (PM2)
  • Trigger: Telegram Trigger (Updates: message)
  • Bot token: classic (not scoped)

Problem:

  • The Telegram bot is active and responds correctly via the Send Telegram Message node.
  • The workflow works fine when using the When Chat Message Received node (on chat trigger).
  • However, the Telegram Trigger does not respond to any new messages.
  • I have tried deleting the webhook via deleteWebhook, then re-running the workflow — no effect.
  • getWebhookInfo shows a valid webhook URL, no error message, and pending_update_count is always 0.

The bot has received /start in private chat, and it’s not part of any group.

Is this a known issue or am I missing something?

Thanks in advance!

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

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

Hi @dicomutiny ,
could you please share the workflow you’re working with? This will help me better understand your setup.

3

Hi @dicomutiny
Here’s what I’d suggest checking:
Make sure Telegram can reach your webhook URL—check if any firewalls, VPNs, or reverse proxies are blocking its servers. Also, Telegram requires a valid HTTPS URL, so ensure your SSL certificate is valid and trusted. Remember, only one webhook can be active for your bot, so make sure no other workflow is using the same bot. Double-check that your Telegram Trigger node is set to listen for the correct message types, like text or reactions. If you’re using a reverse proxy or custom domain, ensure the WEBHOOK_URL environment variable is set correctly in your n8n configuration. If pending_update_count is always 0, it could mean Telegram isn’t sending messages or they’re being delivered to another webhook. Lastly, check the execution tab in your workflow for any errors or missed executions that might help diagnose the issue.

4

Thanks for the answer.
Stopped working after updating the telegram program itself, when bot_father was updated and became a mini application.
On another version of Telegram (previous) everything works, the telegram trigger catches the message.