DATA OPS
Drift impact analyst with downstream lineage
When a Snowflake column drifts, an agent traces which downstream models, dashboards, and dbt nodes depend on it.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled drift scan fires
- ActionDetect changed columns in SnowflakeSnowflake
- ActionRead dbt manifest and lineage from GitHubGitHub
- LogicAgent traces and ranks downstream impact
- OutputPublish impact brief to NotionNotion
- OutputLink the brief in SlackSlack
What it does
Goes beyond detecting drift to explaining its blast radius. When a watched Snowflake column changes, an agent reads your lineage metadata and dbt manifest to figure out every downstream consumer, reasons about which ones will actually break, and writes a prioritized impact brief in Notion that a non-engineer can act on.
When to use it
You get drift alerts but spend hours each time tracing what they affect. You want the triage done for you — a ranked list of at-risk models and dashboards with a recommended fix order — handed to you as a readable doc.
How it works
- 1A scheduled trigger runs the drift scan.
- 2Query Snowflake metadata to detect changed columns since the last run.
- 3The agent reads the dbt manifest and lineage from GitHub to map downstream dependents of each changed column.
- 4It reasons over the graph to rank consumers by breakage likelihood and business impact.
- 5It drafts a structured impact brief — what changed, what breaks, suggested fix order.
- 6Publish the brief as a new Notion page and link it in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.