DEVOPS
Vercel Build-Budget Breach PR Gate
When a preview build exceeds the agreed build-time budget, posts a failing check and a comment on the PR explaining the overage and which dependency or file change likely caused…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment succeeded webhookVercel
- LogicCompare duration against per-branch build budget
- ActionInspect PR diff for heavy deps / large filesGitHub
- OutputSet failing check + post overage comment on PRGitHub
What it does
This workflow enforces a build-time budget on pull requests. When a Vercel preview build for a PR exceeds the configured budget, it sets a failing commit status and comments on the PR with the overage amount and a diff-based guess at the cause — a new heavy dependency, a large new file, or expanded type-check scope.
When to use it
Use it to stop build-time regressions at review time rather than after merge. Ideal for teams that treat build duration as a budget with a hard ceiling and want PRs blocked when they blow past it.
How it works
- 1A Vercel preview-deployment-succeeded webhook fires for a PR build.
- 2A logic step compares the build duration against the per-branch budget.
- 3If within budget, it sets a passing check and exits.
- 4If over budget, it inspects the PR diff for added dependencies and large files via GitHub.
- 5It posts a failing commit status plus an explanatory PR comment naming the likely culprit and the overage in seconds.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.