Slack integration
Website monitoring alerts in your Slack channels
When a client site goes down, the alert lands in the channel your team already watches: monitor name, what failed, and a link to the incident. Set up with one incoming webhook.
Sentinel → Slack
Why Slack alerts
Alerts belong where your team already looks
An email about downtime sits unread in an inbox. A Slack message lands in the channel your team has open all day, where somebody claims it, threads the fix, and everyone sees it resolve. For an agency, a shared #client-alerts channel also becomes a running record of what happened and who handled it.
The trap with chat alerts is volume: route everything to one channel and it becomes noise nobody reads. Sentinel routes by severity, so the channel that pages people carries outages only, and the housekeeping notices go somewhere quieter.
- Set up with a standard Slack incoming webhook, no app install
- Choose which severities reach Slack: critical, warning, info
- Override the routing per monitor for staging or low-priority sites
- Covers uptime, SSL, DNS, keyword, heartbeat and cron checks
SentinelAPP11:24
clientbakery.com SSL expires in 14 days
Renew before Aug 17 to avoid browser warnings
SentinelAPP12:51
acmestudio.co is down
Connection timeout · detected from Ashburn
View incident →
SentinelAPP12:57
acmestudio.co is back online
Down for 6 minutes
Features
Everything Slack alerting should do
One webhook, every monitor
Paste a Slack incoming webhook URL once and every monitor can alert through it. No per-channel apps to install or bots to invite.
Severity routing
Decide which severities reach Slack: critical outages, warnings like an expiring certificate, or info notices when a site recovers. Each tier is a checkbox.
Rich incident messages
Alerts arrive with the monitor name, what failed, the region that saw it, and a link back to the incident, not a bare URL you have to decode.
Per-monitor overrides
A staging site does not deserve the same channel as production. Override the routing on any monitor without touching your account defaults.
Quiet hours
Suppress non-critical Slack noise overnight while critical alerts still get through. Your team wakes up for outages, not for recoveries.
Test before you trust it
Send a test notification through every configured channel from the monitor's notifications page, so you know Slack is wired up before an outage proves it.
How do I connect Sentinel to Slack?
Create an incoming webhook in your Slack workspace, paste the URL into your Sentinel profile settings, and save. Every alert type can then route to Slack. The whole setup takes about two minutes.
Which plans include Slack alerts?
Slack notifications are included on the Starter plan and above. The free plan includes email alerts.
Can I send different alerts to different channels?
Each Sentinel account connects one webhook, which posts to the channel you chose when creating it. Severity routing controls what reaches that channel, and per-monitor settings let you exclude noisy monitors entirely. Many teams create a dedicated #alerts channel for exactly this.
What does a Slack alert contain?
The monitor name, what failed and why, the severity, the region that detected it, and a link to the incident in Sentinel. Recovery messages follow in the same channel when the check passes again.
Will Slack alerts wake me up for minor issues?
Only if you ask them to. Severity routing means you can send critical outages to Slack while keeping warnings and recovery notices to email, and quiet hours suppress non-critical notifications during the window you set.
Put downtime in front of your team
Connect Slack in two minutes and stop finding out about outages from clients.
No card for the free plan · 14-day trial on paid plans · Cancel anytime