Sign in

Detect a non-functional telegram integration

The platform detects that a connected Telegram bot's token was revoked or its webhook is failing, and shows the Admin exactly why.

When this happens: The periodic health check runs (FR-15), or an Admin opens the connection's diagnosis panel.

Step by step

  1. 1

    Open the connection and sees Token revoked — replace it to resume.

    The health check calls getMe against the stored token. EasyCRM returns 401 Unauthorized — the token was revoked from @BotFather. Moves the connection to *RequiresReauth*, records the error, and notifies Admins (FR-10).

Other paths

Webhook delivery failing

The health check calls getWebhookInfo and finds a recent last_error_message. Surfaces the webhook error in the diagnosis panel with a Re-register webhook action.

If something goes wrong

Unexpected webhook caller

Repeated inbound calls arrive with an invalid secret token. The diagnosis panel flags unexpected caller on the webhook endpoint without moving the connection out of *Active* on a single occurrence.

Good to know

  • A revoked or invalid token is distinguished from a webhook delivery problem in the diagnosis detail.
  • Admins are notified when a channel connection degrades. (FR-10, FR-15)