DATA OPS
Snowflake Table Contract Drift to GitHub Migration PR
On a schedule, snapshots the live schema of tracked Snowflake tables, diffs it against the committed contract.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionQuery Snowflake INFORMATION_SCHEMA for tracked tablesSnowflake
- LogicDiff live schema vs committed contract; stop if no drift
- ActionCommit regenerated contract to a new branchGitHub
- OutputOpen GitHub PR with diff summary and table labelsGitHub
What it does
Keeps a versioned "contract" file for each tracked Snowflake table in your repo and continuously checks that the warehouse still matches it. When the live schema diverges (a column added, dropped, renamed, or retyped), it writes the updated contract and opens a GitHub pull request so the change goes through review instead of landing silently.
When to use it
Use it when analytics or product engineers can ALTER tables faster than your dbt models and downstream consumers can keep up. It turns invisible warehouse drift into a reviewable code change with a clear owner.
How it works
- 1A daily schedule fires the run.
- 2The workflow queries `INFORMATION_SCHEMA.COLUMNS` in Snowflake for every table on the watch list.
- 3It compares the live shape against the checked-in contract YAML and computes a structured diff.
- 4A logic step exits early if the diff is empty — no noise on clean days.
- 5When drift exists, it commits the regenerated contract to a new branch and opens a GitHub PR with the diff summarized in the body and the affected tables labeled.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 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
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.