DATA OPS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionRead column types from Snowflake INFORMATION_SCHEMASnowflake
- LogicDiff current column signatures vs stored snapshot
- LogicStop if no type drift detected
- ActionPost drift summary to SlackSlack
- OutputOpen Linear fix ticket per drifted columnLinear
What it does
It watches the physical shape of your Snowflake tables. Every run it reads `INFORMATION_SCHEMA.COLUMNS` for your tracked schemas, compares each column's data type, precision, and nullability to the previous snapshot, and flags any column whose type changed (for example `NUMBER(10,2)` becoming `VARCHAR`, or a `NOT NULL` column going nullable). Each drift becomes a Slack alert and a Linear ticket pre-filled with the table, column, old shape, and new shape.
When to use it
Run this when downstream dashboards or pipelines silently break because an upstream column quietly changed type during a model rebuild or a migration. It catches the change at the warehouse before a report renders garbage.
How it works
- 1A nightly schedule fires the run.
- 2Query `INFORMATION_SCHEMA.COLUMNS` in Snowflake for the tracked schemas and capture each column's type signature.
- 3Diff the current signatures against the stored snapshot to isolate columns whose type, scale, or nullability changed.
- 4If no drift is found, store the new snapshot and stop.
- 5Post a Slack alert listing each drifted column with its before and after shape.
- 6Open a Linear issue per drift with reproduction details, then persist the new snapshot as the baseline.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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
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…
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.
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.