DEVOPS
Page on-call when BigQuery daily spend breaches the budget
Polls BigQuery job costs on a schedule, and when cumulative daily bytes billed crosses the budget it pages PagerDuty and posts the top contributors to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerFrequent schedule (e.g. every 30 min)
- ActionSum today's bytes billed across jobsBigQuery
- LogicCompare running spend to daily budget
- ActionOpen PagerDuty incident on breachPagerDuty
- OutputPost top contributors to SlackSlack
What it does
It watches running spend, not individual queries. On a regular schedule it sums today's bytes billed across all BigQuery jobs, and when the cumulative total crosses your daily budget it fires a PagerDuty incident and posts the queries driving the breach to Slack so on-call can react immediately.
When to use it
Use it when a runaway backfill or a broken scheduled query can burn a day's budget in an hour and you need a real-time alarm, not a next-morning report. It protects against acute cost spikes rather than slow drift.
How it works
- 1A frequent schedule triggers the flow throughout the day.
- 2A BigQuery query sums today's bytes billed across all jobs.
- 3A logic step compares the running total to the daily budget.
- 4If breached, a PagerDuty incident is opened with the current spend and threshold.
- 5The top contributing queries are posted to Slack so on-call can identify and stop the culprit.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.