AI & RAG
Ask 'why is this config set this way?' in Slack, answered from Git + ADRs
An operator asks why a setting has its current value in a Slack channel, and a RAG agent answers with the rationale traced from the commit that introduced it and any linked ADR.
How it runs
The automated pipeline, trigger to output.
- TriggerEngineer asks a config question in SlackSlack
- ActionFind the commit that last changed the config line via GitLab blame/logGitLab
- ActionSearch Confluence ADRs for matching rationaleConfluence
- ActionSynthesize a grounded answer from commit + ADR text
- OutputReply in-thread with rationale, commit SHA, and ADR linkSlack
What it does
Lets engineers ask plain-English questions like "why is the connection pool capped at 20?" in Slack and get a grounded answer that traces the value back to the commit that set it and the architecture decision record (ADR) that justified it. Every answer cites a commit SHA and, where one exists, an ADR ID and link.
When to use it
When tribal knowledge about config keeps getting lost, new hires keep asking "who set this and why," or a value looks wrong and someone needs the original reasoning before changing it. Best for teams keeping ADRs in Confluence and config in GitLab.
How it works
- 1A Slack slash command or mention captures the config question and the file or key in question.
- 2The agent runs `git log -p` / blame against the GitLab repo to find the commit that last changed that line and its message body.
- 3It searches Confluence ADRs for terms from the commit message and the config key.
- 4It synthesizes the rationale, grounding the answer in the retrieved commit and ADR text only.
- 5It replies in-thread with the explanation plus cited SHA and ADR link.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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.