AI & RAG
Re-index ReadMe corpus into a vector store on every doc publish
When a ReadMe page is published or updated, it re-chunks and re-embeds that page and upserts the vectors into Postgres so the answer endpoint always grounds on the latest docs.
How it runs
The automated pipeline, trigger to output.
- TriggerReadMe page published/updated eventHTTP webhook
- ActionFetch current page content from ReadMeReadMe
- ActionChunk and embed page sectionsOpenAI
- LogicDecide upsert vs prune removed sections
- OutputUpsert vectors and metadata into PostgresPostgres
What it does
Keeps your retrieval index in sync with ReadMe. On every publish or edit event, it pulls the changed page, splits it into section-level chunks, generates embeddings, and upserts them into the Postgres vector table that your answer endpoint queries.
When to use it
Run this so your grounded answer endpoint never serves stale documentation. Essential when your docs change frequently and you cannot tolerate the index drifting from what developers actually read.
How it works
- 1A ReadMe publish/update event fires the webhook with the affected page identifier.
- 2The current page content is fetched from ReadMe so you index exactly what shipped.
- 3The page is split into section-level chunks preserving heading anchors for later citation.
- 4Each chunk is embedded by the model.
- 5A logic step decides upsert vs delete: removed sections are pruned, changed sections overwritten.
- 6The vectors and section metadata are upserted into Postgres, keeping the corpus current.
Set it up
What you configure once, before turning it on.
- 1Connect ReadMeAPI docs, changelog, auth.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI & RAG workflows
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.
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…
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.
RFP and security questionnaire drafter grounded in Coda
Drafts answers to inbound RFP and security questionnaire questions by retrieving approved language from your Coda hub, then files the cited draft for review before a rep sends it.
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.