Slack Integration

PingSLA posts incident and recovery notifications to Slack channels via incoming webhooks.

Setup

Step 1 — Create a Slack Webhook

1. Go to api.slack.com/apps
2. Click Create New App → From scratch
3. Name: PingSLA Alerts, Workspace: your workspace
4. Go to Incoming Webhooks → toggle On
5. Click Add New Webhook to Workspace
6. Select the target channel
7. Copy the webhook URL:

   https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX

Step 2 — Add to PingSLA

1. Go to Settings → Notification Channels → New Channel
2. Select Slack
3. Paste the webhook URL
4. Optionally, override the channel name
5. Click Test

Notification Format

PingSLA sends Slack Block Kit messages for rich formatting:

DOWN notification:

🔴 *INCIDENT: Production API Health is DOWN*

• *URL:* https://api.yourapp.com/health
• *Reason:* HTTP 503 Service Unavailable
• *Region:* us-east-1
• *Time:* May 18, 2026 14:32 UTC

<https://app.pingsla.com/incidents/inc_xxx|View Incident →>

RECOVERED:

✅ *RECOVERED: Production API Health is UP*

• *Downtime:* 4 minutes 22 seconds
• *Resolved:* May 18, 2026 14:36 UTC

<https://app.pingsla.com/incidents/inc_xxx|View Incident →>

Best Practices

• Create a dedicated #ops-alerts channel for PingSLA notifications
• Use a separate webhook per alert severity (critical in #p1-critical, standard in #ops-alerts)
• Set the channel topic to reference the PingSLA dashboard URL

Rotating the Webhook URL

If you regenerate or delete the Slack app:

1. Create a new webhook in Slack
2. In PingSLA: Settings → Notification Channels → Edit your Slack channel
3. Replace the webhook URL
4. Test the updated channel

Troubleshooting

Issue	Resolution
Webhook returns 404	Webhook was deleted in Slack — regenerate
Webhook returns 403	App was removed from workspace — re-install
No messages appear	Check the webhook is authorized to post to the target channel
Duplicate messages	Verify the channel is attached to only one alert policy per monitor