DATA OPS
Snowflake Schema-Drift Guard: Block Breaking Column Changes
Polls Snowflake INFORMATION_SCHEMA on a schedule, diffs the live column layout against a stored contract snapshot, and posts a ranked Slack alert the moment a column is dropped.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires (every 30 min)
- ActionQuery INFORMATION_SCHEMA.COLUMNS for watched schemasSnowflake
- ActionLoad last accepted contract snapshotPostgres
- LogicDiff layouts; classify additive vs. breaking
- ActionPersist new snapshot when no breaking changePostgres
- OutputPost breaking-change alert to SlackSlack
What it does
Keeps a saved "contract" of every column in your governed Snowflake schemas (name, type, nullability, ordinal) and compares the live catalog against it on each run. Additive changes (new nullable columns) pass silently; breaking changes (dropped column, type narrowed, NOT NULL added) raise an alert with the exact table and column named.
When to use it
When downstream dashboards, reverse-ETL syncs, or ML features read directly from warehouse tables and a silent column drop would break them hours before anyone notices. Ideal for a central data-platform team enforcing change discipline on shared marts.
How it works
- 1A schedule fires the run (e.g. every 30 minutes).
- 2Query `INFORMATION_SCHEMA.COLUMNS` in Snowflake for the watched schemas to get the current layout.
- 3Load the last accepted contract snapshot from Postgres.
- 4Logic step diffs the two: classify each change as additive, breaking, or none.
- 5If no breaking changes, persist the new snapshot to Postgres and exit.
- 6On a breaking change, post a Slack message listing each violation, its severity, and the prior vs. current definition.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.