DATA OPS
Schema-Drift Triage Agent that Maps Impact and Files a Linear Issue
When BigQuery schema drift is detected, an agent traces which downstream models, dashboards, and pipelines depend on the changed column, writes a plain-English impact assessment.
How it runs
The automated pipeline, trigger to output.
- TriggerDrift-detected webhook receivedHTTP webhook
- ActionTrace dependent models and jobs via BigQuery lineageBigQuery
- LogicAgent assesses blast radius and assigns severity
- ActionPost impact summary to SlackSlack
- OutputOpen prioritized Linear issue for the ownerLinear
What it does
This goes beyond detection to triage. Once drift is found on a watched BigQuery table, an agent walks the dependency lineage to determine what actually breaks — which transformed models reference the column, which dashboards surface it, which jobs will fail. It drafts a human-readable impact summary, picks a severity, and files a Linear issue assigned to the owning team with the diff and a suggested fix.
When to use it
Use it when raw drift alerts create more triage work than they save. The agent does the reasoning a data engineer would otherwise do by hand: scoping blast radius and routing the ticket to whoever owns the affected assets.
How it works
- 1A schema-drift webhook from the detector fires with the changed table and column.
- 2The agent queries BigQuery lineage and metadata to find dependent models, views, and jobs.
- 3The agent reasons over the blast radius and writes an impact assessment with a severity.
- 4It posts the summary to Slack for visibility.
- 5It opens a Linear issue with the diff, impact, owner, and suggested remediation.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.