DATA OPS
Cross-warehouse replication parity check (Snowflake vs BigQuery)
Compares the schema of mirrored tables between Snowflake and BigQuery and pages on-call via PagerDuty when the two warehouses drift out of sync.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled parity check fires
- ActionFetch Snowflake mirrored-table schemaSnowflake
- ActionFetch BigQuery mirrored-table schemaBigQuery
- LogicCompare and flag divergence between warehouses
- ActionOpen PagerDuty incident on divergencePagerDuty
- OutputPost mismatch summary to SlackSlack
What it does
For organizations that replicate the same tables into two warehouses, this confirms the column sets and types stay identical across Snowflake and BigQuery. When replication lags or a one-sided migration lands, the schemas diverge silently — this catches the divergence and treats it as an incident.
When to use it
Use it when you maintain a dual-warehouse setup (e.g. Snowflake for finance, BigQuery for product analytics) fed from the same source, and a schema mismatch between them would corrupt joins or reconciliation reports.
How it works
- 1A scheduled trigger fires every few hours.
- 2Pull the column inventory for the mirrored table list from Snowflake.
- 3Pull the same inventory from BigQuery.
- 4Compare the two side by side, flagging columns present in one but not the other and any type mismatches.
- 5If divergence exists, branch to escalation.
- 6Trigger a PagerDuty incident with the per-table mismatch detail and post the same summary to the data team's Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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
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.