AI & RAG

Keep the support knowledge index fresh from Confluence changes

On a schedule, pulls newly created and edited Confluence pages, re-embeds them with OpenAI, and upserts the vectors into Supabase so retrieval always reflects the latest docs.

CategoryAI & RAG
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled reindex run
  • ActionFetch pages changed since last sync from ConfluenceConfluenceConfluence
  • LogicSkip run if no pages changed
  • ActionChunk and embed updated pages with OpenAIOpenAI
  • OutputUpsert vectors and prune stale chunks in SupabaseSupabaseSupabase

What it does

Maintains the vector index that every RAG support workflow reads from. It periodically detects which Confluence pages changed since the last run, regenerates their embeddings, and writes them back to Supabase — removing stale chunks for deleted or rewritten pages so answers never quote outdated docs.

When to use it

Run this alongside any docs-grounded answering workflow. Essential when your knowledge base changes weekly and you can't afford support bots citing superseded instructions.

How it works

  1. 1A schedule (for example, hourly) fires the trigger.
  2. 2Confluence is queried for pages created or modified since the last successful sync.
  3. 3A branch skips the run cleanly when nothing has changed.
  4. 4Changed pages are chunked and embedded with OpenAI.
  5. 5The new vectors are upserted into Supabase and obsolete chunks for those pages are deleted, keeping the index in lockstep with the 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 SupabaseTables, auth, storage, edge functions.
  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.