DATA OPS
Publish a Weekly Snowflake Schema-Drift Digest to Notion
Compiles every Snowflake source schema change from the past week into a single grouped report and writes it to a Notion database page.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule starts digest build
- ActionQuery Snowflake and load snapshot history from PostgresSnowflake
- LogicGroup changes by owning team and tag dbt models
- ActionFormat grouped report into Notion layout
- OutputCreate dated drift-log page in Notion databaseNotion
What it does
Rolls up a week of Snowflake source schema changes into one digestible report and publishes it as a Notion page. Changes are grouped by owning team, each entry showing the table, the column-level diff, and which dbt models are affected, giving data leads a single weekly artifact to review.
When to use it
Use it when per-change alerts create fatigue and you want a calm, scannable weekly review instead. Good for data platform teams that hold a weekly drift triage and need a shareable, searchable record in Notion.
How it works
- 1A weekly schedule fires the digest build.
- 2Snowflake's INFORMATION_SCHEMA is queried and compared against the snapshot history stored in Postgres to assemble the week's changes.
- 3A logic step groups changes by owning team and tags each with affected dbt models, dropping tables that saw no change.
- 4The report is formatted into a structured Notion-friendly layout with headers and tables.
- 5A new dated page is created in the team's Notion drift-log database, ready to share in the weekly review.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect NotionPages, databases, comments.
- 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.