ENGINEERING
Sentry error-spike to auto-filed Linear bug
Watches Sentry for a sudden jump in a new or regressed issue's event rate and files a deduplicated Linear bug with the stack trace, affected release, and a direct Sentry link.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry issue-alert webhook fires on event-rate spikeSentry
- LogicFilter out sub-threshold and already-resolved issues
- ActionSearch Linear for existing ticket by Sentry issue IDLinear
- LogicBranch: skip if duplicate, continue if new
- ActionCreate Linear bug with stack trace, release, and Sentry linkLinear
- OutputComment the Linear ticket URL back onto the Sentry issueSentry
What it does
Turns a Sentry error spike into a ready-to-triage Linear ticket automatically, so an engineer never has to manually copy a stack trace into the tracker at 2am.
When to use it
Use it when your on-call rotation lives in Linear and you want every meaningful error regression captured as a tracked bug without watching dashboards. Best for teams that already tag issues with a service or team owner in Sentry.
How it works
- 1Sentry fires its issue-alert webhook when an issue's event frequency crosses your configured threshold.
- 2A filter drops anything below the spike count or flagged as already-resolved, so noise never reaches the tracker.
- 3The flow searches Linear for an existing ticket carrying the Sentry issue ID to avoid duplicates.
- 4If none exists, it creates a Linear issue with the culprit, stack trace, first/last seen, affected release, and a deep link back to Sentry.
- 5It posts the new ticket URL back as a Sentry comment so both systems stay cross-linked.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.