Integration
Send delivery updates to Slack
Authorise once, pick a channel, and choose which three things Stride is allowed to interrupt you about. The point is a quiet channel — a feed that reproduces every backlog event gets muted in a week, which is worse than no integration at all.
Three switches, nothing else
| Toggle | Posts when |
|---|---|
| Mentions | Someone @-mentions a teammate on a story, comment, or document. |
| Status changes | A story moves between status categories. |
| Sprint events | A sprint opens or closes. |
Stride maps its members to Slack users, so a mention notifies the right person rather than posting a name as plain text.
Scope and limits, up front
- Outbound only. Stride posts to Slack. It does not read channel history, DMs, or files, and you cannot drive Stride from a slash command.
- One workspace, one channel. No per-project routing today.
- Best-effort delivery. A Slack failure is logged and swallowed so it can never fail the underlying write. There are no retries on the Slack path.
- Connection health is surfaced in settings, so a revoked authorisation shows up as a broken connection instead of silence.
Need guaranteed delivery, per-project routing, or a richer event set? That is what webhooks are for — retries with backoff, manual replay, and 19 subscribable events.
Frequently asked questions
How do I connect Slack to Stride?
Open Settings → Integrations → Slack and authorise the app over OAuth, then choose the channel Stride should post to. There is no bot token to paste and no manifest to configure.
What exactly gets posted?
Three independently switchable categories: @-mentions of your teammates, story status transitions, and sprint open/close events. Each is off or on for the whole workspace — there is no per-project or per-user routing today.
Can I post to more than one channel?
Not today. One Slack workspace and one default channel per Stride workspace. If you need different streams for different projects, use webhooks and route them yourself.
What happens if Slack is down?
The notification is dropped and the failure is logged; the underlying story update or sprint close still succeeds. This is deliberate — a Slack outage must never fail a write in Stride. It also means Slack is a convenience channel, not a delivery guarantee. If you need at-least-once delivery with retries and replay, use webhooks.
Does Stride read my Slack messages?
No. This is an outbound integration. Stride posts to the channel you nominate and does not read channel history, DMs, or files.