DATA OPS
Weekly PII drift governance digest to Notion register
Compiles the week's column-classification changes across BigQuery into a written summary and updates a Notion data-governance register so stewards have a single living record…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule triggers the digest
- ActionQuery past-week classification changes from BigQueryBigQuery
- ActionDraft structured governance digest with an LLMOpenAI
- LogicSkip the run if no changes occurred
- ActionUpsert digest into the Notion governance registerNotion
- OutputPost register link to Slack governance channelSlack
What it does
This workflow produces the weekly paper trail governance teams need. It gathers every classification change recorded over the past week, has an LLM write a concise human-readable digest grouping new PII, downgraded columns, and still-open masking candidates, then updates a Notion data-governance register so the register always reflects current reality.
When to use it
Use it when you already detect drift daily but need a periodic, auditable rollup that non-engineers can read and that satisfies governance reviewers asking what changed this week and why.
How it works
- 1A weekly schedule triggers the digest.
- 2The workflow queries BigQuery for all classification-change records logged in the past seven days.
- 3An OpenAI call drafts a structured digest: new PII columns, resolved items, and outstanding masking candidates with rationale.
- 4A logic step skips the run cleanly if there were no changes, avoiding empty noise.
- 5The workflow upserts the digest and per-column entries into the Notion governance register.
- 6It posts a short link to the updated register in the Slack governance channel.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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
Snowflake column type-drift sentinel with Linear fix ticket
Snapshots the data types of every column in your tracked Snowflake schemas on a schedule, diffs against the last snapshot.
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 dropped/renamed column sentinel with PagerDuty incident
Detects when a column is dropped or renamed in your governed BigQuery datasets and, because that breaks downstream queries hard, pages the on-call via PagerDuty and posts…
PR-time Snowflake schema contract check on dbt model changes
When a pull request changes a dbt model, it compares the model's declared output columns against the live Snowflake table it will replace and blocks the merge with a GitHub check…
Agent-triaged warehouse drift with impact analysis and runbook update
On a webhook from your warehouse audit log, an agent investigates the changed column, traces which downstream models and dashboards depend on it.
Cross-warehouse replication schema mismatch reconciler
Compares the column shape of mirrored tables between BigQuery and Snowflake and, when a replicated table has drifted out of sync between the two, opens an Asana task for the data…
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.