DEVOPS
Weekly Vercel Build-Health Digest with GitLab Offenders
Runs every Monday, summarizes the past week's Vercel build durations into a trend report.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly Monday schedule
- ActionQuery trailing 7-day build-duration historyPostgres
- LogicCompute median, p95, WoW delta, top jumps
- ActionMatch each jump to its GitLab merge requestGitLab
- OutputPublish trend digest to Confluence pageConfluence
What it does
On a weekly schedule, this workflow rolls up the last seven days of Vercel build durations into a digest: median, p95, week-over-week change, and the largest single jumps. It cross-references each jump against GitLab merge requests to name the MR most likely responsible, then publishes the digest to a Confluence page.
When to use it
Use it for a recurring team ritual — a Monday build-health review that keeps build time on the radar without anyone manually pulling numbers. Good for teams on GitLab who want accountability tied to specific merge requests.
How it works
- 1A weekly schedule trigger fires Monday morning.
- 2The workflow queries the build-duration history table for the trailing seven days.
- 3A logic step computes median, p95, week-over-week delta, and the top duration jumps.
- 4For each jump, it fetches the corresponding GitLab merge request that landed nearest that build.
- 5It publishes the assembled trend digest to a Confluence page for the team.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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
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.