AI AGENTS
Sentry Recurrence Deduper that Updates the Existing Linear Bug
When a Sentry issue reopens, an agent checks for an existing Linear ticket and, if found, appends fresh occurrence data and a re-analysis as a comment instead of creating…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry resolved issue reopensSentry
- ActionSearch Linear for matching ticket by fingerprintLinear
- LogicBranch on whether a ticket already exists
- ActionWrite recurrence note for the matchOpenAI
- OutputComment on existing Linear bug or create a new oneLinear
What it does
Keeps your Linear backlog clean by routing recurrences to the right place. When a previously resolved Sentry issue reopens, the agent searches Linear for a matching ticket; if one exists it appends the new event count, latest release, and a refreshed root-cause note as a comment, and only opens a new bug when no match is found — so a flapping error never spawns ten tickets.
When to use it
Use it when duplicate bug tickets pile up from intermittent or reopened errors. It is the right fit for teams whose Linear board gets cluttered with the same crash filed repeatedly and who want a single living ticket per root cause.
How it works
- 1Sentry fires when a resolved issue regresses or reopens.
- 2The agent searches Linear for an existing ticket tied to the issue's fingerprint.
- 3A branch checks whether a matching ticket was found.
- 4If found, an OpenAI model writes a recurrence note and it is added as a Linear comment.
- 5If not found, a new Linear bug is created with the full context as the fallback output.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.