DEVOPS

Flag runaway preview build minutes per branch

Runs on a schedule, tallies Vercel preview build minutes grouped by branch over the last 24 hours.

CategoryDevOps
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEvery 4 hours
  • ActionList Vercel deployments (last 24h)VercelVercel
  • LogicGroup and sum build minutes per branch
  • LogicKeep branches over budget threshold
  • OutputPost over-budget branch report to SlackSlack

What it does

This workflow watches your Vercel preview build-minute consumption and catches the one branch quietly burning your monthly budget. On a fixed schedule it pulls recent deployments, sums build duration per Git branch, and raises a Slack alert for any branch that exceeds the minute threshold you set.

When to use it

Use it when a team ships many preview deploys and a noisy branch (rebuild loops, oversized monorepo builds, a stuck CI retry) can silently consume thousands of build minutes. Runs unattended so you catch the overage mid-month, not on the invoice.

How it works

  1. 1A schedule fires every few hours.
  2. 2Vercel returns all deployments from the last 24 hours with their build durations and source branch.
  3. 3A logic step groups deployments by branch and sums build minutes per branch.
  4. 4A logic step compares each branch total against your per-branch budget threshold and keeps only the offenders.
  5. 5If any branch is over budget, a Slack message names each branch, its minutes, and a link to its deployments.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect VercelDeploys, runtime logs, analytics.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.