--- title: Alerting Integrations: Slack, Discord & More description: Alerting integrations by WatchFor. Send enriched, actionable alerts to email, Slack, Telegram, Discord, PagerDuty, Opsgenie, webhooks and 16 channels in total — with smart routing you can change without a restart. Free plan available. canonical: https://watchfor.io/alerting-integrations --- # Alerting Integrations for Every Tool Your Team Uses Send enriched, actionable alerts to the places your team already works — email, Slack, Telegram, Discord, PagerDuty, Opsgenie, Teams, ntfy and webhooks, 16 channels today with more rolling out — and route the right incidents to the right people without restarts. [Get started for free](/auth/sign-up)[View pricing](/pricing) ## Alerts That Reach the Right People, Everywhere A growing channel lineup, smart routing, zero noise ### Growing Channel Lineup Live today: email, Slack, Telegram, Discord, PagerDuty, Opsgenie, Microsoft Teams, Google Chat, Mattermost, Rocket.Chat, ntfy, Gotify, Pushover, Pushbullet, Zapier and webhooks. Rolling out next: SMS, Jira and more. ### Chat, On-Call & ITSM Slack, Discord and Teams for chat, PagerDuty and Opsgenie for paging, webhooks and Zapier to plug into anything — with built-in on-call schedules and escalations. SMS and ticketing integrations are on the way. ### Webhooks for Anything Webhooks send a structured JSON payload your system can act on, so you can integrate anything not on the list — including Zapier. ### Enriched, Actionable Alerts Not just 'something broke' — the monitor, the failing condition, a plain-language diagnosis, the confirming locations, and a link straight to the incident. ### Smart Routing, No Restarts Routes decide which incidents go to which channels, and you can change routing live — with no restart and no downtime. ### Contact Groups Decide who each channel reaches by attaching one or more contact groups, so the right people are notified for the right things. ### Protected Fallback Channels A built-in Email channel is wired to your account and protected, so you always have a working fallback path that can't be deleted by accident. ### Duplicate Detection WatchFor flags duplicate channels with a friendly warning, so you never accidentally wire the same destination twice. ## Why Route Alerts Through WatchFor? An alert is only useful if it reaches the right person, in the right place, with enough context to act. WatchFor delivers to 16 channels today — email, Slack, Telegram, Discord, PagerDuty, Opsgenie, Teams, ntfy, push apps and webhooks — with SMS and ITSM integrations rolling out, and every alert is enriched with the monitor, the diagnosis, the confirming locations and a direct link to the incident. Routing decides who hears about what, and you can change it live without a restart. Protected fallback channels mean you're never left without a path. [Start monitoring now](/auth/sign-up) Reach people where they work — email, chat & webhooks Email, Slack, Telegram, Discord, PagerDuty & webhooks + more Webhooks (and Zapier) for anything custom Enriched alerts with diagnosis and a link to the incident Route the right incidents to the right people Change routing live — no restart, no downtime Contact groups control exactly who gets reached Protected built-in Email fallback channel ## How Alerting Integrations Work Add a channel, attach who it reaches, route incidents 1 ### Add a Channel Pick a type — Slack, Discord, a webhook, and so on — and provide its details, such as a webhook URL or a phone number. 2 ### Attach Contact Groups Decide who the channel reaches by attaching one or more contact groups. 3 ### Set Routes Configure which incidents go to which channels with routes — by severity, monitor, and more. 4 ### Get Enriched Alerts Incidents reach the right people with full context, plus recovery notifications. Adjust routing anytime, live. ## Alerting Integration Use Cases However your team likes to be paged ### On-Call Paging Page whoever is on call through PagerDuty, Opsgenie or their personal methods (Telegram, Pushover, ntfy, Gotify, Pushbullet) — with full context, escalation levels and a link straight to the incident. On-call schedules are built in. ### Team Chat Alerts Drop alerts into the Slack or Discord channels your team already watches, so problems surface where people are looking. ### ITSM & Ticketing Feed incidents into your ticketing flow today with the signed webhook payload or Zapier; native Jira, ServiceNow and Zendesk channels are on the way. ### Custom Automation Use webhooks (or Zapier) to trigger your own systems — auto-remediation, dashboards, on-call schedules — from a structured incident payload. ## Frequently Asked Questions Everything you need to know about alerting integrations Which notification channels does WatchFor support? 16 channels live today: email, Slack, Discord, Telegram, Microsoft Teams, Google Chat, Mattermost, Rocket.Chat, ntfy, Gotify, Pushover, Pushbullet, PagerDuty, Opsgenie, Zapier and signed webhooks. SMS and ITSM channels (Jira, ServiceNow, Zendesk) are being enabled next. Can I use webhooks for tools that aren't on the list? What's actually in a notification? How does routing work? What are contact groups? Do I always have a working fallback? Will I get duplicate or noisy alerts? Do I get recovery notifications? ## From our blog Guides, deep-dives, and best practices from the WatchFor team [Reliability ### Alert Fatigue: why your team stopped reading alerts (and how to fix it) Jun 25, 2026·5 min readRead article](/blog/alert-fatigue)[Reliability ### On-Call Best Practices: a rotation that doesn't burn people out May 27, 2026·4 min readRead article](/blog/on-call-best-practices)[Monitoring ### Webhooks 101: what they are and how to use them Apr 18, 2026·3 min readRead article](/blog/webhooks-101) ## Ready to Get Alerts Where You Work? Join the teams who route enriched, actionable alerts to the tools they already use. Get started in minutes with our free plan — no credit card required. [Get started for free](/auth/sign-up)[View documentation](/docs/notifications) --- Canonical page: https://watchfor.io/alerting-integrations · Site guide: https://watchfor.io/llms.txt