Back to blog

Introducing Slack & Discord Notifications

·3 min read
feature-launchintegrationsnotifications

Email is fine. But it's not where you work.

When your API goes down at 2 AM, you're not checking email. You're in Slack, or your team's Discord. By the time you see the email notification, someone's already pinged you in the channel asking what's going on.

We kept hearing the same thing from users: "I love the email alerts, but can you send them to Slack too?" Fair enough.

What we shipped

Chirp now supports webhook integrations for both Slack and Discord. You paste a webhook URL, pick which events you care about, and you're done. Alerts show up in your channel within seconds of something happening.

Two ways to use it:

Page owner integrations let you wire up your team's channels from the settings page. You manage the webhooks, pick which events trigger them, test them with one click, and disable or delete them anytime.

Subscriber webhooks let anyone subscribe to your public status page with a Slack or Discord webhook URL instead of an email address. Same concept as email subscriptions, just a different delivery channel.

What gets sent

Five event types, all optional per integration:

  • Incident created - something broke, here's what we know
  • Incident updated - new info, status change, or message from the team
  • Incident resolved - all clear, here's what happened
  • Monitor down - a monitor stopped responding
  • Monitor recovered - it's back

Each event gets a color-coded message with the status page name, incident details, and a link to the full status page. Slack messages use Block Kit formatting. Discord messages use rich embeds. both look good without any extra setup.

Security stuff

Webhook URLs are a common SSRF vector, so we locked this down hard. Chirp only accepts URLs matching the official Slack (hooks.slack.com/services/...) and Discord (discord.com/api/webhooks/...) patterns. No arbitrary URLs. Validation runs on both client and server.

if a webhook starts failing consistently, Chirp auto-disables it after 5 consecutive failures. You'll see a warning badge in settings with the last error, so you know what happened.

Setting it up

Takes about 30 seconds.

Slack

  1. Open your Slack workspace settings
  2. Go to "Incoming Webhooks" (or create a Slack app with webhook permissions)
  3. Pick a channel and copy the webhook URL
  4. Paste it in Chirp under Settings > Integrations
  5. Hit "Test" to verify it works

Discord

  1. Open your Discord server settings
  2. Go to Integrations > Webhooks
  3. Create a new webhook, pick a channel
  4. Copy the webhook URL
  5. Paste it in Chirp, test, done

Pro feature

Slack and Discord integrations are available on the Pro plan ($9/mo). if you downgrade, your integrations get paused but not deleted. Upgrade again and they're right where you left them.

Subscribers can only use webhook subscriptions on pages owned by Pro users. if the page owner is on Free, the subscribe form only shows the email option.

What's next

this is the first of several notification channels we're planning. we've got the infrastructure in place now for adding more webhook targets, and we're looking at what makes sense next.

if you've got a channel you want us to support, let me know on X. building this based on what people actually need.

Try Chirp free

Status pages, uptime monitoring, and SSL checks. No credit card required.

Get started free