DEVOPS
Vercel Build-Anomaly PagerDuty Escalation
Detects a sudden build-duration spike (not a slow creep) on the main branch, opens a PagerDuty incident.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel production deployment succeeded webhookVercel
- LogicFlag anomaly if duration > 2x trailing-5 median
- ActionFetch merge commit + recent build historyPostgres
- OutputOpen PagerDuty incident with suspect commit attachedPagerDuty
What it does
This workflow catches abrupt build-time spikes on the main branch — a build that suddenly doubles, not a gradual creep. On detection it opens a PagerDuty incident, attaches the suspect merge commit, recent build history, and a one-line summary so the on-call engineer can act immediately.
When to use it
Use it when main-branch build health is release-critical and a sudden spike warrants a page, not a Slack message. Complements the gradual-creep watchdog by handling the sharp, urgent case.
How it works
- 1A Vercel production deployment-succeeded webhook fires on a main-branch build.
- 2A logic step flags an anomaly if duration is more than double the trailing-5-build median.
- 3If anomalous, it fetches the merge commit and last several build records from the history table.
- 4It opens a PagerDuty incident with severity scaled to the spike size.
- 5It attaches the suspect commit, build history, and summary to the incident for the on-call.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.