Alert Integrations & Notification Channels

NorthDuty turns monitoring signals into alerts and delivers them where your team already works. You can route alerts to nine channel types — email, Slack, Microsoft Teams, Discord, Google Chat, custom webhooks, Telegram, SMS, and WhatsApp — and control which signals fire with threshold-based alert rules.

Get Started Free See Solutions

Route alerts to email, Slack, and webhooks so the right people hear first.

Every signal, routed to the right place

Monitoring only helps if the right people hear about a problem quickly. NorthDuty connects each project to the notification channels your team uses, so health, journey, and visual-change signals reach the inbox, chat channel, or phone that gets seen.

Slack, Microsoft Teams, Discord, Google Chat, and custom webhooks are delivered as an HTTP POST to a per-channel webhook URL, so they fit existing channel and automation setups. Telegram delivers through a bot, and SMS and WhatsApp are delivered via Twilio.

Supported notification channels

Nine channel types, grouped by how they deliver.

Email

Direct email notifications for teams that want alerts in the inbox.

Webhook family

Slack, Microsoft Teams, Discord, Google Chat, and custom webhooks — each delivered as an HTTP POST to a per-channel webhook URL.

Messaging apps

Telegram via a bot, plus SMS and WhatsApp delivered through Twilio for alerts that reach a phone.

Custom webhooks

Post alerts to your own endpoint to drive on-call tooling, automations, or internal dashboards.

Decide what fires an alert

Alert rules turn monitoring signals into thresholds before anything is sent to a channel.

Alert Rules

Threshold rules for health, journeys, visual diffs, and SSL

Configure alerts for health score, response time, failed user journeys, visual differences, and SSL expiry, then route them to your connected channels.

NorthDuty alert rules screen showing health score, response time, user journey failure, visual difference, and SSL expiry thresholds. — Alert thresholds for health score, response time, journey failures, visual differences, and SSL expiry.

Why flexible alert routing matters

Different signals deserve different urgency and different channels.

Reach the team where they already work — chat, email, or phone
Route urgent signals to SMS or WhatsApp and routine ones to chat or email
Drive on-call tooling and automations with custom webhooks
Control noise with threshold-based alert rules per signal
Use the same rules across health, journey, and visual-change signals

How to set up integrations

Connect a channel, then point alert rules at it.

1

Add a notification channel

Choose a channel type and provide its destination — a webhook URL for the webhook family, or the details needed for email, Telegram, SMS, or WhatsApp.

2

Define alert rules

Set thresholds for health score, response time, journey failures, visual differences, and SSL expiry.

3

Route rules to channels

Send each rule to the channels that fit its urgency.

4

Tune over time

Adjust thresholds and routing as you learn which signals matter most.

Related NorthDuty Pages

Explore pricing, feature details, solution pages, and related tools connected to this website monitoring use case.

Pricing

NorthDuty pricing for website monitoring: a free plan through $29/mo Starter, Pro, and Business — covering uptime, visual change detection, and user journeys.

Compare pricing plans

Hub

Features

Explore NorthDuty features: website health checks every 5 minutes, screenshot-based visual change detection, and AI-suggested user journey monitoring in one project.

Browse Features

Hub

Solutions

Explore NorthDuty solutions for ecommerce website monitoring, SaaS website monitoring, agency website monitoring, and startup website monitoring.

Browse Solutions

Feature

Alerting

Send NorthDuty alerts to email, Slack, Microsoft Teams, Discord, Google Chat, custom webhooks, Telegram, WhatsApp, and SMS. Route every website health signal to the channels your team already uses.

Explore Alerting

Feature

Status Pages

Publish a public status page, track incidents automatically from alert rules, and schedule maintenance windows — all from NorthDuty project settings.

Explore Status Pages

Feature

Uptime Monitoring

Monitor uptime every 5 minutes by default with HTTP, SSL, DNS, blank-page detection, broken resources, JavaScript errors, and API call tracking.

Explore Uptime Monitoring

Feature

Reports

Generate PDF reports covering website health, user journeys, and UI changes. Download on demand or schedule recurring email delivery.

Explore Reports

Frequently Asked Questions

Answers to common questions about this monitoring feature and when teams should use it.

Which alert channels does NorthDuty support?

Nine channel types: email, Slack, Microsoft Teams, Discord, Google Chat, custom webhooks, Telegram, SMS, and WhatsApp.

How are Slack and Teams alerts delivered?

Slack, Microsoft Teams, Discord, Google Chat, and custom webhooks are all delivered as an HTTP POST to a per-channel webhook URL you configure.

Can I send alerts by SMS or WhatsApp?

Yes. SMS and WhatsApp are delivered via Twilio, and Telegram is delivered through a bot.

Can I control which signals trigger alerts?

Yes. Alert rules let you set thresholds for health score, response time, failed journeys, visual differences, and SSL expiry before anything is sent.

Call To Action

Start monitoring your website with NorthDuty today.

Connect NorthDuty to the channels your team already uses and route every monitoring signal to the right place.

Get Started Free View Pricing

Start on the free plan — add your base URL and monitoring starts in minutes.