Overview
Sentry is an error + performance monitoring platform – issue tracking, release tracking, alerts. The Automize Sentry connector covers issue read/update, event listing, projects, and release management.
- Regions: Sentry.io (US, sentry.io) + EU (de.sentry.io). Self-hosted Sentry (open source) at any URL. Connector pins to one base URL.
- Plans: Developer (free), Team, Business, Enterprise – all expose the API.
Setting up the connection
Auth type: Bearer Token.
- Sign in to Sentry → User Settings → Auth Tokens → Create New Token.
- Pick scopes (project:read, project:write, event:read, org:read, release:admin).
- Copy the token.
- In Automize, open Settings → Connectors → Sentry → Add connection. Paste token + base URL.
Find your credentials at https://sentry.io/settings/account/api/auth-tokens/.
Rate limits
Sentry enforces ~40 req/sec per org. Connector retries 429 with backoff.
Data model
Hierarchy:
Organization ─┬─ Projects ─┬─ Issues ─── Events
│ ├─ Releases
│ └─ Alerts (rules)
└─ Teams ─── Users
org_slug + project_slug uniquely identify a project. Issues + events
have global numeric IDs.Available operations
7 operations available. Click any row to jump to its detail.
| Operation | Category | What it does |
|---|---|---|
| Create Release | General | Create a new release |
| Get Issue | General | Get issue details |
| List Events | General | List events for an issue |
| List Issues | General | List issues for a project |
| List Projects | General | List all projects |
| List Releases | General | List releases for an organization |
| Update Issue | General | Update issue (resolve, ignore, etc.) |
Operations
Create Release
Create a new release
| Parameter | Required | Type | Description |
|---|---|---|---|
Org Slug org_slug | Yes | text | |
Version version | Yes | text | |
Projects projects | Yes | text |
Tips
- org_slug + version (typically a git SHA or semver) + projects: ['project-slug'] (slugs).
- Used to mark deploys + correlate errors to specific commits.
Get Issue
Get issue details
| Parameter | Required | Type | Description |
|---|---|---|---|
Issue Id issue_id | Yes | text |
Tips
- issue_id (numeric). Returns issue + counts (events, users affected) + tags.
List Events
List events for an issue
| Parameter | Required | Type | Description |
|---|---|---|---|
Issue Id issue_id | Yes | text |
Tips
- Events on an issue (each occurrence). Returns stack traces, tags, breadcrumbs.
List Issues
List issues for a project
| Parameter | Required | Type | Description |
|---|---|---|---|
Org Slug org_slug | Yes | text | |
Project Slug project_slug | Yes | text |
Tips
- org_slug + project_slug. Filter by query (Sentry search syntax – e.g. 'is:unresolved age:-7d').
- Sort: date (newest first), priority, freq, user.
List Projects
List all projects
No input parameters.
Tips
- Returns projects across all your orgs. Filter via org_slug.
List Releases
List releases for an organization
| Parameter | Required | Type | Description |
|---|---|---|---|
Org Slug org_slug | Yes | text |
Tips
- org_slug. Filter by project.
Update Issue
Update issue (resolve, ignore, etc.)
| Parameter | Required | Type | Description |
|---|---|---|---|
Issue Id issue_id | Yes | text | |
Status status | Yes | text | |
Assignedto assignedTo | Yes | text |
Tips
- status: 'resolved', 'unresolved', 'ignored'.
- assignedTo: user_id, team_id, or null.
- Useful for auto-routing – e.g. resolve issues that match a deploy fix.
FAQ
- Why does Update Issue return 204 but I see no change?
- 204 is success (No Content). The change applied – refresh Sentry UI. If a project_slug is wrong, you'd see 404.
- Self-hosted Sentry?
- Set base URL to your Sentry instance (e.g. https://sentry.yourcompany.com). Otherwise same API surface.
- How do I auto-resolve issues on a deploy?
- After deploying a fix, call Update Issue status=resolved for matching issues, then Create Release with the deploy's commit SHA. Sentry links resolutions to the release.