DATA OPS
Reverse-ETL Salesforce Drift Auto-Repair with Review Gate
Detects Salesforce account fields that have drifted from their Snowflake source of truth and auto-corrects low-risk fields while routing high-risk field changes to Slack…
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule starts the drift sweep
- ActionRead source-of-truth account attributes from SnowflakeSnowflake
- ActionRead current account field values from SalesforceSalesforce
- LogicDiff fields and classify drift as low or high risk
- ActionAuto-write low-risk corrections back to SalesforceSalesforce
- OutputRoute high-risk changes to Slack for approvalSlack
What it does
This is a detect-and-fix loop for Salesforce. It compares warehouse-derived account fields in Snowflake against the live Salesforce values, then splits the drift by risk. Low-risk cosmetic fields (region, segment label, last-computed-score) are written back to Salesforce automatically. High-risk fields that affect routing or revenue recognition (account tier, owner, contract value) are held and posted to Slack with an approve action, so a human confirms before the CRM is overwritten.
When to use it
Use it when you want drift fixed fast but cannot let an automated job blindly overwrite fields that change deal ownership or forecasting. Run hourly or on demand.
How it works
- 1A schedule starts the drift sweep.
- 2Snowflake returns source-of-truth account attributes.
- 3Salesforce returns current account field values.
- 4A logic step diffs fields and classifies each mismatch as low or high risk.
- 5An action writes the low-risk corrections back to Salesforce immediately.
- 6High-risk changes are posted to Slack with an approval prompt for a human to confirm before any write.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect SalesforceAccounts, opportunities, cases.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.