ENGINEERING
Daily error-budget burn digest across services to Confluence and Slack
Each morning it pulls remaining SLO budget and burn rate for every tracked service from Datadog, ranks them by risk, writes a dated report to Confluence.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires each morning
- ActionQuery Datadog budget + burn per serviceDatadog
- LogicRank services by risk, flag below floor
- ActionPublish dated digest page to ConfluenceConfluence
- OutputPost top at-risk services to SlackSlack
What it does
This workflow produces a single daily snapshot of error-budget health across the whole fleet. It reads each service's remaining budget and current burn rate from Datadog, sorts the services from most to least at risk, publishes a dated page to Confluence for the record, and drops a short summary of the riskiest services into Slack so the team starts the day knowing where the budget is tight.
When to use it
Use this when you run many services with SLOs and want a recurring reliability standup artifact instead of asking everyone to open dashboards. It is reporting, not gating, so it never blocks a deploy.
How it works
- 1A schedule trigger fires once each morning.
- 2The workflow queries Datadog for remaining budget and burn rate per tracked service.
- 3A logic step ranks services by risk and flags any below the warning floor.
- 4It writes a dated digest page to Confluence with the full table.
- 5It posts the top at-risk services and a link to the full page in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 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.