DATA OPS
On-Demand Drift Investigation and Remediation Plan
Chat-triggered agent that, given a table name, fetches both schemas, explains in plain language exactly how BigQuery and Snowflake diverged, assesses downstream impact.
How it runs
The automated pipeline, trigger to output.
- TriggerChat: investigate this table
- ActionRead BigQuery schemaBigQuery
- ActionRead Snowflake schemaSnowflake
- LogicReason over diff, impact, and fix orderOpenAI
- OutputReply with explanation and proposed DDL
What it does
This is an agent you talk to. Ask it about a table and it pulls the live BigQuery and Snowflake schemas, narrates precisely how they differ, reasons about which downstream models or reports the drift would affect, and proposes a concrete reconciliation plan including the DDL it would run. It produces understanding and a plan, not a silent automated change.
When to use it
Use it during an active investigation when a dashboard looks wrong or a dbt run failed and you suspect schema drift. It is the interactive counterpart to the scheduled detectors: ask, get an explanation, and get a vetted plan you can hand off.
How it works
- 1A chat message names the table to investigate.
- 2The agent reads the BigQuery schema for that table.
- 3The agent reads the Snowflake schema for the same table.
- 4It reasons over the diff, impact, and a safe remediation order.
- 5It replies in chat with a plain-language explanation plus the proposed reconciliation DDL.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect OpenAIModels, embeddings, files.
- 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
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 orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
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.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
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.
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…
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.