Quickstart
Connect GitHub and Slack, then verify the setup with a test message.
Connect a GitHub account and Slack workspace, choose where notifications go, and send a test message. You need workspace admin access in Angada, permission to install the Angada GitHub App for the repositories you want to connect, and permission to authorize Angada in your Slack workspace.
The visible result is a confirmation in Angada that the test message was delivered, plus the message in your selected Slack channel. This verifies the integration setup; it does not depend on an AI review being available on your plan.
1. Create or open a Workspace
Sign in to Angada. If you are creating a Workspace, enter its name during onboarding. The person who creates the Workspace becomes its first admin. A Workspace is tied to one GitHub account and one Slack workspace; see Roles and permissions for the difference between workspace access and review eligibility.
2. Connect GitHub
On the Connect your code step, select Connect GitHub. On GitHub, install the Angada GitHub App and grant it access to All repositories or Only select repositories. Return to Angada and confirm the step shows GitHub connected. Angada can watch pull requests in the repositories granted to the App; to change access later, update the App installation on GitHub. See GitHub integration for access details.
3. Connect Slack
On the Bring in Slack step, select Add to Slack and authorize Angada in the Slack workspace you want to use. Return to Angada and confirm Slack workspace linked appears with your team's name.
4. Choose a default channel
On Choose where PRs land, select a Slack channel. Angada saves it as the default destination for notifications unless a repository has its own channel route. The confirmation Default channel saved. appears after the selection is saved. See Channel routing to configure repository-specific destinations.
5. Send a test message
On Send a test message, select Send test message. Angada posts a sample pull-request notification to the channel you selected. The page then shows Delivered to #channel-name, and you can confirm the sample message appears in that Slack channel.
After setup
To see AI Review on a pull request, open or update a pull request in a connected repository. Draft pull requests are skipped by default, and the default Post findings at or above setting is High. Workspace plan, review eligibility, and limits can affect whether an AI review runs or posts findings; see Review settings and AI Review for details.
For the notification card on a pull request, see Living PR card. For Slack connection recovery and permissions, see Slack integration.
Next steps
- AI Review — understand review status and findings.
- Channel routing — route repositories to specific channels.
- AI Wiki — generate a source-cited guide to a connected repository.