Alerts and integrations
Route alerts to Slack, Telegram, Google Chat, Discord, webhooks, or email. Every delivery attempt is tracked — see whether the request was accepted by the provider.
Hosted in the EU
GDPR-friendly by design
Core monitoring data stays in the EU
01
An incident opens, and the monitor's notification channels are alerted
02
Each channel fans out to email recipients and any number of integrations
03
One alert when the incident opens, one when it resolves — never a repeat for the same incident
04
Every delivery attempt is recorded, including the provider's response
Notification channels
- A notification channel is the layer between a monitor and the places alerts are sent.
- A channel can include email recipients and multiple integrations.
- The same monitor can notify the channels assigned to it.
Alert triggers
- DOWN alerts are sent when an incident is opened.
- RECOVERY alerts are sent when the incident is resolved.
- Recovery alerts can be disabled per channel when a team only wants failure notifications.
One alert per incident
- Alerts are tied to incidents, so an open incident is announced once and not re-sent on every failed check.
- Alerts are processed asynchronously, so there can be a short delay between an incident event and notification delivery.
- Delivery order usually follows event order; treat alerts as near-real-time signals.
Delivery reliability
- Delivery attempts are tracked so failed notifications can be inspected.
- If an integration rejects a request, WatchCat records the failure instead of hiding it.
- Each attempt is stored with its outcome, HTTP status, and error, so a missing alert can be traced to the provider that refused it.
Why it matters
Alerts you can audit
- One notification cycle when an incident opens, one when it resolves — no repeated alerts for the same incident
- Every delivery attempt is logged — see whether the provider accepted the request, not just that it was sent
- Recovery alerts fire automatically when the service comes back — no manual close needed
Destinations
Integrations
Alerts leave the EU only through the providers you choose, and only once you configure them.
How notification channels work-
Slack
-
Discord
-
Telegram
-
Google Chat
- Webhooks
Use cases
Typical use cases
- A Slack channel that gets DOWN and RECOVERY, and a management email list that only wants DOWN
- A webhook into your own tooling that opens a ticket for every incident
- A Telegram group for a two-person team that lives on their phones
Start monitoring for free
5 monitors free · no credit card required