DATA OPS
Nightly Snowflake table freshness check with Slack digest
Every night after your ELT loads finish, this checks the max load timestamp on a set of Snowflake tables against each table's expected SLA and posts a single pass/fail digest…
How it runs
The automated pipeline, trigger to output.
- TriggerNightly cron after load window
- ActionQuery MAX(loaded_at) per Snowflake tableSnowflake
- LogicCompute lag and flag SLA breaches
- ActionFormat pass/fail freshness digest
- OutputPost digest to Slack channelSlack
What it does
Runs a freshness audit across a list of critical Snowflake tables. For each table it reads the most recent `_loaded_at` (or equivalent watermark column) and compares the lag against that table's allowed staleness window. It then rolls every result into one Slack message: green tables, stale tables, and exactly how far behind each stale table is.
When to use it
Use it when your ELT writes to Snowflake overnight and downstream dashboards or models depend on those tables being current by morning. It replaces the manual "is the data loaded yet?" check the on-call analyst does over coffee.
How it works
- 1A nightly cron fires after your scheduled load window closes.
- 2A Snowflake query pulls `MAX(loaded_at)` per table from an information/metadata view.
- 3A logic step computes lag per table and flags any that exceed their SLA.
- 4The results are formatted into a single digest with a clear PASS/FAIL header.
- 5The digest is posted to a Slack channel, tagging the data on-call only when something is stale.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
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 orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
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.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
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.
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…
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.