Skip to main content
The Devin AI connector gives Rootly AI authenticated access to repository knowledge in your Devin organization. AI SRE can discover available repositories, read their generated wikis, and ask grounded questions about the code during an investigation. The same connection exposes a reviewed set of Devin platform tools in Slack AI. Slack AI users can run supported read-only actions, while changing Devin resources additionally requires permission to manage AI connectors. Every request runs as the connected service user, so Devin separately limits the data and actions available through that account’s role.
For public GitHub repositories that do not require authentication, use the separate DeepWiki AI connector. Connecting DeepWiki does not grant access to your Devin organization.

​
Before You Start

You need:
  • A Devin organization with the repositories Rootly AI should investigate available to it.
  • Permission in Devin to create a service user and assign its role.
  • Permission in Rootly to manage AI connectors.
  • An organization-scoped service-user API key beginning with cog_.
Create a dedicated Devin service user with only the permissions your team wants Rootly to use. Devin displays the API key once when you generate it, so store it securely until you finish the Rootly setup.
Rootly does not currently support Devin enterprise service-user keys or personal access tokens that require an X-Org-Id header. Legacy keys beginning with apk_ or apk_user_ are also unsupported.

​
Connect Devin

Use these steps to connect a dedicated Devin service user to Rootly AI.
1

Create a Devin Service User

In Devin, open Settings → Service users for the organization you want to connect. Create a dedicated service user and assign a role whose repository and platform permissions match the access Rootly should have.
2

Generate the API Key

Generate an organization-scoped API key for the service user. Copy the key beginning with cog_ when Devin displays it.
3

Open the Devin AI Connector

In Rootly, go to AI & Agents → Connectors and click Connect on the Devin card.
4

Enter the Service-User Key

Paste the key into Service user API key, then click Connect.
5

Confirm the Connection

Rootly validates the reviewed tool catalog and verifies that the service user can list the organization’s available repositories. The card shows Connected after both checks succeed.
Rootly encrypts the API key at rest. One Rootly team has one active Devin connection, shared by the team wherever the connector’s tools are allowed.

​
AI SRE Repository Tools

AI SRE receives four repository-focused tools: This profile is read-only. AI SRE cannot launch a Devin session or use the platform management tools described below.

​
Investigation Examples

  • “Which repositories can Devin access for the checkout service?”
  • “Read the checkout repository’s architecture wiki and trace a request from the API to the payment provider.”
  • “Which retry and idempotency edge cases could explain duplicate charges in this incident?”
  • “Find where this error is handled and identify the tests that cover an upstream timeout.”
  • “Compare the repository documentation with the observed failure. Which assumption no longer holds?”
  • “The repository name is ambiguous. List the available matches before reading its wiki.”

​
Slack AI Platform Tools

Slack AI can use the broader reviewed Devin catalog. Supported read-only actions are available to Slack AI users; actions that change Devin resources additionally require permission to manage AI connectors. Slack AI users can use read-only Devin tools from an incident channel, the Slack assistant pane, or a direct message. Users with permission to manage AI connectors can also run mutating Devin actions from those surfaces. Rootly-native writes such as paging or changing an incident remain limited to incident channels; Devin actions use the connector-specific boundary instead.
The connected service user’s repository and organization access applies to every Devin call. Slack AI users without permission to manage AI connectors can still query repositories and inspect supported platform resources available to that service user. Use a dedicated service user whose access is appropriate for every Rootly user with an Incident Response role.
Slack AI also receives the four repository tools listed above. The following platform operations are read-only and do not require permission to manage AI connectors: The following operations change Devin resources and require permission to manage AI connectors: For a tool that accepts an action, Rootly treats any action not listed in the read-only table as mutating for authorization and confirmation. These tools can change your Devin organization or consume Devin credits. Rootly asks for confirmation before high-risk calls when your Rootly AI guardrails require it, and checks the user’s permission to manage AI connectors again immediately before execution.
The service user’s Devin role remains the provider-side security boundary. Rootly authorization determines which operations the requesting user can run, while Devin determines what the connected service user can perform.

​
Slack AI Examples

  • “Start a Devin session to reproduce the checkout timeout, add a regression test, and report the result here.”
  • “Check the session’s progress and summarize the evidence it has gathered so far.”
  • “Send the failed test output to the active session and ask Devin to revise its approach.”
  • “Generate the wiki for the newly connected repository, then confirm when it is ready.”
  • “Find the on-call configuration for this service without changing it.”
For requests that can modify Devin, Slack AI presents the proposed action before execution when confirmation is required. Review repository targets, instructions, schedules, and other action parameters carefully.

​
Access and Data Handling

  • Permission-scoped: Devin applies the connected service user’s organization role and repository access to every request.
  • Surface-specific tools: AI SRE receives only repository tools. Slack AI receives the broader platform catalog, but changing Devin resources additionally requires permission to manage AI connectors.
  • Reviewed tool sets: Rootly blocks newly advertised Devin tools until they are reviewed and explicitly supported.
  • Encrypted credential: Rootly stores the organization-scoped service-user API key encrypted at rest.
  • Data sent to Cognition: Prompts, repository identifiers, questions, and platform action parameters are processed by Cognition.
  • Redacted session history: Raw Devin tool results and the response derived from them are available during the active interaction but are replaced with omission markers in durable AI session history.
  • Quality traces: Connector results can appear in retained LLM traces used for quality monitoring. See Data Privacy for Rootly AI for the retention boundary.
  • Audit boundary: Rootly logs connector tool-call telemetry, but a provider-side change is not a standard Rootly audit event attributed to the requesting user. Review Devin’s audit history for provider-side records associated with the service user.

​
Managing the Connection

Open the Devin card to reconfigure or disconnect it. To rotate the key, create a replacement organization-scoped key in Devin and reconnect with it. Rootly validates the replacement before removing the working connection, so a failed validation leaves the existing connection available. After a successful rotation, revoke the old key in Devin. Disconnecting removes Rootly’s stored credential and prevents future Devin queries or actions; it does not revoke the key in Devin or delete Devin resources.

​
Troubleshooting

Confirm the key is an organization-scoped service-user key beginning with cog_. Rootly cannot use a key that requires a separate X-Org-Id header or a legacy key beginning with apk_ or apk_user_.
Confirm the service user is active, belongs to the intended organization, and can list at least the repositories Rootly should investigate. If you copied the key incompletely, generate a replacement in Devin and try again.
Sign in to Devin and confirm the repository is available to the connected organization and service user. Repository access can differ from the access of your personal Devin account.
Launching a session changes Devin resources, so the user must have permission in Rootly to manage AI connectors and the connected service user must have the required Devin permission. Slack AI users without that Rootly permission can still use the supported read-only tools but cannot create or change Devin resources.
Check the Devin organization for available credits, repository access, and session errors. Then retry with a specific repository and bounded instructions. Connecting successfully verifies authentication and repository discovery, but it does not guarantee that every later platform action can run.
The key may have been revoked or the service user’s role may have changed. Generate a new organization-scoped key, reconfigure the Devin card, and revoke the old key after Rootly validates the replacement.

​
Frequently Asked Questions

No. The Devin connector currently uses an organization-scoped service-user API key. Rootly does not ask you to authorize an OAuth application.
No. Keys that require a separate X-Org-Id header are not supported. Generate an organization-scoped service-user key for the Devin organization you want to connect.
No. AI SRE receives only repository discovery, wiki reading, and question-answering tools. Slack AI exposes the session and platform catalog; changing Devin resources additionally requires permission to manage AI connectors.
No. Devin and DeepWiki are separate Rootly connectors with different access boundaries. Connect DeepWiki separately if you also want no-authentication access to public GitHub repository documentation.

DeepWiki

Query public GitHub repository documentation without a credential.

Connectors

Browse all Rootly AI connectors and how investigations use them.

Devin MCP

Review Cognition’s authentication options and Devin MCP tool catalog.