Slack
Slug: slack
Provider: Slack Incoming Webhooks
Inbound ACK: No — users must ACK via the web dashboard
How it works
PSAPLink posts an incident alert as a Slack Block Kit message to a channel via an Incoming Webhook URL. The message includes priority, incident type, location, and a web dashboard link.
Configuration schema
| Field | Type | Required | Description |
|---|---|---|---|
webhook_url | string | Yes | Slack Incoming Webhook URL. Must start with https://hooks.slack.com/. |
username | string | No | Bot display name shown in Slack (default: "PSAPLink"). |
Create a Slack Incoming Webhook
- In your Slack workspace, go to Apps → search Incoming WebHooks → Add to Slack.
- Select the channel to post to.
- Copy the Webhook URL (
https://hooks.slack.com/services/T.../B.../...).
Create a channel
POST /api/v1/transport-channels
Authorization: Bearer <token>
Content-Type: application/json
{
"transport_type_slug": "slack",
"name": "Operations Slack",
"config": {
"webhook_url": "https://hooks.slack.com/services/T.../B.../...",
"username": "PSAPLink Alerts"
}
}
Test the channel
POST /api/v1/transport-channels/{id}/test
Authorization: Bearer <token>
Limitations
- No inbound ACK. Users acknowledge via the PSAPLink web dashboard only.
- Slack rate-limits Incoming Webhooks to 1 message per second per channel.
- If the Slack workspace revokes the webhook, notifications will be recorded as delivery failures. Retest after any workspace reconfiguration.