DATA OPS
Open a GitHub Issue When a BigQuery Source Table Breaks dbt Models
Watches BigQuery source table schemas daily and, when a breaking change like a dropped or retyped column is detected, opens a GitHub issue on the analytics repo tagging…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule starts schema check
- ActionFetch BigQuery source table metadataBigQuery
- LogicKeep only breaking changes (dropped or retyped columns)
- ActionResolve dependent dbt models and owners
- OutputOpen assigned GitHub issue on the analytics repoGitHub
What it does
Monitors BigQuery source tables for breaking schema changes and files a tracked GitHub issue against your analytics repository whenever one appears. The issue names the table, the exact change, and the dbt models that reference it, with owners assigned so the work lands in someone's queue.
When to use it
Use it when your team manages drift through pull requests and issues rather than chat pings, and you want a durable, assignable record instead of a Slack message that scrolls away. Best for breaking changes that demand a code fix.
How it works
- 1A daily schedule kicks off the schema check.
- 2BigQuery's table metadata is fetched for each registered source table.
- 3A logic step classifies the diff and keeps only breaking changes — dropped columns or incompatible type changes — discarding additive ones.
- 4For each breaking change, the dependent dbt models and their owners are looked up.
- 5A GitHub issue is opened on the analytics repo with the diff, impacted models, and owners assigned as assignees and labels.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.