CHATBOTS

Nightly Schema-Drift Digest for the Dictionary

Each night compares the live Snowflake schema to the documented data dictionary in Coda and posts a Slack digest of new, dropped, renamed, or undocumented columns…

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule
  • ActionSnapshot live schema from SnowflakeSnowflakeSnowflake
  • ActionRead documented columns from CodaCodaCoda
  • LogicDiff and categorize drift (new/dropped/changed)
  • ActionWrite documentation gaps to Coda tableCodaCoda
  • OutputPost drift digest to SlackSlack

What it does

Keeps the data dictionary honest. Every night it diffs the warehouse's real columns against what the dictionary documents and surfaces exactly what changed, so undocumented or stale entries never pile up unnoticed.

When to use it

When schemas evolve faster than docs and analysts lose trust in the dictionary. Use it to assign documentation debt the morning after any schema change lands.

How it works

  1. 1A scheduled trigger runs on a nightly cron.
  2. 2The flow snapshots the current table and column inventory from Snowflake INFORMATION_SCHEMA.
  3. 3It reads the documented columns from the Coda data dictionary.
  4. 4A diff step categorizes changes: new columns missing docs, columns dropped from the warehouse but still documented, and type changes.
  5. 5If nothing changed, it exits quietly; otherwise it writes the gaps back into a Coda "needs documentation" table.
  6. 6It posts a Slack digest summarizing the drift with owners tagged for follow-up.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect CodaDocs, packs, automations.
  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.