How connections are organized
Each service type (Jira, Linear, Notion, Sentry, Google Drive, etc.) is a connector. A connection is a specific account or credential under that connector. You can create multiple connections for the same connector if different teams need separate accounts or permissions.Supported connection categories
Slack Agent supports a broad set of connection categories:| Category | Services |
|---|---|
| Issue and work tracking | Jira, Linear |
| Documentation and knowledge | Notion, Google Drive |
| Observability and incidents | Datadog, Sentry, PagerDuty |
| Design and content | Figma, Canva |
| CRM and customer | HubSpot, Salesforce, Pylon, Gong |
| Analytics | PostHog |
| Custom tools | MCP servers |
Add a connection
Open Connections in the web app
Go to Connections in the Slack Agent dashboard and click Add connection. You need to be a global admin (Slack admin, workspace owner, or
cr_admin holder) to add connections.Pick a connector
A searchable grid shows all available connector types (Jira, Linear, Notion, Sentry, Google Drive, and more). Select the service you want to connect. If your tool is not listed, choose Custom to connect it through an MCP server, API endpoint, or other custom integration.
Name and describe the connection
Give the connection a name (required, at least 2 characters) and an optional description. The name defaults to something like “Jira OAuth RO” but you can change it to anything that helps your team identify this connection.
Authenticate
The form shows one or more authentication tabs depending on what the connector supports:
- OAuth
- API key / Credentials
- MCP server
- Fill in any required fields (such as a site URL for Jira or a base URL for Sentry)
- Save the connection first
- Click Connect [Service] to open the provider’s authorization page in a new tab
- Authorize CodeRabbit in the provider
- You are redirected back, and the form shows a “Connected” status with the account email and granted scopes
Test the connection
Click Test to validate that the credentials work. This is available for most connectors after saving. If the test fails, check your credentials or URL fields and try again.
Save
Click Save to create the connection at the workspace level. The connection is now available but not yet assigned to any scope.
Assign to a scope
Go to Scopes and add the new connection to the Base Scope or a scope. The connection does nothing until at least one scope includes it.
Connector-specific notes
Some connectors require additional fields during setup:| Connector | Extra configuration |
|---|---|
| Jira | Site URL (required for both OAuth and credential modes) |
| Sentry | Base URL (sentry.io or a regional variant) |
| PagerDuty | Base URL (api.pagerduty.com or regional) |
| Datadog | Site selector (datadoghq.com, datadoghq.eu, etc.) |
| Google Drive | Service account JSON upload when using service account mode |
| Linear | Policy mode choice: read-only or read-write (OAuth only) |
| AWS | Account ID (12 digits) + region |
How connections work with scopes
Creating a connection does not grant Slack Agent access on its own. A connection only becomes available when a scope explicitly includes it. This means you can configure connections at the workspace level and then decide, scope by scope, which teams or channels should be able to use each one. For most service types, a scope can include one connection per service. MCP connections are the exception: they are additive, so a scope’s MCP servers stack on top of those already included in the Base Scope.Reusing existing integrations and creating new ones
If your team already uses CodeRabbit for pull request reviews, you may already have integrations configured for services like Jira or Linear. Slack Agent can reuse those existing integrations as connections, so you do not need to set them up again from scratch. Create a separate connection when the existing one does not fit: for example, when a different team needs its own account for the same service, when you want a stricter permission mode (read-only instead of read-write), or when a specific scope should only see a subset of a service’s data.What’s next
Scopes
Decide which scopes should be allowed to use each connection.
Knowledge Base
Learn how Slack Agent uses connected systems to build and refine durable workspace knowledge.
MCP servers
See the canonical docs for MCP-based integrations that Slack Agent can use through workspace connections.