DATA OPS
Daily BigQuery freshness SLA scorecard to Notion
Each morning it computes per-table on-time percentage and worst lateness over the trailing window from the breach ledger, writes a ranked SLA scorecard page in Notion.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily after ingestion window closes
- ActionQuery trailing-7-day breach ledger historyPostgres
- LogicCompute on-time %, worst lateness, and trend; rank
- ActionUpsert dated SLA scorecard pageNotion
- OutputLink scorecard and flag below-target tables in SlackSlack
What it does
It turns raw breach history into a readable daily scorecard. For every tracked table it calculates the trailing-7-day on-time landing rate, average and worst minutes-late, and a trend arrow, then publishes a ranked page in Notion. Tables dipping below their SLA target get flagged so data leads can prioritize ingestion fixes.
When to use it
Use it when leadership wants a recurring, glanceable view of pipeline reliability rather than ad-hoc incident noise. Good for weekly data-platform reviews and proving SLA compliance.
How it works
- 1A schedule fires once each morning after the ingestion window closes.
- 2A Postgres action queries the breach ledger for the trailing-7-day landing and lateness history.
- 3A logic step computes per-table on-time percentage, worst lateness, and trend, then ranks worst-first.
- 4A Notion action upserts the dated scorecard page with the ranked table.
- 5A Slack message links the new scorecard and calls out any table that fell below target.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect NotionPages, databases, comments.
- 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.