DEVOPS
Build-time regression alert against Axiom baseline
On every Vercel deployment-ready webhook, compares the new build duration to the project's 30-day baseline in Axiom and alerts Slack when the build is a statistically significant…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment-ready webhook firesVercel
- ActionWrite build duration event to AxiomAxiom
- ActionQuery Axiom for 30-day baseline statsAxiom
- LogicCompute z-score, branch regression vs normal
- OutputPost regression alert to SlackSlack
What it does
Fires the moment a Vercel deployment finishes building, ships the build duration as an event to Axiom, then queries Axiom for that project's trailing 30-day baseline (mean and standard deviation). If the fresh build exceeds the baseline by more than a configurable number of standard deviations, it raises an alert; otherwise it stays silent.
When to use it
Use it when you want immediate, per-deploy detection of a build slowdown but refuse to drown in false positives. Anchoring to an Axiom baseline means natural variance is tolerated and only genuine regressions page the team.
How it works
- 1A Vercel deployment-ready webhook triggers the flow with the build metadata.
- 2The flow writes the build duration and commit SHA as an event to Axiom.
- 3An Axiom query step pulls the project's 30-day mean and standard deviation.
- 4A logic step computes the z-score and branches: regression vs. normal.
- 5When the build is a significant outlier, the flow posts a Slack alert naming the project, commit, duration, and how many standard deviations over baseline it landed.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect AxiomLog streams, queries, dashboards.
- 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 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.