DEVOPS
Page the owning service team when projected month-end spend breaches its budget
Hourly it projects each service's month-end spend from BigQuery run-rate, and for any service tracking to blow past its budget it pages the owning team via PagerDuty and opens…
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule
- ActionProject month-end spend per serviceBigQuery
- LogicKeep services projected to breach budget
- ActionPage owning team's escalation policyPagerDuty
- OutputOpen GitLab issue with burn-down detailGitLab
What it does
Projects where each service's monthly cloud spend will land based on current run-rate, compares that projection to the service's budget, and escalates only the services on track to breach. Breaches page the owning on-call team in PagerDuty and open a tracking issue in GitLab so the overrun has both an immediate responder and a paper trail.
When to use it
Use it when teams have explicit monthly cloud budgets and a late-month surprise is unacceptable. Best for orgs that want proactive, owner-targeted escalation rather than a reactive end-of-month review.
How it works
- 1An hourly schedule triggers the projection run.
- 2A BigQuery query computes month-to-date spend per service and projects month-end via run-rate.
- 3A logic step compares each projection to the service's budget and keeps only those projected to breach by a meaningful margin.
- 4For each breach, an action triggers a PagerDuty incident routed to the owning service's escalation policy.
- 5An output step opens a GitLab issue in the owning repo with the projection, budget, and contributing cost lines, linked to the incident.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect GitLabRepos, MRs, pipelines, registry.
- 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.