DATA OPS
Reverse-ETL Sync Freshness SLA Monitor
Watches the last successful sync timestamp recorded in Snowflake for each reverse-ETL destination and pages on-call via PagerDuty when any sync exceeds its freshness SLA.
How it runs
The automated pipeline, trigger to output.
- Trigger15-minute schedule runs the freshness check
- ActionRead last-success timestamps and SLAs from SnowflakeSnowflake
- LogicCompute staleness and select SLA breaches
- ActionOpen a PagerDuty incident per breached destinationPagerDuty
- OutputMirror the alert to the data-ops Slack channelSlack
What it does
Instead of comparing values, this workflow watches the heartbeat of the reverse-ETL pipeline itself. It reads the sync metadata table in Snowflake that records when each downstream destination (HubSpot, Salesforce, ad platforms) was last loaded successfully, then checks each destination's age against its configured freshness SLA. A sync that has gone quiet past its threshold triggers a PagerDuty incident so the pipeline is fixed before sales sees stale fields.
When to use it
Use it when silent sync failures are your real risk: the job stops running, no rows error, and CRM data quietly ages. Best for teams with named freshness SLAs per destination.
How it works
- 1A schedule runs the freshness check every 15 minutes.
- 2Snowflake query returns the last-success timestamp and configured SLA for each destination.
- 3A logic step computes staleness age and selects destinations past their SLA.
- 4If any breach exists, a PagerDuty incident is opened with the destination, age, and SLA.
- 5A Slack note mirrors the alert to the data-ops channel for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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.