Telegram bot webhook in Make.com
Updated 2026-08-01
Telegram webhooks are a high-traffic Make.com topic. Messages never reach the scenario, or setup worked once and then went silent. Most failures are URL, exclusive webhook mode, or a scenario that is not listening — not a bad Telegram module mapping.
Setup checks
The webhook URL Make shows must be the one registered with Telegram. Recreating the scenario changes the URL; old BotFather / setWebhook calls keep posting into nowhere.
Telegram allows one webhook per bot. If another tool or a local getUpdates poller holds the webhook, Make will not receive updates.
The scenario must be enabled. Instant triggers do not fill while the scenario is off.
When you have an error string
Timeouts, 401, or errors on modules after the Telegram trigger are different problems. Paste the exact log into the free diagnosis instead of assuming "webhook is dead" when a later module failed validation.
Paste the error for a sourced diagnosis
If you still have the execution log, use the free tool — Make's docs only, every claim linked, or an honest refusal when coverage is missing.
Example you can try: Telegram webhook in Make is not receiving messages. The Watch updates module stays empty.
Official Make documentation
FAQ
Can I use getUpdates and a webhook together?
No — Telegram treats them as conflicting modes for the same bot. Pick webhook (Make instant trigger) or polling, not both.
Related guides
- Make.com webhook not receiving data
- Incomplete executions in Make.com
- Why your Make.com scenario suddenly stopped working
Eviverse is independent and not affiliated with Make. These guides are original explanations with links to Make's public Help Center — not republished documentation.