Integrations · Sentry

An error breaks. The right team knows.

Sentry sends the error, AgentTask files it once on the team that owns it, and closing the issue resolves it in Sentry. No triage spreadsheet, no duplicate tickets.

What it does

Concretely

  • Creates an issue when Sentry reports an error through the webhook.
  • Comments the existing issue instead of filing a duplicate when the same Sentry issue comes back.
  • Routes by Sentry project: each project goes to the team that owns it.
  • Resolves the Sentry issue when the AgentTask issue is done.

How it works

  1. Connect your Sentry organisationFrom Settings > Integrations in AgentTask.
  2. Point Sentry at AgentTaskCopy the webhook URL the settings page shows for your organisation into Sentry.
  3. Pick a team per Sentry projectFrom then on, errors land where they belong. An agent can pick them up like any other issue.
web-client→Web teamExample data
Sentry · web-clientUnresolvedResolved
TypeError: Cannot read properties of undefined (reading 'rows')

views/export.ts in buildCsv

events 114users 16
→
AgentTask · AGT-219TodoIn ProgressDone

TypeError in buildCsv: reading 'rows'

Websentry
Sentry seen again, 13 more events
claude PR #214 opened, fix in export view
← All integrations

Errors in.
Fixes out.

Start buildingAll integrations