DEVOPS
Throttle preview deploys for branches that overrun their build-minute budget
Watches Vercel deployment events and, when a single branch burns more than its allotted build minutes in a rolling window, cancels in-flight preview builds for that branch…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment.created webhook firesVercel
- ActionRead rolling build-minute total for branchPostgres
- LogicIs branch over its build-minute budget?
- ActionCancel in-flight preview deploymentVercel
- ActionRecord throttle event to audit tablePostgres
- OutputDM branch owner the cancellation reasonSlack
What it does
Caps the damage from a branch that redeploys on every push. It tracks build minutes consumed per branch over a rolling window, and once a branch crosses its budget it cancels the current preview build on Vercel and notifies the person who pushed it.
When to use it
Use it when one feature branch (or a misconfigured CI loop) quietly eats your monthly Vercel build minutes through dozens of preview rebuilds. Instead of finding out on the invoice, you stop the bleed in real time and tell the owner why.
How it works
- 1A Vercel deployment-created webhook fires on every new preview build.
- 2The flow reads recent build-minute totals for that branch from Postgres and adds the new build's estimate.
- 3A logic branch checks the running total against the branch's budget; under budget, it just records the build and exits.
- 4Over budget, it calls the Vercel API to cancel the in-flight deployment.
- 5It writes the throttle event back to Postgres for the audit trail.
- 6It posts a Slack DM to the branch owner naming the branch, minutes used, and that the build was cancelled.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.