DEVOPS
Monthly GitLab CI Carbon Footprint Report
At month end, estimates the carbon footprint of your GitLab CI runner minutes by region and project.
How it runs
The automated pipeline, trigger to output.
- TriggerFirst of the month schedule
- ActionPull prior-month runner minutes by project/regionGitLab
- LogicEstimate CO2 from minutes x grid intensity
- ActionRank emitters and draft reduction leversOpenAI
- OutputPublish carbon report to NotionNotion
What it does
Converts a month of GitLab runner usage into estimated CO2 emissions, broken down by project and runner region, and publishes a clear sustainability report highlighting which pipelines emit the most and how to cut it.
When to use it
When you need to report engineering carbon for an ESG goal, or want to make the environmental cost of inefficient CI visible alongside the dollar cost. Pairs well with caching and scheduling initiatives.
How it works
- 1A scheduled trigger fires on the first of each month.
- 2The flow pulls the prior month's runner minutes per project and region from the GitLab API.
- 3A logic step multiplies minutes by region-specific grid carbon intensity to estimate kilograms of CO2 per project.
- 4An OpenAI step ranks the top emitters and drafts reduction levers — caching, off-peak scheduling, greener runner regions.
- 5The formatted report is published as a new Notion page for stakeholders.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 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.