Sign in

Detect a non-functional viber integration

The platform detects that a connected Viber account's token is no longer valid 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 invalid — replace it to resume.

    The health check calls get_account_info with the stored token. EasyCRM returns an authentication failure — the token is no longer valid. Moves the connection to *RequiresReauth*, records the error, and notifies Admins (FR-10).

Other paths

Webhook not set or failing

A send or webhook check finds webhookNotSet or a persistent non-zero status. Surfaces the 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 X-Viber-Content-Signature. The diagnosis panel flags unexpected caller on the webhook endpoint without moving the connection out of *Active* on a single occurrence.

Good to know

  • An 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)