DATA OPS
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…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily reconciliation schedule fires
- ActionRead mapped table columns from BigQueryBigQuery
- ActionRead matching table columns from SnowflakeSnowflake
- LogicNormalize dialects and diff each mirrored pair
- OutputOpen Asana task per divergent tableAsana
What it does
When the same logical table is replicated across two warehouses, the copies can silently diverge after one side gets a migration the other didn't. This workflow reads the column definitions of each mirrored pair in BigQuery and Snowflake, normalizes the type names across the two dialects, and reports tables where the shapes no longer match. Each divergence becomes an Asana task assigned to the replication owner.
When to use it
Use it when you run a dual-warehouse setup (for example BigQuery for analytics, Snowflake for the product) and need the mirrors kept structurally identical so cross-warehouse joins and failover stay trustworthy.
How it works
- 1A daily schedule starts the reconciliation.
- 2Read column definitions for the mapped tables from BigQuery.
- 3Read the matching tables' column definitions from Snowflake.
- 4Normalize dialect type names and diff each pair to find missing, extra, or retyped columns.
- 5If every pair matches, finish with no action.
- 6Create an Asana task per divergent table listing the field-level mismatches.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect AsanaTasks, projects, milestones — everywhere.
- 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
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.
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.