DATA OPS
BigQuery Cost Guard on Pull Request
On every pull request that touches a scheduled query, it dry-runs the new SQL against BigQuery, compares estimated bytes scanned to the base branch.
How it runs
The automated pipeline, trigger to output.
- TriggerPull request touches query filesGitHub
- ActionFetch head and base SQLGitHub
- ActionBigQuery dry-run estimates bytes each versionBigQuery
- LogicCompute delta, decide pass/fail
- OutputPost blocking check + comment to PRGitHub
What it does
Catches BigQuery cost regressions before they merge: on a pull request it dry-runs both the changed and base-branch SQL, compares estimated bytes processed, and posts a pass/fail check with the cost delta.
When to use it
When scheduled queries live in a Git repo and you want a guardrail that stops a partition-killing change from ever reaching production, rather than detecting it the next morning.
How it works
- 1A GitHub pull request event triggers the run when files under your queries directory change.
- 2A GitHub action fetches the changed SQL from the PR head and the matching SQL from the base branch.
- 3A BigQuery dry-run estimates bytes processed for each version without running the query.
- 4A logic step computes the percent increase and decides pass or fail against your budget tolerance.
- 5A GitHub action posts a check status and a comment showing estimated bytes before and after.
- 6On a material regression the check fails and blocks the merge.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
Weekly BigQuery Cost Trend Sheet and Exec Digest
Compiles week-over-week BigQuery scheduled-query cost by owner and dataset into a Google Sheet with trend columns.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
BigQuery Per-Team Budget Breach Alert to PagerDuty
Tracks month-to-date BigQuery scheduled-query spend per team and, when a team crosses its monthly budget, pages the team's on-call in PagerDuty and snapshots the spend breakdown…
dbt source freshness watcher with severity-routed alerts
Checks Snowflake loaded-at timestamps against each dbt source's freshness SLA, then routes warnings to Slack and hard breaches to a PagerDuty incident so stale data never…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Raw Sensor Telemetry Archive to BigQuery
Captures every incoming building sensor reading via webhook, normalizes the payload into a consistent schema.
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.