AI & RAG

Nightly policy index sync from Confluence and Drive

Runs every night to pull new and changed Confluence pages and Google Drive docs, chunk and embed them.

CategoryAI & RAG
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule fires
  • ActionList changed Confluence pages + Drive filesConfluenceConfluence
  • LogicBranch: deletions vs. new/updated docs
  • ActionChunk and embed changed documents (OpenAI)OpenAI
  • OutputUpsert vectors into Supabase indexSupabaseSupabase

What it does

Keeps your retrieval index fresh. On a schedule it detects which Confluence pages and Drive files changed since the last run, re-chunks and re-embeds only those, and upserts them into Supabase. Deleted documents are tombstoned so stale policy never resurfaces in answers.

When to use it

Use it as the backbone for any policy Q&A bot. Run it nightly (or hourly) so the index never drifts from the source of truth. Essential when handbooks and SOPs change often and answering from outdated text would be a compliance risk.

How it works

  1. 1A scheduled trigger fires the sync (e.g. nightly at 2am).
  2. 2The workflow lists Confluence pages and Drive files modified since the last checkpoint.
  3. 3A branch routes deletions to tombstoning and updates to re-embedding.
  4. 4Changed documents are chunked and embedded with OpenAI.
  5. 5New vectors are upserted into the Supabase store and the checkpoint timestamp is advanced.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ConfluenceSpaces, pages, blueprints.
  2. 2
    Connect Google DriveDocs, sheets, slides, files.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect SupabaseTables, auth, storage, edge functions.
  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.