Sentry (Public Integrations)

Overview

Pre-built tooling

Pre-built integrations

Access requirements

Setup guide

Useful links

API gotchas

Pre-built tooling

✅ Authorization

Tools	Status
Pre-built authorization (OAuth)	✅
Credentials auto-refresh	✅
Pre-built authorization UI	✅
Custom authorization UI	✅
End-user authorization guide	✅
Expired credentials detection	✅

✅ Read & write data

Tools	Status
Pre-built integrations	✅
API unification	✅
2-way sync	✅
Webhooks from Nango on data modifications	✅
Real-time webhooks from 3rd-party API	✅
Proxy requests	✅

✅ Observability & data quality

Tools	Status
HTTP request logging	✅
End-to-end type safety	✅
Data runtime validation	✅
OpenTelemetry export	✅
Slack alerts on errors	✅
Integration status API	✅

✅ Customization

Tools	Status
Create or customize use-cases	✅
Pre-configured pagination	🚫 (time to contribute: <48h)
Pre-configured rate-limit handling	🚫 (time to contribute: <48h)
Per-customer configurations	✅

Others

Function name	Description	Type	Source code
`add-member-to-team`	Add an organization member to a team.	Action	🔗 Github
`add-team-to-project`	Assign an additional team to a project.	Action	🔗 Github
`bulk-delete-issues`	Permanently delete a set of issues by their IDs.	Action	🔗 Github
`bulk-update-issues`	Update the given field(s) on up to 1000 issues at once, selected by id or by the current search query.	Action	🔗 Github
`create-alert-rule`	Create a new alert rule.	Action	🔗 Github
`create-monitor`	Create a new cron monitor for a project.	Action	🔗 Github
`create-project-key`	Create an additional client key (DSN) for a project.	Action	🔗 Github
`create-project`	Create a new project bound to a team	Action	🔗 Github
`create-release-deploy`	Record a new deploy of a release to an environment.	Action	🔗 Github
`create-release`	Create a new release, optionally attaching commits	Action	🔗 Github
`create-team`	Create a new team in a Sentry organization.	Action	🔗 Github
`delete-alert-rule`	Delete an alert rule.	Action	🔗 Github
`delete-issue`	Permanently delete an issue.	Action	🔗 Github
`delete-monitor`	Delete a monitor.	Action	🔗 Github
`delete-project-key`	Delete a project key (DSN).	Action	🔗 Github
`delete-project`	Delete a project.	Action	🔗 Github
`delete-release`	Delete a release.	Action	🔗 Github
`delete-team`	Delete a team	Action	🔗 Github
`get-alert-rule`	Retrieve a single alert rule.	Action	🔗 Github
`get-issue-event`	Retrieve a single event belonging to an issue, with full payload (message, exception, stacktrace, tags, user, contexts).	Action	🔗 Github
`get-issue-tag`	Get aggregate info for one tag key on an issue (unique/total value counts, top values).	Action	🔗 Github
`get-issue`	Retrieve details of a single Sentry issue, including its stats, comment/user-report counts and latest event context.	Action	🔗 Github
`get-monitor`	Retrieve a single monitor’s details.	Action	🔗 Github
`get-organization-event-counts`	Get event counts for the organization grouped and time-bucketed by an arbitrary dimension (category, project, outcome, etc.).	Action	🔗 Github
`get-organization-member`	Retrieve a single organization member.	Action	🔗 Github
`get-organization-stats-summary`	Get accepted, filtered, and dropped event counts per project for the organization over a time window.	Action	🔗 Github
`get-organization`	Retrieve details for the connected Sentry organization.	Action	🔗 Github
`get-project-environment`	Retrieve a single project environment by name	Action	🔗 Github
`get-project-event`	Retrieve a single event’s full payload by project and event ID	Action	🔗 Github
`get-project-key`	Retrieve a single project key (DSN).	Action	🔗 Github
`get-project`	Retrieve details of a single Sentry project	Action	🔗 Github
`get-release`	Retrieve a single release’s details.	Action	🔗 Github
`get-team`	Retrieve a single team’s details.	Action	🔗 Github
`invite-organization-member`	Invite a new member to a Sentry organization by email	Action	🔗 Github
`list-alert-rules`	List the organization’s alert rules (Sentry’s current public API models these as “alerts”/“workflows”).	Action	🔗 Github
`list-issue-events`	List the individual events that make up an issue (group).	Action	🔗 Github
`list-issue-tag-values`	List the distinct values seen for one tag key on an issue, with cursor pagination.	Action	🔗 Github
`list-monitor-checkins`	List check-in events recorded for a monitor.	Action	🔗 Github
`list-monitors`	List cron monitors for the organization, optionally filtered by project or environment.	Action	🔗 Github
`list-organization-environments`	List environment names known to the organization	Action	🔗 Github
`list-organization-issues`	List issues across a Sentry organization, optionally filtered by projects, environments, time window, or search query.	Action	🔗 Github
`list-organization-members`	List members of the organization.	Action	🔗 Github
`list-organizations`	List organizations accessible to the connected account.	Action	🔗 Github
`list-project-environments`	List a project’s environments (including hidden ones only when requested).	Action	🔗 Github
`list-project-events`	List events ingested for a project, optionally windowed by time.	Action	🔗 Github
`list-project-issues`	List issues bound to a single project, with optional search query, sorting, and cursor pagination.	Action	🔗 Github
`list-project-keys`	List a project’s client keys (DSNs).	Action	🔗 Github
`list-project-releases`	List releases associated with a single project.	Action	🔗 Github
`list-project-teams`	List the teams a project is assigned to.	Action	🔗 Github
`list-projects`	List all projects in a Sentry organization.	Action	🔗 Github
`list-release-commits`	List commits associated with a release.	Action	🔗 Github
`list-release-deploys`	List the deploys recorded for a release.	Action	🔗 Github
`list-release-files`	List source/asset files uploaded for a release.	Action	🔗 Github
`list-releases`	List releases for the organization.	Action	🔗 Github
`list-team-members`	List the members of a team.	Action	🔗 Github
`list-team-projects`	List a team’s projects	Action	🔗 Github
`list-teams`	List all teams in a Sentry organization	Action	🔗 Github
`remove-member-from-team`	Remove an organization member from a team.	Action	🔗 Github
`remove-organization-member`	Remove a member from the organization.	Action	🔗 Github
`remove-team-from-project`	Unassign a team from a project, revoking its access	Action	🔗 Github
`update-alert-rule`	Update an alert rule’s name, enabled state, config, or trigger/action wiring.	Action	🔗 Github
`update-issue`	Update an issue’s status, assignment, bookmark, or subscription state.	Action	🔗 Github
`update-monitor`	Update a monitor’s name, slug, or schedule config.	Action	🔗 Github
`update-organization-member`	Update a member’s organization-level role and/or per-team roles.	Action	🔗 Github
`update-project-environment`	Hide or unhide a project environment.	Action	🔗 Github
`update-project-key`	Update a project key’s name, rate limit, or active state.	Action	🔗 Github
`update-project`	Update a project’s settings (name, slug, platform, bookmarked flag, digest delays, and more). Only submitted fields are changed.	Action	🔗 Github
`update-release`	Update a release’s ref/url/dateReleased or commit list.	Action	🔗 Github
`update-team`	Update the slug, name, or other settings of a team.	Action	🔗 Github
`alert-rules`	Sync the organization’s alert rules (workflows in Sentry’s current public API)	Sync	🔗 Github
`events`	Sync events ingested per project, using time-window pagination	Sync	🔗 Github
`issues`	Sync issues (error groups) across all projects in the organization.	Sync	🔗 Github
`members`	Sync organization members.	Sync	🔗 Github
`monitors`	Sync cron monitors for a Sentry organization, including schedule configuration and nested monitor environments.	Sync	🔗 Github
`project-keys`	Sync all client keys (DSNs) across every project in the Sentry organization	Sync	🔗 Github
`projects`	Sync all projects in a Sentry organization, including their teams and environments. Full refresh; projects deleted in Sentry are removed from the cache.	Sync	🔗 Github
`releases`	Sync releases for the organization.	Sync	🔗 Github
`teams`	Sync all teams in the Sentry organization.	Sync	🔗 Github

Access requirements

Pre-Requisites	Status	Comment
Paid dev account	✅ Not required	Free, self-signup here.
Paid test account	✅ Not required	Free, self-signup here.
Partnership	✅ Not required
App review	❗ Required if publishing	Required only when publishing the integration.
Security audit	✅ Not required

Setup guide

Create a Sentry account

If you don’t already have a Sentry account, go to sentry.io and sign up for a free account.
Sign in to your Sentry account.

Create a new Nango integration

Navigate to Integrations, then click Configure New Integration.
Search for Sentry (Public Integrations) and select it.
You can leave the Client ID and Client Secret fields empty for now — you’ll fill them in later.

Create a new Sentry integration

Naviagate to Settings > Custom Integrations.
Click Create New Integration and select Public Integration then click Next.

Configure your integration

Fill in the required fields:

Name: Enter a name for your integration (e.g., “My App Integration”).
Author: The company or person who built and maintains this Integration.
Webhook URL: You can find the specific Webhook URL on the integration page of the Nango integration you created earlier in Step 2.
Under PERMISSIONS, configure the required scopes for your integration.

Obtain your OAuth credentials

After saving your integration, you’ll receive:

Client ID
Client Secret

These will be used when configuring your integration in Nango.

Configure your integration in Nango

Using the integration you created earlier within Nango, enter your Client ID and Client Secret from the previous step, then save your changes.

Submit for review (if publishing publicly)

Once your integration is ready for public use, ensure that you have a valid logo, navigate to Settings > Custom Integrations.
Click Publish next to your integration.
This will notify the Sentry team (via email) that your app is ready for review.

Public integrations require review before being listed in the Sentry marketplace.

Follow the Quickstart.

Need help getting started? Get help in the community.

Useful links

Topic	Links
General	Sentry Website
	Create a Sentry Account
Developer	Integration Platform Overview
	API Reference
	Authorization & OAuth Guide
	Public Integration
	Public Integration OAuth Process
	Public Integration Publication
	Rate Limits
	Alerts & Notifications

Contribute useful links by editing this page

API gotchas

A partial connection is created when initiating the OAuth flow for a Sentry public integration in Nango. This connection remains in a pending state until the user manually accepts and installs the integration from the Sentry Public Integrations page (via the Accept & Install button).

Contribute API gotchas by editing this page

Going further

Connect to Sentry (Public Integrations)

Guide to connect to Sentry (Public Integrations) with an Auth Token using Connect UI

​Overview

Pre-built tooling

Pre-built integrations

Access requirements

Setup guide

Useful links

API gotchas

​Pre-built tooling

​Others

​Access requirements

​Setup guide

​Useful links

​API gotchas

​Going further

Connect to Sentry (Public Integrations)

Overview

Pre-built tooling

Others

Access requirements

Setup guide

Useful links

API gotchas

Going further