Slack
Monitor Slack event notification delivery and logs.
This page covers Block Kit message format, send history, and delivery logs for Slack event notifications. Open Slack history and Slack delivery logs in the admin console. For OAuth setup and admin controls, see Slack integrations. For how visitors subscribe on /subscribe, see Slack subscriptions.
When an event with Notifications enabled triggers a delivery, matching verified Slack subscribers receive a message via the Slack API describing the event at send time. For incidents and maintenance, the message includes an Impact Analysis section after the description when that field is set (before affected components).
Description, impact analysis, and timeline messages keep the formatting you author in the event editor: bold, italic, strikethrough, inline code, links, and bullet or numbered lists.
For how Visibility and subscription toggles affect delivery across channels, see Notifications overview — FAQ. Turning the dashboard Subscriptions Slack toggle off hides public sign-up; existing verified channels still receive deliveries.
Monthly integration message limit
Outbound webhook, Teams, Google Chat, and Slack deliveries share an organization monthly integration message limit (UTC calendar month). Usage appears on Overview and integration or notification screens.
- When the limit is reached, further deliveries are skipped (logged as skipped for quota) and are not retried.
- Event saves always succeed — the limit applies only to asynchronous outbound delivery.
Send history
Slack history shows a UTC calendar-month bar graph of event notification Slack deliveries per day. Navigate 13 months of history with previous/next month controls. Counts match the event-notification portion of your combined integration delivery quota (history is tracked per channel). All bucketing uses UTC calendar days and months.
Delivery logs
Slack delivery logs list individual delivery attempts. Each row includes:
| Field | Meaning |
|---|---|
| Channel | Human-readable #channel · workspace label |
| Status | Aggregate outcome — Accepted, Failed, or Skipped (see below) |
| HTTP status | Slack API response code when applicable |
| Event / dashboard | Related event and dashboard when applicable |
| Error | Short client-side reason on failures |
Open a row for request and response bodies (may be truncated). Logs are retained for 30 days. Bot tokens are never logged or returned.
Each log includes a delivery timeline with one step — integration delivery is a single HTTP round-trip. Status reflects the Slack API response, not delivery inside the Slack client.
Status values
| Status | Meaning |
|---|---|
| Queued | Delivery job accepted |
| Accepted | Slack API returned success |
| Failed | HTTP or network failure |
| Skipped (suppressed) | Channel is on the suppression list — no API call. Clear on Slack suppression or see Suppression. |
| Skipped (quota) | Monthly integration message limit reached |
| Skipped (feature) | Integrations entitlement not available at send time |
Delivery timeline
| Timeline step | When it appears |
|---|---|
| Endpoint accepted | Slack API success |
| Endpoint rejected | Slack API error response |
| Request failed | Network error before a response |
| Not attempted | Suppressed, quota, or feature skip — no API call |