AI & RAG

Incremental Runbook Re-Index on Confluence Page Update

Listens for Confluence page edits, re-chunks only the changed runbook page into heading-anchored sections, re-embeds them, and upserts the vectors in Postgres so the answer bot…

CategoryAI & RAG
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerConfluence page created or updated webhook firesConfluenceConfluence
  • ActionFetch page body and split into heading-anchored sectionsConfluenceConfluence
  • ActionEmbed each changed section with OpenAIOpenAI
  • ActionUpsert section vectors in Postgres by page ID, version, and anchorPostgreSQLPostgres
  • LogicPrune vectors for sections removed from the page

What it does

Keeps the RAG index fresh by reacting to individual Confluence edits instead of nightly full rebuilds. When a runbook page changes, it re-chunks that single page by heading, generates fresh embeddings, and upserts them into the vector store keyed by page ID, version, and heading anchor.

When to use it

Use it when your runbooks change often and a stale index would hand engineers outdated rollback or escalation steps. It also keeps embedding costs low by only reprocessing what actually changed.

How it works

  1. 1A Confluence webhook fires when a runbook page is created or updated.
  2. 2The flow fetches the page body and splits it into sections at each heading, capturing the anchor and version number.
  3. 3Each section is embedded via OpenAI.
  4. 4Vectors are upserted into Postgres keyed by page ID and heading anchor; sections deleted from the page are pruned.
  5. 5The run records the new version so citations always resolve to the live source.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ConfluenceSpaces, pages, blueprints.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  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.