DATA OPS

Weekly Contract Drift Digest

Each week, aggregates all schema changes observed across the warehouse, writes a human-readable changelog to a Notion page, and posts a summary digest to Slack for the data team.

CategoryData Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule triggers the digest
  • ActionRead accumulated schema observations from BigQueryGoogle BigQueryBigQuery
  • LogicGroup and classify changes per table
  • ActionAppend changelog entry to Notion governance pageNotionNotion
  • OutputPost summary digest to SlackSlack

What it does

Rather than alerting on every individual change, this workflow batches a week of schema observations into one digest. It groups changes by table, separates additive evolution from breaking changes, appends the full changelog to a versioned Notion page, and drops a short summary in Slack so the team starts the week knowing what moved.

When to use it

Use it for governance and visibility rather than incident response. It gives data stewards a reliable weekly record of how table contracts are evolving, and a searchable history in Notion for audits and onboarding.

How it works

  1. 1A weekly schedule triggers the digest.
  2. 2Read the week's accumulated schema observations from BigQuery audit metadata.
  3. 3Group and classify changes per table into additive vs breaking.
  4. 4Append a formatted changelog entry to the Notion governance page.
  5. 5Post a concise summary with counts and links 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.

Run this workflow in your colony.

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