SUMMARIZATION

Turn a first-seen Sentry signature into a triaged Linear issue

When Sentry detects a brand-new error signature in a release, summarizes its stack trace and impact and opens a Linear issue pre-filled with severity, affected release…

CategorySummarization
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSentry first-seen issue webhookSentrySentry
  • ActionFetch stack trace and impactSentrySentry
  • LogicAbove noise threshold?
  • ActionSummarize and propose severity/ownerOpenAI
  • OutputCreate triaged Linear issueLinearLinear

What it does

This workflow converts genuinely new error signatures into actionable tickets. When Sentry sees a first-seen issue tied to a release, it summarizes the stack trace, event volume, and affected users, then creates a Linear issue with a proposed severity, the offending release version, and a suggested owner based on the touching commit.

When to use it

Use it when new errors slip through because nobody files them. It closes the gap between detection and triage so a fresh signature becomes a tracked, owned issue automatically.

How it works

  1. 1Sentry fires an issue webhook filtered to first-seen events.
  2. 2The flow pulls the stack trace, event count, user impact, and the release that introduced it.
  3. 3A branch suppresses noise below a minimum event-count threshold.
  4. 4An OpenAI step writes a triage summary and proposes severity plus an owner from the suspect commit.
  5. 5A Linear issue is created pre-filled with that context and labeled by release.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SentryErrors, performance, releases.
  2. 2
    Connect LinearIssues, projects, cycles, triage.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.