DATA OPS
Nightly Snowflake schema drift watcher with Linear migration ticket
Every night, snapshots the column-level schema of your tracked Snowflake tables, diffs it against yesterday's snapshot.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionQuery INFORMATION_SCHEMA.COLUMNS for tracked tablesSnowflake
- ActionLoad prior snapshot baselinePostgres
- LogicDiff columns; classify additive vs breaking
- ActionOpen Linear migration ticket on breaking changeLinear
- OutputPersist new snapshot as next baselinePostgres
What it does
This workflow keeps a running fingerprint of every tracked Snowflake table's columns, types, and nullability. Each night it compares the fresh fingerprint to the last stored one. Additive changes (new nullable columns) are logged quietly; breaking changes — a dropped column, a narrowed type, or a column that became NOT NULL — open a Linear ticket so a migration is scheduled before downstream jobs break.
When to use it
Use it when upstream tables are owned by another team or a third-party ELT tool and change without warning, and your dbt models or BI dashboards silently break the next morning. It turns a 9am Slack fire drill into a triaged ticket waiting in your sprint.
How it works
- 1A nightly schedule fires the run.
- 2It queries `INFORMATION_SCHEMA.COLUMNS` in Snowflake for every tracked table.
- 3It loads the previous snapshot from Postgres and diffs column names, types, and nullability.
- 4A logic step classifies each change as additive or breaking.
- 5If any breaking change exists, it opens a Linear issue with the table, the diff, and a suggested migration.
- 6It writes the new snapshot back to Postgres as the next baseline.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.