DATA OPS
Comment on dbt Pull Requests With Upstream Schema Impact
On every dbt repo pull request, cross-checks the changed models against live BigQuery source schemas and posts a PR comment flagging any model that references a column the source…
How it runs
The automated pipeline, trigger to output.
- TriggerPull request opened or updated on dbt repoGitHub
- ActionParse changed models and referenced source columnsGitHub
- ActionQuery live BigQuery source column setsBigQuery
- LogicCollect references to missing or renamed columns
- OutputPost impact comment on the GitHub PRGitHub
What it does
On each pull request to your dbt repository, this checks the models touched in the PR against the current BigQuery source schemas. If a model selects or joins on a column that the upstream source has since dropped or renamed, it posts a clear PR comment so the change is fixed before merge, not after a failed run.
When to use it
Use it when schema drift surfaces as broken builds after merge and you want a pre-merge guardrail in code review. Ideal for analytics teams practicing PR-based dbt development who want CI-time confidence that models still match live sources.
How it works
- 1A GitHub pull-request event triggers the check.
- 2The PR's changed dbt model files are read and their referenced source columns are parsed from the GitHub diff.
- 3BigQuery is queried for the current column set of each referenced source table.
- 4A logic step compares referenced columns against live columns and collects any mismatches.
- 5If mismatches exist, a GitHub PR comment is posted naming each model, the missing column, and the source table.
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.