Telegram trigger

Feature Requests
1

Hi everyone! I’m having trouble getting the Telegram Trigger node to work correctly in n8n, and I’d really appreciate any help or ideas.

I have n8n installed on my own server with a public domain, and the Telegram bot is properly connected with its credentials. The problem is that I can’t receive any messages from the bot — neither in test mode nor in production — and the whole experience is blocked.

Here’s exactly what’s happening:
• When the workflow is deactivated and I click “Test step”, n8n doesn’t detect any messages I send from Telegram.
• It also doesn’t let me switch from “Test URL” to “Production URL” in the node. Even if I click on Production, when I open the node again, it goes back to Test.
• If I activate the workflow, the bot messages do arrive and the execution starts — but in that state, I can’t edit the workflow because it’s active.
• Only when the workflow is active and running can I receive messages, but then I can’t make any changes to the automation.
• I’ve tested with a new bot, new credentials, and even new workflows — nothing works.
• Even after correctly configuring the Telegram API in the credentials section, it still doesn’t work as expected.

Has anyone experienced this? Is there any solution to use the Telegram Trigger as it’s supposed to work — being able to test, edit, and activate without doing everything manually?

Thanks in advance :pray:

  • n8n version: 1.91.2
  • **Running n8n via Portainer-Contabo-traeffic
2

can you share the workflow?
</> icon in the comments editor

3

hello man did you manage to solve this? i have the same problem.

4

Today, all of our workflows using the Telegram Trigger node in n8n have suddenly stopped working.
Nothing is being received from the bot, and when trying to activate workflows, we’re getting errors like:

csharp

КопироватьРедактировать

Workflow could not be activated:
The connection timed out, consider setting the 'Retry on Fail' option in the node settings

or

vbnet

КопироватьРедактировать

The workflow is activated but could not be started.
Click to display error message.

This is affecting all Telegram workflows, and the issue came out of nowhere — everything was working fine before.

We’ve checked Telegram API, tokens, webhooks, and network — no changes were made on our side.

Anyone else experiencing this?
Any known fixes or explanations?