Telegram Trigger Automatically Sets Invalid Webhook URL (.../webhook/.../webhook)

Questions
1

Hi n8n team,

I’m experiencing a persistent issue with the Telegram Trigger node in n8n (version 1.88.0, running in Docker with Cloudflare Tunnel on a custom domain).

Problem description:

Every time I create a Telegram Trigger, the webhook URL is automatically set to:

bash

КопіюватиРедагувати

https://n8n.jarvisst.xyz/webhook/<webhook-id>/webhook

This happens immediately upon node creation, before activating or testing the workflow.

This path is clearly malformed — the expected webhook should be:

bash

КопіюватиРедагувати

https://n8n.jarvisst.xyz/webhook/<webhook-id>

What I’ve tried:

  • Manually editing the JSON of the node — doesn’t work, the URL still resets to the wrong one
  • Deleting and recreating workflows
  • Registering the webhook manually via Telegram Bot API (setWebhook) — successfully set, but ignored by n8n
  • Clean install of n8n via Docker with environment variables:

env

КопіюватиРедагувати

WEBHOOK_URL=https://n8n.jarvisst.xyz
N8N_HOST=n8n.jarvisst.xyz
N8N_PORT=5678
  • Confirmed: REST API works, webhook registration doesn’t emit Webhook registered message
  • Tried with and without test mode, and in both cloudflared + local environments

Request:

  • What causes this malformed webhook to be set automatically?
  • Is there a way to override or prevent it?
  • Should this be treated as a bug in how the Telegram Trigger node registers webhooks?

Thanks in advance — happy to share full config files and logs if needed.

Best regards,

2

Hi @Serj_Temlyaev

If you’re checking the webhook path after creating a Telegram trigger using this link:

https://api.telegram.org/bot<YOUR_TOKEN>/getWebhookInfo

It should look like this:

https://n8n.exmaple.xyz/webhook/<webhook-id>/webhook

image
image587×451 41.2 KB

This looks correct to me, I believe it’s by design, and it’s working as intended btw!