ENGINEERING
Auto-file a budget-breach postmortem ticket when an SLO blows its window
When a Honeycomb SLO exhausts its error budget for the compliance window, it creates a Linear postmortem issue pre-filled with the burn timeline and recent Vercel deploys.
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb SLO budget-exhausted webhookHoneycomb
- ActionPull burn-rate timeline from HoneycombHoneycomb
- ActionList Vercel deploys in the breach windowVercel
- ActionCreate pre-filled Linear postmortem issueLinear
- OutputNotify owning team in SlackSlack
What it does
Makes budget breaches automatically accountable. When a Honeycomb SLO burns through its budget for the full compliance window, this workflow assembles the context an investigator needs: the burn timeline from Honeycomb and the list of Vercel production deploys in that window. It files a Linear postmortem issue with that evidence attached and assigns it to the service owner.
When to use it
Use it when your team commits to a postmortem for every error-budget breach and you want the paperwork started automatically with real data instead of a blank template days later. Good for teams with an SLO review cadence.
How it works
- 1A Honeycomb SLO budget-exhausted webhook triggers the flow.
- 2The workflow pulls the burn-rate timeline for the breached window from Honeycomb.
- 3It queries the Vercel API for production deployments during that window.
- 4It creates a Linear postmortem issue pre-filled with the timeline, suspect deploys, and owner assignment.
- 5It posts a Slack note linking the new postmortem issue to the owning team.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Connect LinearIssues, projects, cycles, triage.
- 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
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.
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.
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.
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…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.