Telegram trigger event doesn't work

I’ve set up my docked n8n instance, created a new telegram bot, added a key and added a telegram trigger on any event (*) to my workflow (i’ve tried a ‘message’ as well)

But it never triggers an event no matter how I tried: Listen for event or Ececute the workflow – there is 0 executions from telegram trigger

I’ve tested simple webhook with juest GET trigger and it works fine.

I’ve checked all the threads here and found no any useful hints. Please help me to investigate.

What is the error message (if any)?

No errors or any other messages

Please share your workflow

it's only one telegram trigger

Share the output returned by the last node

no output

Information on your n8n setup

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

Source Code

When I check telegram API for getWebhookInfo there is an empty url

{"ok":true,"result":{"url":"","has_custom_certificate":false,"pending_update_count":6,"allowed_updates":["message"]}}

UPD: when I start listening the url appears:

{"ok":true,"result":{"url":"https://n8n...(hidden)...host/webhook-test/2931e504-2743-44ae-aada-2a601eaa5b5b/webhook","has_custom_certificate":false,"pending_update_count":6,"last_error_date":1693332689,"last_error_message":"SSL error {error:0A000086:SSL routines::certificate verify failed}","max_connections":40,"ip_address":"194.....184","allowed_updates":["message"]}}

So it appears to be an SSL issue?

This is weird because in my browser it works well

I wish such errors would be displayed in n8n interface

I wish such errors would be displayed in n8n interface

Hi @sbrin, I am sorry to hear you’re having trouble. n8n would (usually) display such errors provided it receives them when registering a webhook.

Telegram specifically is a bit tricky though. Many services allow you to register as many webhooks as needed, but Telegram only allows a single webhook per bot. n8n would register a webhook whenever a workflow using the Telegram trigger node is either activated or manually executed, and Telegram disables other webhooks when this happens without throwing an error.

So you want to make sure you have a valid public URL to which Telegram can send webhooks and also make sure you only have one active workflow using the Telegram trigger at a time (or have multiple Telegram bots and use different credentials in each workflow).

Also make sure to save all executions in your workflow settings. Depending on your global settings, n8n might not save successful executions (meaning the execution list would seem empty, even if everything is working as expected and workflows are executed).

2 Likes

Thanks for the details.

But what about custom SSL certificate? I know Telegram API has an option to provide my own cert through webhook call when we register it. How can we use it with n8n?

That’s not a feature currently supported by n8n I am afraid.

I think your best bet would be to use the generic webhook node in n8n instead of the trigger node, and then manually register the webhook URL through the Telegram API (allowing you to set the certificate value when using setWebhook).

Alternatively you could consider using a trusted SSL certificate from (for example) Let’s Encrypt in which case you wouldn’t have to manually register the certificate with Telegram.

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