Skip to main content
Connect your Sentry organization to let CloudThinker agents search issues, events, and traces, review projects and teams, and pull root-cause signals during incident response and release triage. Sentry uses OAuth, so you do not need to create a Sentry token or paste credentials into CloudThinker. Agents only read your error data — investigation leaves it unchanged.

​
Prerequisites

  • A Sentry account with access to the organization you want CloudThinker to investigate.
  • Permission to authorize CloudThinker through Sentry’s OAuth flow.

​
Setup

1

Open CloudThinker

Navigate to Connections → Sentry in your CloudThinker workspace.
2

Start the OAuth flow

Click Connect to open Sentry’s authorization page.
3

Authorize CloudThinker

Sign in to the Sentry account that can access the organization you want agents to investigate, then approve access.
4

Return to CloudThinker

After authorization, CloudThinker stores the OAuth tokens and shows a Connected status.

​
Connection details

Sentry uses OAuth — there are no connection fields to enter manually.

​
Required permissions

CloudThinker inherits the Sentry access granted during OAuth — agents see the organizations and projects the authorizing account can see.
Authorize with an account scoped to the organization you want investigated. Agents read issues, events, and traces; they do not change your Sentry data.

​
Agent capabilities

Once connected, agents can:

​
Verify the connection

​
Example prompts

​
Troubleshooting

Your browser may be signed in to the wrong Sentry account, or not signed in at all. Sign in to the intended Sentry account and retry the connection flow from Connections → Sentry.
The OAuth flow was completed with an account that lacks access to those projects. Reconnect using a Sentry account that belongs to the right organization and teams.
The authorization may have been revoked in Sentry. Remove the connection in CloudThinker and run the OAuth flow again.

​
Security

  • Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
  • Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
  • Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
  • Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
  • Read-focused investigation — agents search and read error data; your Sentry issues and events stay unchanged.
  • Scope by account — the connection sees exactly what the authorizing Sentry account sees, so authorize with an appropriately scoped account.

Rollbar Connection

Error tracking and deployment correlation

Datadog Connection

Log search, metrics, and monitoring