← Back to help centre

Notifications

Setting up WebCheck notifications

Configure WebCheck notification destinations and understand which monitoring events can produce alerts.

WebCheck sends email to the address on your Account profile. A Generic webhook can receive incident-open and recovery alerts. Certificate and domain-expiry warning events can also be sent to enabled Generic webhook, Discord and Telegram destinations.

Choose the destination

Open the site detail page and expand Notifications, then select Configure. Choose a channel, give it a label and enter the destination details. Telegram requires a bot token and chat ID. For incident-open and recovery alerts, choose whether to notify immediately or after 5, 10, 30 or 60 minutes. This is a site-level delay; it does not apply to certificate or domain-expiry warnings.

What can trigger a notification

WebCheck sends incident-open and recovery alerts after the target's failure or recovery threshold is met. A transient failure or ordinary Degraded result does not necessarily open an incident. Certificate and domain-expiry warnings are separate check events and do not wait for the incident notification delay.

Keep destinations safe

Use a destination you control and protect its secrets. WebCheck applies URL-safety validation to outbound webhook destinations and rejects private or restricted addresses. Never put tokens or passwords in a label or URL.

Check delivery state

The site detail page does not show notification delivery records. If an alert does not arrive, confirm the destination is enabled, check the Account email address or messaging configuration, and review the receiving service's logs. Delivery attempts are separate from the check result; see How WebCheck notification retries work and Why WebCheck alerts may be delayed.