Sentry integration

What it does

The Sentry integration lets your agency run a client's error monitoring operations without leaving TaskJuice. Connect a client's Sentry organization once and you can list and update issues, list projects, provision client keys (DSNs) for new SDKs, and list releases against the Sentry REST API at sentry.io. Two webhook triggers turn Sentry activity into workflow runs covering issue alerts and issue lifecycle changes (created, resolved, assigned, archived).

Connect a Sentry account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Sentry and click Connect.
3. Sign in to the Sentry organization you want to manage on behalf of your client.
4. Open User Settings, choose Auth Tokens, and create a new user auth token scoped to event:read, project:read, project:write, project:releases, and org:read. These are the minimum scopes the action set needs.
5. Copy the token, paste it into TaskJuice, enter the organization slug (the value that appears in your Sentry URL, for example acme-co in sentry.io/organizations/acme-co/), and save.

The token is stored encrypted and is sent on every action as a Bearer credential on the Authorization header. To revoke access, sign in to Sentry, open User Settings, choose Auth Tokens, and delete the token. TaskJuice surfaces the resulting 401 on the next workflow run so you can rotate the credential.

Triggers

• sentry-app/issue-alert fires when a Sentry Issue Alert rule is triggered, with the captured event payload and the rule that matched.
• sentry-app/issue-changed fires when an issue is created, resolved, assigned, ignored, archived, or marked unresolved.

Both triggers are powered by a Sentry Internal Integration. Each POST is signed with HMAC-SHA256 over the raw request body and the hex digest is sent in the Sentry-Hook-Signature header. Paste the client secret from your internal integration into the trigger so TaskJuice can verify every inbound POST before activating the workflow.

Actions

• sentry-app/list-issues pages through issues for the connected organization with optional query (for example is:unresolved), environment, and stats period filters.
• sentry-app/get-issue fetches a single issue by ID, including counts, status, and tags.
• sentry-app/update-issue resolves, ignores, reassigns, or bookmarks an issue. Pass only the fields you want to change.
• sentry-app/list-projects lists projects accessible to the auth token across all organizations.
• sentry-app/create-project-key provisions a new client key (DSN) for a project, used by SDKs to ingest events.
• sentry-app/list-releases lists releases for the organization, optionally filtered by project ID or version query.

Known limitations

• Sentry user auth tokens are scoped to the user who created them. If that user loses access to the organization, the token stops working. Use a service account where possible.
• The Sentry API enforces per-organization rate limits and returns 429 with a Retry-After header when exceeded. The action engine retries 429 responses with backoff; high-volume cycles should pace work with a downstream throttle.
• Webhooks are configured by an Internal Integration on the Sentry organization. Each client therefore needs an internal integration installed with the issue and event_alert resources subscribed.
• Pagination is cursor-based via the Link header. Pass the cursor query parameter from the previous response's rel="next" link to fetch the next page.
• The update-issue action is the only mutation on issues; assigning to a team requires prefixing the team slug with # (for example #oncall).