AI & RAG
Flag duplicate root causes when a new postmortem is filed
When a new postmortem is published in Confluence, searches the existing corpus for prior incidents with the same root cause and comments on the page with the matches.
How it runs
The automated pipeline, trigger to output.
- TriggerNew postmortem published in ConfluenceConfluence
- ActionEmbed root cause and vector-search prior incidentsPostgres
- LogicKeep related matches, exclude the page itself
- ActionDraft grounded related-incidents noteOpenAI
- OutputComment on the Confluence page with related historyConfluence
What it does
This closes the loop at write time. As soon as a new postmortem page is published in Confluence, the workflow embeds its root-cause and symptom sections, searches the existing corpus for prior incidents that share the same underlying cause, and posts a comment on the new page listing the related historical incidents with links. Authors immediately see whether they are documenting a fresh problem or a repeat — and can cross-link instead of fragmenting the record.
When to use it
When postmortems live in Confluence and you want recurrence visible at authoring time, not discovered months later. It quietly improves corpus quality by encouraging cross-references.
How it works
- 1A new or newly published Confluence postmortem page triggers the flow.
- 2Its root-cause and symptom text is embedded and vector-searched against the Postgres corpus.
- 3A relevance gate keeps only genuinely related prior incidents and excludes the page itself.
- 4An LLM writes a short 'related incidents' note grounded on the matches, with links.
- 5The note is posted as a comment on the Confluence postmortem page.
Set it up
What you configure once, before turning it on.
- 1Connect ConfluenceSpaces, pages, blueprints.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect OpenAIModels, embeddings, files.
- 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
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.