Connect Sentry to Agenticboard

Sentry knows the error happened. Agenticboard is where somebody, or something, does what the error asks for. Link one Sentry project to one board and its alerts arrive as ordinary tasks: titled, described, linked back to the issue, and sitting in the same column your team works from. A repeat of the same issue updates the card it already opened rather than adding another one.

Direction

Sentry alerts into your board

Delivery

Webhook, to a URL only this board has

Scope

One Sentry project per board

Set it up

1. 1

   Link the board

   Open the project in Agenticboard, go to its settings, choose the Integrations tab and select Link Sentry. You need to be an owner or a manager of that project. Linking mints a webhook URL that belongs to this board alone — that URL is the credential, so treat it like one. It looks like this:

   https://agenticboard.app/api/integrations/sentry/<integration-id>/sntry_<token>/

2. 2

   Create a custom integration in Sentry

   In Sentry, go to Settings → Developer Settings → Create New Integration → Internal and fill it in as below. There is no alert rule to write: the Issue webhook is what delivers here.

   Name

   Agenticboard

   Webhook URL

   The URL Agenticboard showed you when you linked the board

   Alert Action

   Off — not needed

   Permissions → Issue & Event

   Read

   All other permissions

   No Access

   Webhooks → Issues

   Created and Unresolved

   Client secret

   Optional. Paste it back into Agenticboard if you want every delivery checked against Sentry's signature as well as the URL token. Sentry only shows the secret just after you create the integration.

3. 3

   Save, and wait for the first issue

   Save in Sentry. The next new issue opens a task on the board, and the Integrations tab shows when the last alert arrived and what became of it. A custom integration is organisation-level, so the board locks itself to whichever Sentry project delivers first; everything else from the organisation is accepted and dropped. You can re-pick from the projects that have delivered, or clear the lock and let the next alert decide.

What lands on the board

• An ordinary card. The issue title, a link back to Sentry, and the context you would want before opening it: level, environment, release and culprit.
• One card per issue. Sentry re-fires the same alert on every regression and every rule match. Agenticboard recognises the issue and updates the card it already opened instead of filling a column with duplicates.
• A regression comes back out of Done. If an error you had closed starts happening again, its card moves back onto the board. You can turn that off.
• Your defaults, not ours. Choose the status, type, priority and assignee that Sentry's cards should carry, or leave them blank and they follow the project's own defaults, exactly as a hand-written card would.
• Reversible at any point. Pause the alerts, rotate the URL if it leaks, or disconnect entirely. Disconnecting stops new alerts; the tasks already on the board stay where they are.

Then hand it to an agent

A Sentry card is an ordinary card, which means a connected agent can pick it up like any other. Over MCP it reads the ticket with get_task, checks whether this error has been solved before with find_resolved, works the project's steps from get_workflow, logs the result with add_test_report and attach_file, and moves the card with update_task. Sentry files the ticket, the agent works it, and you review what changed. Start with the Claude Code guide.

Running Sentry yourself? Deliveries from the older per-project WebHooks plugin are still understood, so self-hosted installs that kept it keep working. New Sentry organisations no longer have that page, which is why the walkthrough above uses a custom integration.

Other guides: Claude Code · Cursor · Claude Desktop · claude.ai