DATA OPS
Reverse-ETL Post-Sync Validator: Row-Count and Recency Check on Webhook
Fires when your reverse-ETL tool reports a sync finished, then validates that warehouse and destination row counts match and the data is recent — alerting Slack on any mismatch.
How it runs
The automated pipeline, trigger to output.
- TriggerReverse-ETL sync-complete webhook receivedHTTP webhook
- ActionRead expected row count + recency from BigQueryBigQuery
- ActionRead actual landed row count from Airtable destinationAirtable
- LogicCompare source vs. destination counts and recency
- OutputPost drift/staleness mismatch alert to SlackSlack
What it does
This workflow runs immediately after a reverse-ETL job claims success, via a completion webhook. It cross-checks the source warehouse rows against what actually landed downstream and verifies the synced rows are recent, catching the case where a job reports success but quietly dropped or skipped records.
When to use it
Use it when a green sync status isn't enough trust — you want proof the destination matches the warehouse after every run, not on a schedule. Ideal for high-stakes syncs into operational tools your team acts on directly.
How it works
- 1An incoming webhook from your reverse-ETL tool fires when a sync completes, carrying the model name and run ID.
- 2A BigQuery query reads the expected row count and latest timestamp for that model.
- 3An Airtable read pulls the actual landed row count for the synced destination.
- 4A logic step compares expected vs. actual counts and checks recency tolerance.
- 5If counts match and data is fresh, the run ends.
- 6On any drift or staleness, a Slack alert reports the run ID, the gap, and the source-vs-destination numbers.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect AirtableBases, tables, views, automations.
- 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.