How to Set Up Slack Alerts for Website Downtime

Your team is already in Slack. When your site goes down, that's where they need to find out — not in an email that sits unread for 20 minutes.

Here's how to get downtime alerts in Slack in under 3 minutes.

Step 1: Create a Slack incoming webhook

Slack incoming webhooks let external services post messages to a channel.

1. Go to api.slack.com/apps and click Create New App
2. Choose From scratch, name it something like "PoppaPing Alerts", and pick your workspace
3. In the left sidebar, click Incoming Webhooks
4. Toggle Activate Incoming Webhooks to On
5. Click Add New Webhook to Workspace at the bottom
6. Select the channel you want alerts in (e.g. #monitoring) and click Allow
7. Copy the Webhook URL — it looks like https://hooks.slack.com/services/T00000/B00000/XXXX

That URL is all you need.

Step 2: Add the webhook to PoppaPing

1. Log in to PoppaPing and go to Settings
2. Scroll to Alert Channels
3. Select Webhook as the type
4. Add a label like "Slack - #monitoring"
5. Paste the Slack webhook URL
6. Click Add Channel

PoppaPing sends a JSON payload to the webhook URL. Slack will display the alert as a formatted message in your channel.

Step 3: Assign to monitors

By default, new monitors use all alert channels. For existing monitors, edit each one and check the Slack channel under Alert Channels.

Formatting the Slack message

PoppaPing sends a standard webhook payload to Slack. The message will appear as a JSON-formatted notification with the monitor name, URL, error, and status.

If you want richer formatting, you can use a middleware tool like Zapier or n8n to transform the PoppaPing webhook payload into a Slack Block Kit message — but for most teams, the default format gets the job done.

Alternatively, if you want rich embeds out of the box, Discord webhooks get auto-formatted with colors and structured fields. Some teams use a Discord server for ops alerts even if their main communication is in Slack.

Tips for Slack alerting

Use a dedicated channel. Create #monitoring or #site-alerts so downtime notifications don't get lost in #general.

Set channel notification preferences. In Slack, click the channel name → Notifications → Every new message. This ensures you get notified immediately, even if you have other channels muted.

Route by severity. You can create multiple webhook channels — one for #critical-alerts (production monitors) and one for #monitoring (everything else). Assign them to different monitors.

Combine with email. Slack is great for team awareness, but for on-call scenarios you probably want email or PagerDuty too. PoppaPing lets you assign multiple channels to each monitor, so you can alert Slack and email and PagerDuty simultaneously.

Alternative: Slack workflow with PoppaPing webhooks

For more advanced setups, you can use PoppaPing's webhook payload with Slack's Workflow Builder:

1. Create a Slack workflow triggered by a webhook
2. Point PoppaPing's webhook URL to the Slack workflow URL
3. Map the payload fields (monitor name, URL, error) to Slack message blocks
4. Add custom actions like creating a Slack channel for the incident or notifying a user group

This gives you full control over the message format and lets you trigger Slack-native actions from downtime events.

The payload PoppaPing sends

For reference, here's what PoppaPing sends to webhook URLs:

{
  "event": "monitor.down",
  "data": {
    "monitor": {
      "name": "Production API",
      "url": "https://api.example.com/health"
    },
    "error": "HTTP 503 Service Unavailable",
    "regions_down": ["chicago", "miami", "frankfurt"],
    "incident_id": 42
  },
  "timestamp": "2026-02-18T14:32:00Z"
}

And when it recovers:

{
  "event": "monitor.up",
  "data": {
    "monitor": {
      "name": "Production API",
      "url": "https://api.example.com/health"
    },
    "downtime_minutes": 4,
    "incident_id": 42
  },
  "timestamp": "2026-02-18T14:36:00Z"
}

You can use these fields to build custom integrations, auto-create Jira tickets, update Notion databases, or anything else your workflow requires.