DATA OPS
Cross-warehouse parity check with PagerDuty escalation
Compares the schema of mirrored tables between Snowflake and BigQuery on a schedule and pages on-call via PagerDuty when the two warehouses fall out of sync.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled parity check starts
- ActionRead mirrored table schemas from SnowflakeSnowflake
- ActionRead same tables from BigQueryBigQuery
- LogicNormalize types; detect divergence
- OutputTrigger PagerDuty incident on mismatchPagerDuty
What it does
Many teams replicate the same tables into two warehouses for different consumers. This workflow checks that the mirrored tables stay structurally identical. On each run it reads the schema of each table from both Snowflake and BigQuery, normalizes type names across the two dialects, and detects any column that exists in one but not the other or whose type diverges. A real divergence pages on-call so the replication gap is fixed before reports disagree.
When to use it
Use it when you maintain a Snowflake-to-BigQuery (or reverse) mirror and a schema mismatch would cause two dashboards to report different numbers. It is for high-stakes parity where divergence is an incident, not a ticket.
How it works
- 1A scheduled trigger starts the parity check.
- 2It reads schemas for each mirrored table from Snowflake.
- 3It reads the same tables' schemas from BigQuery.
- 4A logic step normalizes type names and detects column or type divergence.
- 5If the warehouses disagree, it triggers a PagerDuty incident with the divergent fields.
- 6Matching runs end silently with no page.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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
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.
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 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 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…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Raw Sensor Telemetry Archive to BigQuery
Captures every incoming building sensor reading via webhook, normalizes the payload into a consistent schema.
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.