Slack integration

The Slack integration is where Angada's coordination happens: living PR cards, threads, mentions, and digests all post into your Slack workspace.

GitHub AppRepository access and checks

SlackChannels, threads, and mentions

Angada's request to join the workspace, as the approving admin sees it.

Connect the workspace

1. On the Bring in Slack step of onboarding, select Add to Slack.
2. Approve the request on Slack's standard OAuth consent screen.
3. You're returned to Angada, where the step now shows Slack workspace linked with your Slack team's name.
4. Choose the default channel — the destination for every connected repo that doesn't have its own route. You can also trigger a repo sync from here if you've just changed GitHub App access.

Required role: you need permission to approve OAuth requests for your Slack workspace (typically a workspace admin), and Angada needs to be allowed to join the channels you route to.

One Angada Workspace connects to exactly one Slack workspace. To send notifications to a different workspace, use a different Angada Workspace — see Workspaces and switching.

Choose where PRs land

New connections post to the default channel immediately. From there, tune delivery per repo: route specific repos to their own channels and set per-route delivery filters. See Channel routing.

Make mentions actionable

By default, a mention in a PR card is just text. Identity links connect GitHub logins to Slack users — matched automatically by profile email, or set manually — so a "changes requested" mention pings the author and a review-request mention pings the reviewer. See Identity links and mentions.

What posts to Slack

• A living card per PR — one message, updated in place; never a repost per event. See Living PR card.
• Thread events — comments and review activity appear in the card's thread.
• Digests — personal DMs, channel rollups, and Team Reports on a schedule.

Each route can be tuned — human-only delivery, bot handling, comment delivery, and an author denylist — so a firehose channel and a quiet leadership channel can coexist.

Workspace-wide vs. personal

Integration-level choices — which workspace, the default channel, routing, and channel digests — are workspace settings managed by admins. Your personal digest is yours alone: enable it, pick the time and timezone in your own notification preferences, and only your pending work shows up.

Connection states and recovery

A Slack connection is active, suspended, or revoked. If cards stop posting:

1. Check that the Angada app is still installed and not blocked in your Slack workspace's admin settings.
2. Reconnect from Angada's Slack connection screen — reconnecting keeps your routes, digests, and history.
3. If the workspace was swapped to a new one, re-check routing: channel references from the old workspace won't resolve.

Disconnecting pauses delivery without erasing your setup, so recovery is usually one re-approval away.