DEVOPS
Vercel Build-Duration Creep Watchdog
Records every production build's duration in a time-series store and, when a rolling-window regression is detected, posts the slowest recent commits to the offending PR as bisect…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment succeeded webhookVercel
- ActionAppend build duration + SHA to time-series tablePostgres
- LogicCompute rolling median; flag if +25% over baseline
- ActionFetch commits since last clean baselineGitHub
- OutputPost ranked bisect-candidate comment on PRGitHub
What it does
Every time Vercel finishes a production build, this workflow logs the build duration, compares it against a rolling baseline, and detects creeping slowdowns before they become a 10-minute deploy. When the trend crosses a threshold, it comments on the triggering pull request with a ranked list of recent commits to bisect.
When to use it
Use it when your Vercel build times have been quietly climbing and nobody can point to a single bad commit. Ideal for teams that want an early warning on build regressions instead of discovering them during a release crunch.
How it works
- 1A Vercel deployment-succeeded webhook fires with build metadata.
- 2The duration and commit SHA are appended to a Postgres time-series table.
- 3A logic step computes the rolling 20-build median and flags a regression if the latest build exceeds it by more than 25 percent.
- 4If flagged, the workflow pulls the commits merged since the last clean baseline from GitHub.
- 5It ranks them and posts a bisect-candidate comment on the associated PR.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.