DATA OPS
Warehouse Table Freshness Sentinel
Checks the max-loaded timestamp of critical Snowflake tables against each table's SLA on a schedule, and pages the data owner in Slack when a table goes stale.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 15 minutes
- ActionLoad freshness registry from PostgresPostgres
- ActionQuery MAX(loaded_at) per table in SnowflakeSnowflake
- LogicKeep only tables past their SLA
- OutputPage owners in Slack with lag vs SLASlack
What it does
Runs a scheduled freshness sweep across a registry of business-critical Snowflake tables. For each table it reads the newest load timestamp, compares the gap to the table's declared SLA (e.g. orders must update hourly, dim_customer daily), and raises an alert only for tables that have actually breached. Fresh tables pass silently so the channel stays quiet until something is wrong.
When to use it
When downstream dashboards or reverse-ETL jobs silently serve stale numbers because an upstream load failed and nobody noticed for hours. Use it to put an explicit freshness SLA on the tables your business depends on.
How it works
- 1A schedule fires every 15 minutes.
- 2The flow reads the freshness registry (table name, SLA minutes, owner handle) from a Postgres config table.
- 3For each table it queries Snowflake for MAX(loaded_at) and computes minutes-since-load.
- 4A logic step keeps only tables whose lag exceeds their SLA.
- 5Breached tables are grouped by owner and posted to Slack, tagging each owner with the table, current lag, and SLA.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.