DEVOPS
Catch BigQuery scheduled-query cost regressions and file a tuning ticket
Daily compares each scheduled query's bytes billed to its 7-day baseline and, when a job's cost jumps past the regression threshold, opens an Asana tuning task and alerts Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionRead per-job bytes billed for yesterday and prior 7 daysBigQuery
- LogicCompute baseline and flag cost regressions
- ActionCreate Asana tuning task per regressionAsana
- OutputPost regression summary to SlackSlack
What it does
It watches your recurring BigQuery scheduled queries for cost creep. Each day it pulls per-job bytes billed, compares every scheduled query against its own trailing 7-day average, and flags any job whose cost jumped beyond a regression threshold, usually because an underlying table grew or a filter broke. Each regression becomes an Asana task and a Slack alert.
When to use it
Use it when scheduled queries are your main spend and a single one quietly doubling in cost would otherwise go unnoticed for weeks. Baseline comparison catches relative regressions that a flat budget threshold misses.
How it works
- 1A daily schedule triggers the flow.
- 2A BigQuery query reads per-scheduled-job bytes billed for yesterday and the prior 7 days.
- 3A logic step computes each job's baseline and flags jobs over the regression threshold.
- 4For each regression, an Asana task is created with the job name, baseline, and new cost.
- 5A summary of regressions is posted to Slack for the data platform team.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect AsanaTasks, projects, milestones — everywhere.
- 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.