DEVOPS
Reap Previews When Vercel Spend Crosses a Budget Threshold
When monthly Vercel usage exceeds a budget alert, ranks live preview deployments by age and cost, posts a teardown plan to Slack for one-click approval.
How it runs
The automated pipeline, trigger to output.
- TriggerBudget-threshold webhook firesHTTP webhook
- ActionList previews with age + usageVercel
- LogicRank + build teardown plan to target
- ActionPost plan to Slack for approvalSlack
- LogicBranch on approve vs skip
- OutputDelete approved previews, report savingsVercel
What it does
Treats preview cleanup as a budget control. When Vercel spend trips a threshold, it assembles a ranked teardown plan of the oldest, costliest previews and asks an operator to approve before reaping, so cost is reined in deliberately rather than blindly.
When to use it
When preview environments are a real line item and you want spend-driven cleanup with a human in the loop, rather than a fixed TTL. Ideal for teams that batch-clean only when they are actually over budget.
How it works
- 1A budget webhook (from your billing alert) fires when Vercel spend crosses the threshold.
- 2List all live preview deployments with age and resource usage from the Vercel API.
- 3Logic ranks previews oldest-and-costliest first and builds a teardown candidate list down to the target savings.
- 4Post the ranked plan to Slack with approve/skip controls and wait for an operator decision.
- 5A branch proceeds only on approval; a skip ends the run with the plan logged.
- 6Delete the approved previews via the Vercel API and post the realized savings summary back to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect VercelDeploys, runtime logs, analytics.
- 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
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.