AI & RAG

Keep the SOP search index fresh when Dropbox documents change

On a schedule, detects added or updated SOP files in Dropbox, re-embeds them into the searchable corpus.

CategoryAI & RAG
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled reindex run fires (nightly)
  • ActionList SOP files changed in Dropbox since last runDropboxDropbox
  • LogicDiff against current index to find adds, updates, deletes
  • ActionChunk and embed changed documents with OpenAIOpenAI
  • OutputPublish an indexing changelog to ConfluenceConfluenceConfluence

What it does

A RAG answer is only as current as its index. This workflow runs on a schedule, finds SOP files in Dropbox that were created or modified since the last run, chunks and re-embeds them into the vector store, and removes entries for deleted files. It then publishes a short changelog page in Confluence listing what was indexed, so the operations team has a record of the corpus state over time.

When to use it

Use it whenever your SOPs change often and you need the answer bot to reflect the latest version without manual reindexing. Pair it with the answering workflows so techs always get current guidance.

How it works

  1. 1A scheduled trigger fires the indexing run (for example nightly).
  2. 2Dropbox is queried for files changed since the last successful run.
  3. 3New and updated documents are chunked and embedded with OpenAI, and stale entries are purged.
  4. 4The refreshed vectors are written back to the corpus index.
  5. 5A changelog summarizing indexed, updated, and removed files is published to Confluence.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DropboxFiles and folders.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect ConfluenceSpaces, pages, blueprints.
  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.