WebCheck notifications are configured per site. The site detail page provides the notification configuration area, where an available plan can add a destination such as a signed webhook or supported messaging destination.
Choose the destination
Open the site detail page and expand Notifications. Select the destination type, give it a recognizable label and provide the destination details requested by the form. WebCheck validates webhook-style URLs and requires the fields needed for messaging destinations.
What can trigger a notification
Monitoring events can include a confirmed incident, recovery, meaningful escalation and certificate or domain-expiry warnings where applicable. A transient failure or ordinary degraded result does not necessarily create an alert immediately.
Keep destinations safe
Use an endpoint you control, protect destination secrets and do not paste credentials into labels or URLs. WebCheck applies URL-safety validation to outbound webhook destinations and does not accept private destinations through the normal configuration path.
Check delivery state
If an alert does not arrive, review the incident and delivery records, confirm the destination remains configured and check the receiving service logs. Notification delivery is separate from the monitoring run itself.