DEVOPS
Build-budget breach opens a Linear issue
When a Vercel project's build crosses its defined compile-minute budget, automatically files a Linear issue with the offending commit, build trend, and a deduped guard so repeat…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment-ready webhook firesVercel
- LogicCompare build duration to project budget, exit if under
- ActionSearch Linear for existing open breach issueLinear
- LogicBranch: update existing vs create new issue
- OutputCreate or comment on Linear breach issueLinear
What it does
Watches Vercel build completions and checks each project's duration against a per-project compile-minute budget you set. When a build blows the budget, it opens a Linear issue tagged to the owning team, pre-filled with the commit, duration, budget, and overage. It first searches Linear for an open breach issue for that project so repeated breaches append a comment rather than creating duplicates.
When to use it
Use it when build slowdowns need to become tracked, ownable work — not just a Slack ping that scrolls away. Turning a budget breach into a Linear ticket makes the regression someone's queue item with a clear acceptance bar: get back under budget.
How it works
- 1A Vercel deployment-ready webhook triggers the flow.
- 2A logic step compares the build duration to the project's configured budget and exits if under.
- 3The flow searches Linear for an existing open breach issue for the project.
- 4A logic step branches: update the existing issue, or create a new one.
- 5The flow writes to Linear — appending a comment with the latest overage, or filing a fresh issue assigned to the owning team.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.