Telegram Trigger issue, on responding to the flow

Questions
1

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

:pushpin: Hi everyone! I could use some help with a Telegram Trigger issue on n8n.cloud.

I have a Telegram-based workflow that had been working reliably for a long time, but then it suddenly stopped responding — no changes were made.

:red_exclamation_mark: The problem:
The Telegram bot is definitely sending data (I checked via getWebhookInfo), and the webhook is correctly set on Telegram’s side. However, the n8n Telegram Trigger node does not react at all — even when the workflow is marked as active. According to getWebhookInfo, Telegram receives a “404 Not Found” error when sending data to n8n.

The trigger node stays in “listening” mode, but nothing ever arrives, and no execution is triggered.

:test_tube: What I’ve tried so far:

  • Recreated the Telegram Trigger node from scratch
  • Re-added and verified the Telegram credentials
  • Manually reset the webhook via setWebhook API
  • Created a fresh new workflow with only the trigger node
  • Tried both Run Once and Active modes
  • Switched browsers and cleared cache
  • Tested with different update types (message, callback_query, etc.)
  • Contacted n8n support → they confirmed the config seems fine on my side

:gear: Context:

  • Using the latest version of Telegram Trigger (v1.2)
  • Hosted on n8n.cloud (not self-hosted)
  • Other webhook-based triggers like HTTP or Slack are working

:bullseye: What I need:
I’m trying to get the Telegram Trigger node to respond again so I can continue building my automation.

If anyone has run into this or has any suggestions on what else to check, I would truly appreciate your help!

2

Hi @Gergely_Jarvas

Make sure there are no other workflows using the same Telegram Trigger with the same bot;

Due to Telegram API limitations, you can use just one Telegram trigger for each bot at a time

It means if you already have an active workflow with a Telegram trigger and then create another one (even just for testing), the active workflow will lose its Telegram webhook connection and stop receiving updates.

Also, try running this telegram request endpoint to check the active Telegram webhooks: