DATA OPS
Weekly Warehouse Schema-Drift Digest to Confluence and Teams
Aggregates all Snowflake schema changes accumulated over the past week, has an agent group and summarize them by domain into a readable changelog.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule kicks off digest
- ActionQuery last 7 days of drift log from PostgresPostgres
- ActionAgent groups changes by domain and narrates changelog
- ActionPublish dated changelog to ConfluenceConfluence
- OutputPost highlights and link to Microsoft TeamsMicrosoft Teams
What it does
It produces a human-readable weekly record of how the warehouse changed. Rather than alerting per change, it collects every schema delta logged over the past seven days, then an agent groups the raw column diffs by data domain, writes a plain-English summary of what changed and why it likely matters, and publishes a dated changelog page. The team gets a digest link instead of a week of scattered notifications.
When to use it
Use it as the calm companion to real-time alerting: stakeholders and analysts who don't need pages still want a periodic, narrated view of warehouse evolution for audits and onboarding. Ideal when leadership asks "what changed in the data this sprint?" and you want a standing answer.
How it works
- 1A weekly schedule kicks off the digest.
- 2Query the stored drift log in Postgres for the last seven days of changes.
- 3The agent groups changes by domain and writes a narrated changelog.
- 4Publish the changelog as a dated Confluence page.
- 5Post the top highlights and the page link to Microsoft Teams.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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.