DATA OPS
Daily freshness watchdog for Snowflake to Salesforce audience syncs
Each morning, checks the max updated-at timestamp in the Snowflake source model against the last synced timestamp in Salesforce and pages on-call if the audience is stale.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionRead max updated-at timestamp from Snowflake modelSnowflake
- ActionRead latest sync timestamp from Salesforce objectSalesforce
- LogicCompute freshness lag vs SLA window
- OutputPage on-call via PagerDuty if audience is stalePagerDuty
What it does
Guards against a frozen reverse-ETL pipeline. It reads the freshest record timestamp in your Snowflake audience model and the most recent sync timestamp on Salesforce records, then measures how far behind the destination has fallen. If the lag breaches your SLA, it escalates.
When to use it
Use it when sales or RevOps acts on data that must be current, like account health scores or intent signals. Reverse-ETL jobs can succeed at zero rows or quietly stop scheduling, leaving Salesforce showing yesterday's truth while everyone assumes it is live. This watchdog turns that invisible staleness into a paged incident.
How it works
- 1A daily schedule fires before the sales team starts its day.
- 2Query Snowflake for the maximum updated-at timestamp across the audience model.
- 3Query Salesforce for the latest sync timestamp on records in the target object.
- 4A logic step computes the freshness lag in hours and tests it against the SLA window.
- 5If fresh, the run ends quietly; if stale, open a PagerDuty incident with the lag, both timestamps, and the model name so on-call can act immediately.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect SalesforceAccounts, opportunities, cases.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.