DATA OPS
Snowflake Drift Detector that Blocks the dbt Pull Request on GitHub
When a pull request touches dbt models, it compares the models' source columns against the live Snowflake schema and posts a blocking check on the PR if the code references…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub pull request opened or updatedGitHub
- ActionRead changed dbt models and extract referenced columnsGitHub
- ActionQuery live source schema from SnowflakeSnowflake
- LogicCompare referenced columns to live schema; pass or fail
- OutputPost blocking check status on the GitHub PRGitHub
What it does
This sentinel runs at code-review time instead of runtime. When a dbt pull request opens, it parses the source columns the changed models depend on, queries Snowflake's `INFORMATION_SCHEMA` for the real current shape of those tables, and fails the PR check if the code assumes columns that upstream has dropped or retyped. Reviewers see the exact mismatch inline.
When to use it
Use it when your transformation code and your upstream warehouse evolve on different schedules and you want drift caught before merge, not in a 2 a.m. pager. Ideal for teams enforcing a data-contract gate in CI.
How it works
- 1A GitHub pull-request opened/synchronized event triggers the flow.
- 2Read the changed dbt model files from the PR to extract referenced source tables and columns.
- 3Query Snowflake `INFORMATION_SCHEMA.COLUMNS` for the live shape of those source tables.
- 4Branch: every referenced column exists with a compatible type -> pass; otherwise -> fail.
- 5Post a commit status / check back to the GitHub PR (success or blocking failure with the mismatch list).
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 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.