DEVOPS
Daily deploy-vs-error-budget scorecard to Axiom and Slack
Each morning it joins yesterday's Vercel deployments with Sentry error data, writes a per-release reliability record to Axiom.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: every morning
- ActionList yesterday's Vercel production deploymentsVercel
- ActionQuery Sentry error volume per release windowSentry
- LogicCompute budget consumed and rank deploys
- ActionWrite per-release reliability records to AxiomAxiom
- OutputPost ranked scorecard digest to SlackSlack
What it does
Builds a daily reliability scorecard that attributes error-budget spend to specific releases. It gathers the prior day's Vercel production deployments, pulls Sentry error counts in each release's window, computes the budget consumed per deploy, streams those records into Axiom for long-term trend analysis, and posts a ranked digest to Slack.
When to use it
Use it for engineering reviews when you want a defensible answer to "which changes are hurting reliability" and a durable dataset in Axiom to trend deploy quality over weeks and months.
How it works
- 1A morning schedule kicks off the run.
- 2The flow lists yesterday's Vercel production deployments.
- 3For each release it queries Sentry for error volume in that deploy's active window.
- 4Logic computes error-budget consumed and ranks deploys worst to best.
- 5It writes one structured reliability record per release to Axiom.
- 6It posts the ranked scorecard digest to the engineering Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect SentryErrors, performance, releases.
- 3Connect AxiomLog streams, queries, dashboards.
- 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 DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.