Notification setup for web monitoring
How to match notification channels to urgency and avoid alert fatigue across email, SMS, Slack, and webhook routes.
A monitor fires; the notification has to land somewhere a human will actually see it. Email is the universal default — and the easiest channel to start ignoring. SMS gets through but burns out fast if overused. Slack works for teams. Webhooks unlock integrations. This guide covers when to use which, and how to set them up without flooding yourself.
Match the channel to the urgency
High-urgency, action-required-now alerts (site down, limited-stock deal): SMS or PagerDuty. Daily-awareness alerts (competitor publishes a blog post, daily price update): email or Slack. Background tracking with no immediate action needed: dashboard-only or weekly digest. The mistake is using SMS for everything — by week two, the SMS feed is unreadable.
Email notification setup
Email is the default channel for every monitor. To avoid flooding the inbox: use rules in your email client to route monitor alerts to a folder. For shared monitoring (team inbox), set up a distribution list rather than sending to one person's inbox.
SMS notification setup
SMS works for the 3–5 monitors per user where speed actually matters — limited-stock deals, site outages, high-stakes regulatory alerts. Adding SMS to every monitor produces an unreadable feed within a week. Be selective.
Slack webhook setup
Most teams use Slack. The webhook posts alerts into a channel with the change details and a link back. Conventions that work: one channel per monitor category (#price-monitors, #competitor-intel, #uptime-alerts), not one channel for everything.
Custom webhook setup
Webhooks unlock integration with anything that accepts HTTP POST — your own internal tools, Zapier, Make, n8n, PagerDuty, Microsoft Teams, Discord. The webhook payload includes the monitor ID, the change details, and a link. Useful for routing alerts into a docketing system, a ticketing tool, or a custom dashboard.
Preventing alert fatigue
Every team eventually hits the point where alerts become noise. The signals: people stop responding to Slack pings, the email folder gets ignored, on-call complains about unnecessary pages. Fixes: tighten the criteria (most alerts shouldn't be cosmetic), route lower-urgency alerts to dashboards instead of channels, batch low-priority alerts into a daily digest, and review the alert volume monthly.
Related
Guide
Writing effective monitoring criteria
How to phrase plain-English criteria so monitors catch what you want and stay quiet about what you don't.
Read moreSolution
Website uptime monitoring
Multi-region health checks at one-minute intervals. When the site goes down, the on-call engineer gets paged before the support tickets pile up.
Read moreSolution
Competitor monitoring and competitive intelligence
Catch competitor product launches, pricing changes, hiring shifts, and content publishes the moment they happen — not in next month's competitive review.
Read moreTry it on the page you want to monitor
Free trial. No credit card. Paste a URL, write a criterion, get alerts.
Start free trial