AI & RAG
Re-Index Versioned Policy Library When Confluence Pages Change
Watches your Confluence policy space for edits and incrementally re-embeds only changed pages into Supabase.
How it runs
The automated pipeline, trigger to output.
- TriggerConfluence policy page published or updatedConfluence
- ActionFetch current page content and version numberConfluence
- LogicDiff against stored version; skip if unchanged
- ActionChunk by paragraph and embed with OpenAIOpenAI
- OutputUpsert vectors into Supabase and mark superseded versionsSupabase
What it does
Keeps the retrieval index behind your contract Q&A in lockstep with your source-of-truth policies. When a Confluence policy page is published or updated, the flow re-chunks just that page, regenerates embeddings, and upserts them into Supabase with the new version number and stable paragraph anchors.
When to use it
Use it whenever your policies change often enough that stale answers are a real risk. It guarantees that clause citations resolve to the live paragraph and that superseded language is marked, so legal teams trust the system as the canonical lookup.
How it works
- 1A Confluence page-updated event triggers the flow with the page ID.
- 2The flow fetches the full current page content and its version number from Confluence.
- 3A logic step diffs against the stored version and skips if content is unchanged.
- 4Changed pages are split into paragraph-level chunks, each tagged with page title, version, and anchor.
- 5OpenAI generates embeddings for the new chunks.
- 6The flow upserts vectors into Supabase, marking prior-version chunks as superseded so retrieval prefers current text.
Set it up
What you configure once, before turning it on.
- 1Connect ConfluenceSpaces, pages, blueprints.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SupabaseTables, auth, storage, edge functions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI & RAG workflows
Coda-grounded sales answer bot with citations in Slack
Reps ask product, pricing, or competitive questions in Slack and get an answer drawn only from your Coda knowledge hub, with links to the exact docs and rows it pulled from.
Weekly knowledge-gap digest from unanswered rep questions
Each week, scans rep questions the answer bot couldn't ground in Coda, clusters the recurring gaps.
Pre-meeting prep brief grounded in Coda and CRM
Before each booked sales meeting, builds a one-page prep brief by combining the account's HubSpot context with grounded talking points and objection responses pulled from your…
Publish a Grounded API FAQ Page to Confluence Weekly
Each week, clusters the top unanswered or repeated API questions, generates spec-grounded answers with citations.
Detect Breaking API Changes from Spec Diffs and Alert Owners
Compares the new OpenAPI spec against the previous version on each GitLab merge, uses retrieval over the changelog to classify whether changes are breaking.
Re-Index API Specs on GitLab Merge to Keep the Answer Bot Fresh
Watches GitLab merges to your API repo, detects changed OpenAPI specs and changelog files, re-chunks and re-embeds only what changed.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.