AI & RAG

ADR Index Sync: scheduled Confluence-to-Postgres embedding refresh

On a schedule, pulls new and edited ADR pages from Confluence, generates embeddings, and upserts them into the Postgres decision index so the answerbot always retrieves current…

CategoryAI & RAG
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled refresh timer fires
  • ActionFetch ADR pages changed since watermark from ConfluenceConfluenceConfluence
  • LogicExit early if no pages changed
  • ActionGenerate embeddings for changed pages with OpenAIOpenAI
  • OutputUpsert vectors and metadata into Postgres indexPostgreSQLPostgres

What it does

Keeps the retrieval index behind your ADR answerbot fresh. It scans the Confluence ADR space for pages created or changed since the last run, re-embeds them, and upserts the vectors plus metadata into Postgres so searches never return stale or missing decisions.

When to use it

Run this as the ingestion backbone for any ADR RAG setup. Use it when ADRs change often, when a new decision should be answerable within minutes, or when you want embeddings recomputed without a manual reindex.

How it works

  1. 1A scheduled timer fires (e.g. every 30 minutes).
  2. 2The flow queries Confluence for ADR pages with a lastModified newer than the stored watermark.
  3. 3A branch checks whether any pages changed; if none, it exits cleanly.
  4. 4For each changed page, OpenAI produces an embedding of the chunked body.
  5. 5The embeddings, page id, version, status, and title upsert into the Postgres index, and the watermark advances.

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.