DATA OPS
Weekly Snowflake Schema-Change Digest to Notion and Slack
Runs weekly, collects every column add, drop, and type change across watched Snowflake schemas.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires on Monday morning
- ActionRead current schema fingerprint from SnowflakeSnowflake
- ActionLoad last week's fingerprint from PostgresPostgres
- LogicDiff weekly fingerprints and build changelog
- ActionAppend changelog to Notion pageNotion
- OutputPost highlights and link to SlackSlack
What it does
Not every schema change is an emergency, but they all need an audit trail. This sentinel accumulates a week of column-level changes across your watched Snowflake schemas — comparing weekly fingerprints — and rolls them into one tidy changelog: what changed, in which table, and when first seen. It writes the changelog to a Notion page your team can review and posts a short summary to Slack.
When to use it
Use it for governance and review cadence rather than incident response. It gives data and analytics teams a recurring, searchable record of how their warehouse evolved, useful for weekly data-platform standups and audits.
How it works
- 1A weekly schedule fires (e.g. Monday morning).
- 2Query Snowflake `INFORMATION_SCHEMA.COLUMNS` across the watched schemas for the current fingerprint.
- 3Compare against last week's fingerprint stored in Postgres; assemble the full list of adds, drops, and type changes.
- 4Format the changes into a dated changelog section.
- 5Append the changelog to the team's Notion page.
- 6Post a highlights summary with a link to Slack and store the new fingerprint.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect NotionPages, databases, comments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
Snowflake column type-drift sentinel with Linear fix ticket
Snapshots the data types of every column in your tracked Snowflake schemas on a schedule, diffs against the last snapshot.
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 dropped/renamed column sentinel with PagerDuty incident
Detects when a column is dropped or renamed in your governed BigQuery datasets and, because that breaks downstream queries hard, pages the on-call via PagerDuty and posts…
PR-time Snowflake schema contract check on dbt model changes
When a pull request changes a dbt model, it compares the model's declared output columns against the live Snowflake table it will replace and blocks the merge with a GitHub check…
Agent-triaged warehouse drift with impact analysis and runbook update
On a webhook from your warehouse audit log, an agent investigates the changed column, traces which downstream models and dashboards depend on it.
Cross-warehouse replication schema mismatch reconciler
Compares the column shape of mirrored tables between BigQuery and Snowflake and, when a replicated table has drifted out of sync between the two, opens an Asana task for the data…
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.