Troubleshooting: Telegram isn't receiving messages
A step-by-step fix when Telegram messages don't reach your Inbox: token, webhook, and a blocked bot.
The problem
You connected a Telegram bot, but your customers' messages aren't reaching the Omnifox Inbox. The cause is almost always one of three: an invalid or expired token, a webhook that isn't registered, or a blocked or misconfigured bot. Work through these steps in order.
Before you start
- You need access to the channel under Channels.
- Keep @BotFather handy in your Telegram.
Step 1 — Verify the token
- Go to Channels and open the Telegram channel (or Connect channel → Telegram if you're recreating it).
- Click Verify Bot Token.
- If you see "Invalid bot token," the token is expired or was revoked. Request a new one from @BotFather with
/token, paste it, and save.
Regenerating a token invalidates the old one: if someone changed it in @BotFather, your channel goes silent until you update the token.
Step 2 — Check the webhook
Telegram delivers messages to Omnifox through a webhook. Omnifox registers it automatically when you save the channel (the Webhook URL field, "auto-registered on save").
- Save the channel again to force the webhook registration.
- To inspect the webhook status directly in Telegram, open this in your browser:
https://api.telegram.org/bot<YOUR_TOKEN>/getWebhookInfo - In the response, the
urlfield must point to the Omnifox domain. Ifurlis empty, the webhook isn't registered—save the channel again. - If
last_error_messageshows an error (a certificate or connection issue, for example), note it for support.
Common cause: using the same bot in another tool. Telegram allows only one webhook per bot; if another platform registered its own, it overwrites Omnifox's and messages stop arriving. Use a token/bot dedicated to Omnifox.
Step 3 — Is the bot blocked or missing privacy settings?
- If you or the customer blocked the bot, Telegram won't deliver messages. Open the chat with the bot, tap its name, and choose Unblock.
- In groups, by default the bot only sees messages that mention it or that are commands. If you expect to capture everything in a group, disable the bot's Group Privacy in @BotFather (
/setprivacy → Disable) and re-add the bot to the group. - Make sure the customer has started the conversation with
/startat least once; a bot can't message someone who has never written to it.
Final check
Send a message to the bot from another Telegram account. It should appear in the Inbox within seconds. If it does, the channel is working.
If it still doesn't work
- Confirm the channel is active (not paused) under Channels.
- Make sure no other integration is running with the same token.
- Contact support with the
getWebhookInfooutput.
Tip: store the token somewhere safe and don't share it; anyone who has it can hijack your bot's webhook.
Related articles
Related articles
-
WhatsApp (Meta) error codes: what they mean and what to do
A table of the most common Meta error codes when sending on WhatsApp (131026, 131047, 131049, 130497, 141006, 131031, 131056, 132000, 190, 368…) and how to fix each one.
-
How to connect Telegram
Connect a Telegram bot to your Omnifox inbox in minutes using BotFather.
-
Instagram and Facebook comments: reply and moderate from Omnifox
See and answer comments on your Facebook and Instagram posts and ads, publicly or privately, and set up automatic replies.
-
Sending and receiving videos on each channel: formats and size limits
Which videos you can send and receive on WhatsApp, Instagram, Messenger, Telegram, web chat and email, the real size limits, and what to do with a large video.
-
Move from WhatsApp QR to Coexistence or Cloud API
Once you're done testing with the QR code, move your number to the official connection: no caps, with templates and broadcasts, and no volume-based ban risk.