Sentry
Connect a Sentry Internal Integration so new Sentry issues and events start Nested agent tasks, with signed webhooks and issue comments.
Sentry is a provider trigger: connect your Sentry organization once, and automations can start an agent when Sentry reports an event, so triage begins before anyone opens the issue.
Before you start#
- In Sentry, create an Internal Integration. Note its installation UUID and client secret, and create an auth token with
project:read(so Nested can list projects) andevent:write(so it can post issue comments).
Steps#
- Create an automation and add the Sentry trigger.
- Select Connect Sentry and enter the Organization slug (for example
acmefromsentry.io/organizations/acme/), Installation UUID, Client secret, and Auth token. - Nested verifies the token and shows a Webhook URL. Paste it into the Internal Integration’s webhook settings in Sentry.
- Choose the conditions under Start when, write the instructions, and save.
Nested verifies every inbound Sentry webhook with the sentry-hook-signature header and the client secret.
Example#
Start your on-call agent when Sentry reports a new issue, with the instructions “Find the commit that likely introduced this error and summarize the fix.” Turn on Mark task complete when the agent finishes for a daily list of triaged issues.
Questions
- Which Sentry permissions does Nested need?
- An auth token with
project:readto list projects andevent:writeto post issue comments, plus the Internal Integration’s client secret to verify webhooks.