ENGINEERING
Weekly Error-Budget Burn Report to Notion
Each week, pulls every service's Honeycomb SLO burn and remaining budget, then writes a ranked summary page to Notion and posts the worst offenders to Slack for the engineering…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly scheduled report run
- ActionPull 7-day burn and remaining budget from HoneycombHoneycomb
- LogicRank services by budget consumed; tag at-risk
- ActionWrite ranked summary page to NotionNotion
- OutputPost worst offenders to SlackSlack
What it does
Produces the weekly error-budget readout so teams stop digging through dashboards before their reliability review. It collects each tracked service's burn rate and remaining budget from Honeycomb over the trailing week, ranks services by budget consumed, and publishes a formatted Notion page with the table and trend. It then posts the top burn offenders to Slack so the review starts with the right discussion.
When to use it
Use it for a recurring reliability or SRE review where you want a consistent, shareable artifact of how each service's error budget is trending — and a nudge in Slack for the ones that need attention.
How it works
- 1A weekly schedule kicks off the report.
- 2The flow queries trailing-7-day burn and remaining budget for all SLOs from Honeycomb.
- 3A logic step ranks services by budget consumed and tags any below the safe-remaining line.
- 4It writes a formatted summary page to Notion with the ranked table.
- 5It posts the worst offenders to Slack for the review.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect NotionPages, databases, comments.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.