DATA OPS

dbt Daily Freshness and Volume Scorecard to Notion

Each morning rolls up the prior day's source-freshness and row-volume health across all tracked Snowflake tables into a single trend scorecard published to Notion.

CategoryData Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSchedule each morning
  • ActionPull freshness and volume metrics from SnowflakeSnowflakeSnowflake
  • LogicClassify tables healthy/degraded/breached
  • ActionPublish dated scorecard to NotionNotionNotion
  • OutputPost headline digest to SlackSlack

What it does

Instead of one alert per breach, this workflow produces the daily picture: it aggregates yesterday's freshness lag and row-volume deviation for every tracked table, scores each as healthy, degraded, or breached, and writes a dated scorecard page to Notion. A short Slack digest summarizes the counts and links the full page.

When to use it

Use it when leadership and stakeholders want trend and accountability, not pager noise — a standing artifact that shows whether warehouse health is improving or sliding week over week. Pairs well with the per-breach sentinels that handle the urgent cases.

How it works

  1. 1A schedule fires each morning after overnight loads settle.
  2. 2Snowflake returns per-table freshness lag and yesterday-vs-baseline volume.
  3. 3A logic step classifies each table as healthy, degraded, or breached.
  4. 4The flow assembles a ranked scorecard with day-over-day deltas.
  5. 5A dated page is published to Notion under the data-health database.
  6. 6A Slack digest posts the headline counts and a link to the page.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.