DATA OPS
On-Demand Freshness Check from SLA Definitions in Notion
Triggered by a webhook, reads the table-to-SLA registry maintained in Notion, checks each table's current freshness in Snowflake.
How it runs
The automated pipeline, trigger to output.
- TriggerIncoming webhook requestHTTP webhook
- ActionRead SLA registry from NotionNotion
- ActionMeasure freshness in SnowflakeSnowflake
- LogicCompute pass/fail per table
- ActionOpen PagerDuty incidents for breachesPagerDuty
- OutputReturn pass/fail report to callerHTTP webhook
What it does
This turns your Notion SLA registry into a runnable check. A webhook call kicks off an evaluation that loads every table's owner and expected freshness window from a Notion database, measures actual freshness in Snowflake, and returns a structured pass/fail result. Any breach also opens a PagerDuty incident so nothing relies on a human reading the report.
When to use it
Use it when teams declare their freshness SLAs in Notion and you want a single source of truth that is both human-editable and machine-enforceable. Great for ad-hoc "is everything fresh right now?" checks before a board demo or release.
How it works
- 1An incoming HTTP webhook starts the run.
- 2It reads the SLA registry rows (table, owner, max staleness) from the Notion database.
- 3It queries Snowflake for each table's actual last-load timestamp.
- 4A logic step computes pass/fail per table against its registry SLA.
- 5For each failure it opens a PagerDuty incident routed to the listed owner.
- 6It returns the full pass/fail report to the webhook caller.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect NotionPages, databases, comments.
- 3Connect SnowflakeWarehouses, queries, shares.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.