DATA OPS
Reverse-ETL Freshness Guard: BigQuery to Salesforce Lag Alert
Checks how long ago each BigQuery-to-Salesforce sync table was last refreshed and alerts Slack the moment any sync exceeds its allowed staleness window.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 30 minutes (schedule)
- ActionQuery BigQuery for each model's MAX(updated_at)BigQuery
- LogicCompute lag per model; flag those over threshold
- ActionConfirm Salesforce destination row count not frozenSalesforce
- OutputPost stale-sync alert to Slack data-ops channelSlack
What it does
This workflow watches your reverse-ETL pipeline that pushes warehouse models into Salesforce. On a schedule it reads the last-updated timestamp for each synced model in BigQuery, compares it against a per-model freshness budget, and raises a Slack alert listing exactly which syncs have gone stale and by how long.
When to use it
Use it when Salesforce records (accounts, lead scores, usage rollups) are powered by warehouse models and your revenue team relies on them being current. It catches a silent sync pause before reps act on day-old numbers.
How it works
- 1A schedule fires every 30 minutes.
- 2A BigQuery query returns each sync model's name and its MAX updated_at timestamp.
- 3A logic step computes lag per model and flags any whose lag exceeds its configured threshold.
- 4If nothing is stale, the run ends quietly.
- 5For stale models, a Salesforce read confirms the destination row count hasn't frozen, ruling out false alarms.
- 6A Slack message posts the stale table list with lag durations and last-sync times to the data-ops channel.
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.