Slack
Paste an incoming-webhook URL and your feedback arrives in Slack — optionally one channel per board.
Slack routes send your board's activity into a channel. There is no app to install and nothing to approve: you create an incoming webhook in Slack and paste the URL.
Pro plan or above. Open Integrations in your workspace.
Get a URL from Slack
In Slack, create an app for your workspace, turn on Incoming Webhooks, and
add one for the channel you want. Slack gives you a URL that looks like
https://hooks.slack.com/services/T…/B…/….
That URL is a credential for that channel. Anyone holding it can post there.
Add the route
Press Route to Slack, paste the URL, and name the channel so you can tell your routes apart later.
Leave the board empty and every board sends to that channel. Pick a board and only that board does.
One channel for everything is the reason integrations get switched off in week two. If you run more than one board, route each to the channel the team that owns it already reads.
What arrives
| Event | When |
|---|---|
post.created | Somebody posts on a board. |
post.status_changed | A post moves to a different status. |
post.merged | Two posts are merged. |
comment.created | Somebody comments. Internal comments never leave. |
vote.created | Somebody votes. |
changelog.published | A changelog entry goes live. |
Each message names what happened and links to the post.
Delivery happens after the visitor's request has been answered, so somebody posting on your board is never left waiting on Slack.
When it breaks
Each route keeps its own delivery history — press History on the row to see the last attempts with their response codes.
A failing route is retried with a widening gap and then stops, and the row says what went wrong in English. Slack revoking a webhook URL, or a channel being archived, shows up here rather than silently.
Internal network addresses are refused, so a pasted URL cannot be used to make us fetch something inside our own infrastructure.
Signed webhooks instead
If you want the events in your own code rather than in a channel, use webhooks — the same events, as signed JSON to an endpoint you control.