DATA OPS
BigQuery Schema Drift Detector
Snapshots BigQuery dataset schemas daily and diffs them against the last known-good snapshot, opening a Linear issue for the owning team when columns are added, dropped…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily after load window
- ActionRead current column schema from BigQueryBigQuery
- ActionLoad prior snapshot from PostgresPostgres
- LogicDiff and classify breaking vs additive
- ActionOpen Linear issue for breaking changesLinear
- OutputWrite new snapshot back to PostgresPostgres
What it does
Captures the column list and types for every table in a watched BigQuery dataset, stores the snapshot, and compares it to yesterday's. When a column is dropped, renamed, retyped, or added, it classifies the change as breaking or additive and files a tracked issue so a producer change can't quietly break a downstream consumer.
When to use it
When upstream teams ship schema changes without warning the analytics or ML teams who consume those tables, causing pipeline failures or silently wrong joins. Use it to turn schema drift into a reviewable ticket instead of a 2am incident.
How it works
- 1A daily schedule fires after the main load window.
- 2The flow pulls INFORMATION_SCHEMA columns for the watched dataset from BigQuery.
- 3It loads the prior snapshot from Postgres and diffs column names and types.
- 4A logic step splits changes into breaking (drop/retype) versus additive (new nullable column).
- 5Breaking changes open a Linear issue assigned to the table owner with the exact diff; the new snapshot is written back to Postgres for the next run.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect LinearIssues, projects, cycles, triage.
- 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 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.