Pain point · Integrations · Blocks work
Telegram Trigger generates a webhook URL that does not work
1 source thread · first seen 2025-01
Summary
The Telegram Trigger node produces an incorrect URL with a webhook suffix, so Telegram never triggers the workflow, while a general Webhook node works.
- Workaround
- Use the general Webhook node
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“The Telegram Trigger node in n8n generates an incorrect webhook URL, causing it to fail when registered as a Telegram webhook”