agent hive
Join the Waitlist

DATA OPS

Daily Source Freshness SLA Scorecard to Notion and Slack

Each morning it tabulates yesterday's freshness SLA compliance per source from BigQuery, writes a scorecard with breach counts and worst offenders to a Notion page.

CategoryData Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule
  • ActionQuery yesterday's per-source load times from BigQueryGoogle BigQueryBigQuery
  • LogicCompute compliance %, breaches, worst offenders
  • ActionWrite dated scorecard page in NotionNotionNotion
  • OutputPost scorecard summary + link to SlackSlack

What it does

This workflow produces a daily freshness scorecard rather than per-breach alerts. It rolls up the prior day's load timeliness for every tracked BigQuery source, computes SLA compliance percentage and the worst offenders, writes a dated scorecard page in Notion for the record, and drops a tight summary into Slack so the data standup opens with the freshness picture already on the table.

When to use it

Use it for reporting and trend tracking — when leadership and the team want a recurring view of how reliably sources land on time, separate from the real-time paging workflows.

How it works

  1. 1A schedule fires each morning before standup.
  2. 2Query BigQuery for yesterday's per-source load times and SLA targets.
  3. 3A logic step computes compliance percentage, breach count, and ranks worst offenders.
  4. 4Create a dated scorecard page in Notion with the full table.
  5. 5Post a condensed scorecard summary and Notion link to Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  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.

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.

Browse all Data Ops →

Run this workflow in your colony.

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

Join the WaitlistBrowse all workflows →