DEVOPS
Vercel build-minutes daily trend digest to Slack
Each morning, pulls the last 14 days of Vercel build durations, computes the rolling trend per project.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires before standup
- ActionFetch 14 days of build durations from VercelVercel
- LogicGroup by project, compute rolling median and slope
- LogicKeep only projects trending up past noise threshold
- OutputPost ranked build-time digest to SlackSlack
What it does
Runs once a day, reads Vercel deployment build durations for every production project over a trailing 14-day window, and computes a per-project median plus the day-over-day and week-over-week slope. It posts a single Slack digest that ranks projects by how fast their build minutes are growing, so a slow regression surfaces before it becomes a 10-minute build.
When to use it
Use it when build times feel like they are slowly getting worse but no single deploy looks alarming. A daily digest catches gradual creep — a new dependency, an unbundled import, a growing test matrix — that a per-deploy alert would miss.
How it works
- 1A scheduled trigger fires every morning before standup.
- 2The flow calls the Vercel API to list deployments and their build durations across the 14-day window.
- 3A logic step groups by project, computes rolling medians, and ranks projects by upward slope.
- 4A second logic step keeps only projects trending up beyond a noise threshold.
- 5The flow posts a ranked digest to a Slack channel, with the worst offenders and their week-over-week delta at the top.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.