ENGINEERING
Post Sentry Issue Blast-Radius From Linked Intercom Reports
When a Sentry issue crosses a spike threshold, this gathers every Intercom conversation tied to the same error and posts a blast-radius summary to Slack listing affected…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry issue crosses spike thresholdSentry
- ActionQuery Intercom for conversations on same fingerprintIntercom
- LogicAggregate affected customers and report timeline
- ActionSummarize blast-radiusOpenAI
- OutputPost blast-radius summary to SlackSlack
What it does
When a Sentry issue spikes, it pulls all Intercom conversations whose error fingerprint maps to that issue, builds a blast-radius picture (how many customers, which accounts, first and latest report), and drops a single Slack message so engineering and support share one view of who is impacted.
When to use it
Use it during incidents or noisy regressions when leadership keeps asking "how many customers does this actually affect?" and the answer is scattered across Intercom threads and Sentry counts.
How it works
- 1A Sentry alert fires when an issue's event rate crosses your threshold.
- 2Intercom is queried for open conversations matching the issue's fingerprint.
- 3A logic step aggregates affected customers, account tiers, and report timestamps.
- 4An OpenAI step writes a concise blast-radius summary.
- 5The summary is posted to a Slack incident channel with deep links to Sentry and the Intercom threads.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect IntercomConversations, contacts, articles.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
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.