DATA OPS
Weekly Postgres source-schema drift digest to Notion
Tracks the schema of your operational Postgres source tables and, once a week, publishes a Notion page summarizing every additive and breaking change since the last digest.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly digest schedule fires
- ActionRead source-table schemas from PostgresPostgres
- LogicDiff vs baseline; group and label changes
- OutputPublish dated changelog page in NotionNotion
- ActionStore new weekly baselinePostgres
What it does
This workflow maintains a weekly changelog of how your operational Postgres database has evolved. It snapshots source-table schemas, accumulates the changes detected across the week, and on a weekly cadence writes them into a Notion page grouped by table — separating safe additive changes from breaking ones. Instead of pinging people mid-week for non-urgent shifts, it batches everything into one reviewable digest.
When to use it
Use it when application engineers ship schema changes to the source database faster than the analytics team can keep up, and you want a calm weekly review rather than real-time alerts. It pairs well with a standing weekly data-sync meeting.
How it works
- 1A weekly schedule triggers the digest.
- 2It reads current source-table schemas from Postgres `information_schema`.
- 3It loads the prior week's baseline and computes the full set of changes.
- 4A logic step groups changes per table and labels additive vs breaking.
- 5It publishes or appends a dated changelog page in Notion.
- 6It stores the new baseline for next week's comparison.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect NotionPages, databases, comments.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.