DATA OPS
Post-sync verification webhook with auto-rollback flag
Triggered by the reverse-ETL platform's sync-complete webhook, immediately re-reads the just-pushed records from Salesforce and compares them to BigQuery.
How it runs
The automated pipeline, trigger to output.
- TriggerSync-complete webhook from reverse-ETL platformHTTP webhook
- ActionRead records the batch updated from SalesforceSalesforce
- ActionRead matching source rows from BigQueryBigQuery
- LogicCompare field-by-field and compute mismatch rate
- LogicBranch when mismatch rate exceeds threshold
- OutputPost Slack alert to hold downstream automationSlack
What it does
Instead of waiting for a scheduled audit, this workflow verifies a sync the moment it finishes. The reverse-ETL platform fires a webhook on sync completion; the flow re-reads the records that batch claimed to update from Salesforce, compares them field-by-field against the BigQuery source rows from the same load, and computes a mismatch rate. If too many records failed to land correctly, it marks the batch as suspect and posts a Slack alert telling the team to pause any downstream automation (lead routing, billing triggers) that consumes those fields until the sync is re-run.
When to use it
Use it when downstream systems act on synced fields within minutes and a bad batch is expensive. It catches partial-failure syncs that report success but only wrote half the rows.
How it works
- 1The reverse-ETL platform's sync-complete webhook triggers the flow with the batch ID.
- 2Read the records the batch updated from Salesforce.
- 3Read the matching source rows from BigQuery for that load.
- 4Compare field-by-field and compute the mismatch rate.
- 5Branch when the mismatch rate exceeds the configured threshold.
- 6Post a Slack alert flagging the batch and advising a downstream hold.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SalesforceAccounts, opportunities, cases.
- 3Connect BigQueryDatasets, queries, schemas.
- 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.