DEVOPS
Alert PagerDuty on Vercel build-time regression
On each successful deploy, records build duration to BigQuery and pages on-call via PagerDuty when build time spikes above the rolling average by the configured margin.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment succeededVercel
- ActionRecord build duration to BigQueryBigQuery
- ActionQuery rolling average build timeBigQuery
- LogicBranch on duration spike vs margin
- OutputOpen PagerDuty incidentPagerDuty
What it does
This workflow watches build duration, not just bundle size. After every Vercel deploy it records the build time to BigQuery, compares it against the rolling average of recent builds for the same branch, and if the duration spikes beyond the configured margin it opens a PagerDuty incident so on-call can investigate before slow builds choke the deploy pipeline.
When to use it
Use it when build times are creeping up and starting to hurt developer velocity or CI cost, and you want a real alert (not a buried metric) the moment a deploy takes meaningfully longer than normal.
How it works
- 1Vercel `deployment.succeeded` webhook fires with build timing data.
- 2Insert the build duration, branch, and SHA into BigQuery.
- 3Query the rolling average build time for that branch.
- 4Branch: if duration exceeds the average by the margin, escalate; else stop.
- 5Open a PagerDuty incident with the deploy, duration, and delta details.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BigQueryDatasets, queries, schemas.
- 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.