AI & RAG

Weekly Runbook Coverage Gaps Digest by Email

Analyzes the week's unanswered runbook questions, clusters them into missing-documentation themes with the closest existing sources, and emails a prioritized gaps report.

CategoryAI & RAG
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly scheduled digest run
  • ActionQuery unanswered question events from PostgresPostgreSQLPostgres
  • ActionCluster into gap themes and match nearest sourcesOpenAI
  • LogicRank themes by frequency and recency
  • OutputEmail prioritized gaps report to KB ownersGmailGmail

What it does

Closes the loop on questions the runbook agent could not answer. It reads the week's logged 'not documented' events from Postgres, clusters them into themes, and for each theme names the nearest existing Confluence or Drive doc plus what is missing. The result is a ranked report emailed to the knowledge-base owners so they know exactly what to write next.

When to use it

Use it alongside the answer bots to turn their refusals into a content backlog. Instead of guessing what documentation gaps exist, you get evidence: the real questions people asked that nothing covered, sorted by frequency.

How it works

  1. 1A scheduled weekly trigger starts the digest.
  2. 2The flow queries Postgres for the week's unanswered question events.
  3. 3OpenAI clusters the questions into gap themes and matches each to the closest existing source with a citation.
  4. 4A logic step ranks themes by frequency and recency.
  5. 5A formatted gaps report is emailed to the documentation owners via Gmail.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect ConfluenceSpaces, pages, blueprints.
  4. 4
    Connect GmailRead, draft, send, label.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.