DATA OPS
Daily BigQuery-to-Salesforce field freshness audit
Compares key account fields in Salesforce against the source-of-truth values in BigQuery every morning.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule before business hours
- ActionQuery source-of-truth values from BigQueryBigQuery
- ActionFetch synced field values from SalesforceSalesforce
- LogicJoin on account ID and compute field deltas and sync age
- LogicFilter to records past the freshness SLA or value mismatch
- OutputPost grouped stale-account digest to SlackSlack
What it does
Reverse-ETL pipelines push warehouse data into Salesforce, but syncs silently skip rows, lag overnight loads, or drop fields when a mapping breaks. This workflow runs a scheduled reconciliation: it pulls the canonical values from BigQuery and the synced values from Salesforce, joins them on account ID, and flags every field that disagrees or is older than your freshness SLA. The result is a single Slack digest naming the drifted accounts and the exact field deltas.
When to use it
Run it when you depend on synced CRM fields (MRR, health score, plan tier) for routing or alerts and need daily confidence that what reps see matches the warehouse. Best for teams who tolerate eventual consistency but must catch sustained drift.
How it works
- 1A daily schedule fires before the sales team logs on.
- 2Query BigQuery for the current source-of-truth field values per account.
- 3Pull the matching synced fields from Salesforce.
- 4Join on account ID and compute per-field deltas and sync age.
- 5Filter to records exceeding the freshness threshold or showing a value mismatch.
- 6Post a grouped Slack digest listing each stale account and its drifted fields.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 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.