Home / Integrations / Slack

Slack integration — notify-only incoming webhook

Route new Feedback DevTools items to a Slack channel through an incoming webhook. Posts title, page, file:line and a link back. Automatic retries with backoff. Notify-only: no threads, no two-way sync.

What it does

Notify-only. When a new feedback item is created, FDT POSTs one Slack message to your incoming webhook. There are no Slash commands, no bot replies, and no reading of channel history.
Incoming webhook only. The sink accepts https://hooks.slack.com/services/… (and the GovSlack host). Generic URLs are rejected.
Fields posted: title, page URL, source file:line when capture mapped it, and a link back to the item in Feedback DevTools.
Retries / backoff. Delivery goes through the routing outbox — transient Slack 429/5xx responses are retried with backoff. Permanent errors (missing service, bad URL) surface on the route.
No threads, no two-way sync. FDT does not create Slack threads, does not mirror replies back into the kanban, and does not update Slack when an item changes status.

How to connect

In Slack, create an Incoming Webhook for the channel that should get alerts and copy the webhook URL.
In the FDT project dashboard, add a route with sink slack and paste that URL.
Submit a test feedback item — you should see one Slack message with title, page, file:line (when available), and a link back.

Honest limits

This is not a Slack app with OAuth scopes, interactive components, or bi-directional sync. If you need tickets in GitHub/Jira with file:line and a local-agent path, use those sinks instead — Slack here is the alert channel.