Under Connections you store a Sentry credential for your organization. You can then enable Sentry under Features for apps, homepages, and backends – the platform creates the matching project and writes the DSN into the generated configuration.
Two options
| Option | Works with | Note |
|---|---|---|
| Connect with Sentry (OAuth) | Sentry Cloud only | Opens Sentry login via a Public Integration |
| Add API token | Cloud and self-hosted | Host/URL, organization slug, and auth token |
Tip
OAuth is available for Sentry Cloud only. For your own instance, always use the API token path.
Create an API token (recommended)
In Sentry Cloud
- Sign in at sentry.io and open your organization.
- Go to Settings → Account → API → Auth Tokens (or organization tokens under Settings → Developer Settings / Auth Tokens – labels may vary slightly).
- Create a new token with permissions to create projects and client keys. At minimum:
- Read organization (
org:read) - Read and write projects (
project:read,project:write) - Read and write teams (
team:read,team:write) – if no matching team exists, the platform creates one
- Read organization (
- Copy the token once and store it securely.
On self-hosted
The flow is the same on your instance URL (e.g. https://sentry.example.com). The token must cover the same organization and permissions.
Enter the values in the Application Platform
Under Connections → Sentry → Add API token:
| Field | Value |
|---|---|
| Name / Slug | Display name and immutable slug for selecting the credential in projects |
| Instance | Sentry Cloud (sentry.io) or Self-hosted |
| Sentry URL | Self-hosted only: base URL of your instance (without /api/0) |
| Organization (slug) | Organization slug from the Sentry URL, e.g. my-company |
| Auth token | The token you just created |
After saving, enable Sentry in the project editor under Features and select this credential.
What the platform does next
When Sentry is enabled for an app, homepage, or backend, the platform ensures team, project, and client key exist in your Sentry organization and writes the DSN into the generated env/GitOps files.
Security
- Do not share auth tokens publicly; restrict access to organization admins.
- Rotate tokens if compromise is suspected and update the entry under Connections.
- Grant only the scopes you need – avoid overly broad admin tokens.
See also
- Connections – SMTP, Google/Firebase, and Sentry overview
- Firebase: Credentials – service account JSON and OAuth (Beta)
- Error tracking – enabling per component
- Working with Sentry – issues and releases