DATA OPS
Snowflake Schema-Drift Sentinel with Data-Contract Review
Snapshots Snowflake table definitions on a schedule, diffs them against the last known-good version, and opens a ClickUp data-contract review task whenever columns are added.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionRead column definitions from Snowflake INFORMATION_SCHEMASnowflake
- ActionLoad prior snapshot and diff in PostgresPostgres
- LogicBranch: additive-only passes, breaking change continues
- ActionOpen ClickUp data-contract review task with diffClickUp
- OutputPost breaking-change summary to SlackSlack
What it does
It watches the structure of your warehouse tables and catches drift before a downstream dashboard or model silently breaks. Every run it reads the current column definitions from Snowflake's `INFORMATION_SCHEMA`, compares them to the snapshot it stored last time, and classifies what changed. Additive-only changes (a new nullable column) are logged and ignored; breaking changes (dropped column, type narrowing, nullability tightening) open a review task and ping the team.
When to use it
Use it when analytics engineers don't own every pipeline writing to the warehouse and an upstream `ALTER TABLE` can break a dbt model or BI report hours later. Run it nightly over your `ANALYTICS` or `RAW` schemas so a contract owner reviews each structural change deliberately instead of discovering it from a red dashboard.
How it works
- 1A nightly schedule fires the sentinel.
- 2Query Snowflake `INFORMATION_SCHEMA.COLUMNS` for the watched schema's full column list.
- 3Diff the result against the prior snapshot persisted in Postgres.
- 4Branch: if only additive changes, log and stop; if any breaking change, continue.
- 5Open a ClickUp task tagged `data-contract` with the exact column diff.
- 6Post the breaking-change summary to the data team's Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect ClickUpDocs + tasks + chats in one workspace.
- 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
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.