DATA OPS
Cross-Warehouse Reconciliation Check
Reconciles a shared metric (like daily revenue) between BigQuery and Snowflake each morning and opens a GitHub issue plus a Slack alert when the two warehouses disagree beyond…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily after both loads finish
- ActionCompute canonical metric in BigQueryBigQuery
- ActionCompute same metric in SnowflakeSnowflake
- LogicCompare against tolerance
- ActionOpen GitHub issue on mismatchGitHub
- OutputPost Slack alert linking the issueSlack
What it does
Guards against the two systems of record drifting apart. Each morning it computes the same agreed metric in both BigQuery and Snowflake for the prior day, compares the two values, and if they differ by more than a small tolerance it raises both a tracked GitHub issue and a Slack alert so the discrepancy is investigated before either number is reported externally.
When to use it
When two warehouses (or a warehouse and a finance mart) are supposed to agree on a headline metric but periodically diverge due to late-arriving data, timezone handling, or differing dedup logic. Use it to catch the mismatch internally instead of in a board deck.
How it works
- 1A daily schedule fires after both warehouses finish their morning loads.
- 2The flow runs the canonical metric query against BigQuery for the prior day.
- 3It runs the equivalent query against Snowflake for the same day.
- 4A logic step computes the absolute and percent difference and checks it against tolerance.
- 5On a breach it opens a GitHub issue with both values and the query definitions, then posts a Slack alert linking the issue.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.