Sentry
Read Sentry projects, teams, members, issues and events; resolve, assign and prioritise issues; create releases and deploys.
Route production errors into service desks and incident tools, and record releases and deploys from delivery pipelines.
Source actions
9
Destination actions
4
Data types
8
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
issue events
- List issue eventsSource
Individual events (occurrences) of an issue, newest first.
issues
- Get issueSource
One issue with status, assignee, priority and counts.
- List issuesSourceIncremental
Issues (grouped errors and performance problems) across the organisation, with status, assignee and counts.
- Update issueDestinationDuplicate protected
Resolves, ignores or reopens an issue, assigns it, or sets priority, bookmark and seen state.
members
- List membersSource
Organisation members with role and invitation state.
project events
- List project error eventsSource
Error events in a project, newest first.
projects
- List projectsSource
Projects in the organisation.
release deploys
- Record deployDestinationNot retried automatically
Records that a release was deployed to an environment.
- List release deploysSource
Deploys of a release to environments.
releases
- Create releaseDestinationDuplicate protected
Creates a release for one or more projects. An existing version is returned unchanged (HTTP 208).
- List releasesSource
Releases in the organisation with new issue, commit and deploy counts, newest first.
- Update releaseDestinationDuplicate protected
Sets the reference, URL or release date of an existing release.
teams
- List teamsSource
Teams in the organisation with member counts.
Authentication
Auth token (internal integration or user token)
Plans and access
All Sentry SaaS plans, including Developer. Organisation auth tokens and internal integration tokens are limited to their scopes; user auth tokens follow the user's membership.
Test environment
A free Developer plan organisation works for testing.
Rate limits
Per-endpoint, per-organisation limits reported in X-Sentry-Rate-Limit headers; HTTP 429 with Retry-After.
Provider events
Integration platform webhooks for issue, error, event alert and comment events. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Self-hosted Sentry is not supported by this recipe.
- Merging, deleting and discarding issues are not implemented.
- Issue lists cover the statsPeriod window (14 days by default, up to 90d); lastSeen filters are applied through the Sentry search query.
- Deploy creation has no idempotency key; uncertain writes are not repeated automatically.