DATA OPS
PR-time schema-contract check for BigQuery loads
On every pull request that touches an ingestion schema file, validates the proposed columns against the live BigQuery table and posts a pass/fail comment on the PR before merge.
How it runs
The automated pipeline, trigger to output.
- TriggerPull request edits a schema fileGitHub
- ActionRead proposed schema from PR diffGitHub
- ActionFetch live table columns from BigQueryBigQuery
- LogicClassify diff as additive or breaking
- OutputComment verdict and set commit status on the PRGitHub
What it does
Shifts drift detection left into code review. When a developer opens a PR that edits a schema or loader config, this validates the proposed column set against what currently exists in BigQuery and comments directly on the PR — green if the change is additive and safe, red with specifics if it would drop or retype a column live data depends on.
When to use it
Schema changes go through PRs but reviewers can't eyeball whether a change is backward-compatible with the deployed table. You want an automated gate that flags breaking changes before merge rather than after deploy.
How it works
- 1A GitHub pull-request event triggers when schema files change.
- 2Read the proposed schema from the PR diff.
- 3Query the live BigQuery table's current columns and types.
- 4A logic step classifies the diff: additive (safe), or destructive/incompatible (breaking).
- 5Post a PR comment with the verdict and the specific offending columns.
- 6Set the commit status to success or failure to gate 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
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 orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
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.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
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.
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…
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.