DATA OPS
Reverse-ETL CRM Field Drift Watcher (Snowflake to HubSpot)
Compares warehouse-of-truth field values in Snowflake against the same fields synced into HubSpot and flags contacts whose CRM values have drifted stale.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires the drift audit
- ActionQuery source-of-truth attributes from SnowflakeSnowflake
- ActionBatch-read matching contact properties from HubSpotHubSpot
- LogicDiff each field and keep only stale CRM rows
- LogicStop if no drift detected
- OutputPost drifted contacts and exact mismatches to SlackSlack
What it does
This workflow audits the reverse-ETL pipeline that pushes computed customer attributes from Snowflake into HubSpot. On a schedule it pulls the authoritative values from your warehouse, fetches the corresponding HubSpot contact properties, and diffs them field by field. Any contact whose CRM value no longer matches the warehouse (lifecycle stage, MRR tier, health score, last-active date) is reported as drift so RevOps knows the sync silently fell behind.
When to use it
Run it when your sales and CS teams rely on warehouse-derived fields in HubSpot and a broken or lagging reverse-ETL job would route leads wrong, misfire workflows, or show reps stale numbers. Daily or hourly is typical.
How it works
- 1A schedule kicks off the run each morning.
- 2Snowflake query returns the current source-of-truth attributes per contact email.
- 3HubSpot batch read fetches the matching contact properties.
- 4A logic step diffs each field and keeps only rows where values disagree beyond tolerance.
- 5If any drift exists, a formatted Slack message lists the affected contacts, the field, the stale CRM value, and the correct warehouse value for RevOps to act on.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect HubSpotCRM, deals, marketing, support.
- 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.