DEVOPS
Pre-deploy budget gate that blocks preview builds when the team is over quota
Exposes a webhook the CI pipeline calls before triggering a Vercel preview build; it checks remaining build-minute headroom and returns an allow or deny decision.
How it runs
The automated pipeline, trigger to output.
- TriggerCI calls budget-gate HTTP webhook pre-deployHTTP webhook
- ActionRead month-to-date usage and capPostgres
- LogicApply policy: protected branch or enough headroom?
- ActionRecord gate decision for reportingPostgres
- OutputReturn allow/deny decision to CIHTTP webhook
What it does
Acts as a gate the CI pipeline asks before it spends build minutes. Given the branch and remaining month, it checks the team's headroom against the monthly cap and answers allow or deny, so low-priority preview builds stop automatically when the budget is nearly exhausted.
When to use it
Use it in the final days of a billing cycle when you want production and release branches to keep deploying but are willing to pause routine feature-branch previews to avoid overage charges. The gate makes that policy automatic instead of a manual freeze.
How it works
- 1The CI step calls the gate's HTTP webhook with the branch name and deploy context before triggering Vercel.
- 2The flow reads month-to-date build-minute consumption and the configured cap from Postgres.
- 3A logic step computes remaining headroom and applies policy: protected branches always pass, others are denied once headroom drops below the reserve.
- 4It records the decision and the requesting branch to Postgres for reporting.
- 5It returns an allow or deny response to the caller, including the reason and remaining headroom, which CI uses to proceed or skip the deploy.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.