Sentry integration

What it does

The Sentry integration lets your agency run a client's error monitoring from inside a workflow. Connect a client's Sentry organization once and your workflows can triage issues (resolve, assign, bookmark, delete), read the events behind them, set up projects, teams and client keys (DSNs) for a new client, and record releases and deploys from your CI. Five webhook triggers start a workflow when an issue alert or metric alert fires, an issue is created or changes state, an error event arrives, or someone comments on an issue.

Organization, team, project and environment fields are dropdowns filled from the connected account, so you pick a project instead of typing its slug. Every dropdown also accepts a mapped value from an earlier step.

Connect a Sentry account

Sentry authenticates with a token. You can use either kind:

• Internal integration token (recommended). It belongs to the organization rather than a person, and you need an internal integration anyway for the triggers. In Sentry, open Settings → Developer Settings → Custom Integrations, click Create New Integration, choose Internal Integration, and grant the permissions your workflows need: Project (Read & Write, or Admin to delete projects), Team (Read & Write, or Admin to delete teams), Release (Admin), Issue & Event (Read & Write, or Admin to delete issues), Organization (Read, or Write to update settings) and Member (Read). Save, then copy the token from the integration page.
• Personal token. Open User Settings → Personal Tokens, create a token with the matching scopes (org:read, org:write, project:read, project:write, project:admin, project:releases, team:read, team:write, team:admin, member:read, event:read, event:write, event:admin), and copy it. It stops working if that person leaves the organization.

Then:

1. Open your workspace in TaskJuice and go to Connections.
2. Choose Sentry and click Connect.
3. Paste the token and enter the organization slug (the acme-co in acme-co.sentry.io or sentry.io/organizations/acme-co/), and save.

The connection reaches Sentry SaaS at sentry.io. Self-hosted Sentry is not supported.

Triggers

Sentry has no API for registering webhooks, so you set the subscription up by hand on the internal integration. One integration delivers every resource to the same URL, and TaskJuice routes each delivery to the right trigger by the Sentry-Hook-Resource header.

• sentry-app/issue-alert fires when an issue alert rule runs this integration as an action, with the event that matched and the rule name.
• sentry-app/metric-alert fires when a metric alert changes state (critical, warning or resolved).
• sentry-app/issue-changed fires when an issue is created, resolved, assigned, archived or unresolved. The action field says which.
• sentry-app/error-event fires for every error event Sentry ingests, not only the first one of an issue. Sentry offers this resource only on its Business and Enterprise plans.
• sentry-app/issue-comment fires when a comment on an issue is created, updated or deleted.

To set them up:

1. Add the trigger to a workflow and copy the webhook URL shown on it.
2. In Sentry, open your internal integration (Settings → Developer Settings → Custom Integrations) and paste the URL into Webhook URL.
3. Under Webhooks, tick the resources your triggers use: issue for Issue Created or Updated, error for Error Event Created, comment for Issue Comment. These need the Issue & Event permission.
4. For Issue Alert and Metric Alert, turn on Alert Rule Action, save, then add the integration as an action on the alert rules that should start the workflow.
5. Copy the integration's Client Secret and paste it into the trigger's signing secret field. Sentry signs every delivery with HMAC-SHA256 over the raw body (the Sentry-Hook-Signature header), and TaskJuice rejects a delivery whose signature does not match.

Actions

Issues and events

• sentry-app/list-issues lists an organization's issues, optionally narrowed to one project, an environment, a search query (for example is:unresolved) and a stats period.
• sentry-app/get-issue returns one issue by ID or short ID (for example ACME-123), with counts and status.
• sentry-app/update-issue resolves (now or in the next release), ignores, unresolves, reassigns or bookmarks an issue. Send only the fields you want to change.
• sentry-app/delete-issue deletes an issue and all its events. Sentry deletes in the background.
• sentry-app/list-issue-events lists the events grouped under an issue.
• sentry-app/list-project-events lists the error events a project captured.
• sentry-app/get-event returns one event by its 32-character event ID.
• sentry-app/list-tag-values lists the values recorded for a tag key on a project, such as browser or release.
• sentry-app/list-project-users lists the end users seen in a project's events.

Projects and client keys

• sentry-app/list-projects lists every project the token can reach.
• sentry-app/get-project, sentry-app/create-project, sentry-app/update-project and sentry-app/delete-project manage projects. A new project is created inside a team you pick.
• sentry-app/create-project-key creates a client key and returns its DSN, ready to hand to an SDK.
• sentry-app/list-project-keys lists a project's client keys with their DSNs.

Releases and deploys

• sentry-app/list-releases, sentry-app/get-release, sentry-app/create-release, sentry-app/update-release and sentry-app/delete-release manage releases. Create Release takes the projects it belongs to from a multi-select.
• sentry-app/create-deploy records that a release was deployed to an environment, so Sentry can tie new issues to the deploy that shipped them.

Organizations, teams and members

• sentry-app/list-organizations, sentry-app/get-organization and sentry-app/update-organization read and change organization settings.
• sentry-app/list-organization-teams, sentry-app/get-team, sentry-app/create-team, sentry-app/update-team and sentry-app/delete-team manage teams, and sentry-app/list-team-projects lists a team's projects.
• sentry-app/list-organization-members lists the organization's members.
• sentry-app/list-organization-repositories lists the code repositories connected to the organization.

Known limitations

• The webhook subscription is manual (see Triggers). Each client organization needs its own internal integration.
• The error webhook resource is available only on Sentry's Business and Enterprise plans. On Developer and Team plans, use Issue Alert or Issue Created or Updated instead.
• Sentry expects a webhook response within one second.
• List actions return one page. To read the next page, pass the cursor from the previous response's Link header.
• Dropdowns show the first 100 projects or teams. For a larger organization, map the slug instead.
• Sentry rate-limits per organization and answers 429 when you exceed it. TaskJuice retries 429 responses with backoff.