DEVOPS
Page on-call when preview build time spikes anomalously
On a schedule it pushes Vercel preview build durations to Datadog as metrics, queries Datadog for branches whose build time is anomalously high versus baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule
- ActionGet Vercel build durations per branchVercel
- ActionSubmit build minutes as Datadog metricDatadog
- ActionQuery Datadog anomaly monitorDatadog
- LogicKeep confirmed build-time anomalies
- OutputPage on-call via PagerDutyPagerDuty
What it does
This workflow turns preview build minutes into an observable signal. It records each branch's build duration as a Datadog metric, then uses Datadog's anomaly detection to spot branches whose builds have spiked far above their normal baseline, and pages on-call when a runaway build is detected.
When to use it
Use it when a fixed minute threshold is too blunt and you want to catch builds that suddenly balloon relative to their own history, for example a dependency change that 5x's a branch's build time. Best for teams already running Datadog who want preview-cost regressions treated as incidents.
How it works
- 1A schedule fires every hour.
- 2Vercel returns recent preview build durations per branch.
- 3A Datadog action submits each branch's build minutes as a tagged metric.
- 4A Datadog action queries the anomaly monitor for branches exceeding their baseline build time.
- 5A logic step keeps only confirmed anomalies above the sensitivity cutoff.
- 6A PagerDuty action opens an incident for each runaway build with branch and current build minutes.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.