ENGINEERING
Turn Sentry deprecation warnings into scoped Linear issues
Watches Sentry for new deprecation-tagged issues, uses OpenAI to summarize the deprecated API and the recommended replacement, and opens a deduplicated.
How it runs
The automated pipeline, trigger to output.
- TriggerNew deprecation issue in SentrySentry
- LogicFilter to genuine deprecation warnings
- ActionSummarize deprecated API and replacement with OpenAIOpenAI
- LogicCheck Linear for an existing issue by symbolLinear
- OutputCreate or update the scoped Linear issueLinear
What it does
Every time Sentry surfaces a new deprecation warning, this workflow converts it into a clean, scoped Linear issue so deprecations stop piling up as silent breadcrumbs in your event stream. Each issue arrives with the deprecated symbol, the suggested replacement, affected files, and a checklist the assignee can actually work from.
When to use it
Use it when your services emit DeprecationWarnings through Sentry and they currently get ignored until something breaks. Ideal for teams that plan migration work in Linear and want every deprecation tracked instead of rediscovered during an upgrade.
How it works
- 1Sentry fires when a new issue is tagged or fingerprinted as a deprecation.
- 2A filter drops anything that isn't a genuine deprecation (severity, tag, message pattern).
- 3OpenAI reads the stack trace and message, then extracts the deprecated API, the recommended replacement, and a short migration checklist.
- 4The flow checks Linear for an existing open issue keyed on the deprecated symbol to avoid duplicates.
- 5If none exists, it creates a labeled Linear issue with the summary, source links, and checklist; otherwise it appends the new occurrence as a comment.
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 Engineering workflows
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
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.