WatchFor
Notifications

Notification channels

Send alerts to email, chat, webhooks and more.

A notification channel is a destination for alerts. WatchFor supports over 25 channel types, so incidents reach people where they already work.

Channel types

Direct

Email

Chat

Slack · Discord · Microsoft Teams · Telegram (setup guide →)

On-call & ITSM

PagerDuty · Opsgenie · Jira · ServiceNow · Zendesk

Developer

Webhook · Zapier · and more

…and others. Webhooks let you integrate anything not on the list — they send a structured JSON payload your system can act on.

System channels

Every organization has a built-in Email channel wired to your account contact details. These are protected — they can't be deleted or renamed by accident, so you always have a working fallback path.

Adding a channel

Open Notification channels

Go to the channels page and click Add channel.

Pick a type

Choose Slack, Discord, PagerDuty, a webhook, etc., and provide its details (a webhook URL, an API key, a phone number…).

Attach contact groups

Decide who the channel reaches by attaching one or more contact groups.

WatchFor flags duplicate channels with a friendly message, so you don't accidentally wire the same destination twice.

Setting up Telegram? It has a dedicated one-minute guide: Telegram alerts — the bot tells you your chat ID itself.

What a notification contains

Alerts are enriched — not just "something broke", but the monitor, the failing condition, a plain-language diagnosis, the confirming locations, and a link straight to the incident. Recovery and administrative resolutions (who resolved it and why) are included too.

Routing — which incidents go to which channels — is configured with routes and can be changed without any restart or downtime.

On this page