DEVOPS
Weekly GitLab CI Slowest-Stage Cost Digest
Every Monday, scans the past week of GitLab pipeline runs to find the slowest and most expensive CI stages.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery Monday at 8am
- ActionFetch last 7 days of pipeline + job timingsGitLab
- LogicAggregate runner minutes and rank stages by cost
- ActionGenerate caching and runner-tier recommendationsOpenAI
- OutputPost ranked cost digest to SlackSlack
What it does
Produces a weekly leaderboard of your most expensive GitLab CI stages, ranked by total runner minutes consumed, and turns it into plain-English optimization advice your team can act on Monday morning.
When to use it
When your GitLab runner bill keeps climbing and nobody knows which jobs are responsible. Ideal for platform teams who want a recurring, low-effort signal instead of manually digging through pipeline analytics.
How it works
- 1A scheduled trigger fires every Monday at 8am.
- 2The flow queries the GitLab API for all pipelines and job timings from the last 7 days.
- 3A logic step aggregates duration and runner minutes per stage, ranking by total cost and flagging stages with high average duration.
- 4An OpenAI step writes targeted recommendations — e.g. enable dependency caching, split a fat test stage, or downgrade an over-provisioned runner tier.
- 5The final digest, with the top 10 costliest stages and dollar estimates, is posted to a Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect OpenAIModels, embeddings, files.
- 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
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.