DATA OPS
Detect Snowflake Column Changes and Alert dbt Model Owners in Slack
Hourly snapshots each watched Snowflake source table's INFORMATION_SCHEMA, diffs it against the last snapshot, and posts a Slack alert to the owning team when columns are added.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule starts drift sweep
- ActionQuery Snowflake INFORMATION_SCHEMA for watched tablesSnowflake
- ActionDiff against prior snapshot in Postgres and update itPostgres
- LogicSkip if no column changes detected
- OutputPost column-level diff to owning team's Slack channelSlack
What it does
Snapshots the column inventory of your upstream Snowflake source tables and compares each run to the previous one. When a column is added, dropped, renamed, or changes data type, it notifies the dbt model owner who depends on that table so they can react before a downstream build breaks.
When to use it
Use it when raw source tables are owned by upstream teams who ship changes without warning, and your dbt staging models silently break or drift. It turns surprise schema changes into a proactive heads-up the same hour they land.
How it works
- 1A schedule fires hourly to begin a drift sweep.
- 2Snowflake is queried against INFORMATION_SCHEMA.COLUMNS for every watched source table, capturing column name, type, and nullability.
- 3The current snapshot is diffed against the prior snapshot stored in Postgres; the prior state is then overwritten.
- 4A logic step filters out runs with no changes so quiet hours stay silent.
- 5For each changed table, the owner is resolved from an ownership map and a Slack message is posted to their channel listing exact column-level diffs and the affected dbt models.
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.