AI & RAG
On-demand API: return commit-cited rationale for any config key
A webhook accepts a repo path and config key and returns a JSON answer explaining why that value is set, grounded in the introducing commit and linked ADR, so dashboards, IDE…
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives repo path + config keyHTTP webhook
- LogicValidate input and resolve the config file
- ActionRun GitLab blame/log for the introducing commitGitLab
- ActionRetrieve matching ADR from ConfluenceConfluence
- ActionCompose grounded explanation from sources
- OutputReturn JSON with value, rationale, SHA, and ADR linkHTTP webhook
What it does
Exposes config-rationale retrieval as a callable HTTP endpoint. Send it a repo path and a config key; get back structured JSON with the current value, the explanation of why it's set, the introducing commit SHA, the author, and any cited ADR. Other tools embed this without scraping Git themselves.
When to use it
When you want rationale lookups available programmatically — inside an internal dashboard, an IDE hover plugin, an incident runbook, or a chatops integration you already maintain. One source of truth, many consumers.
How it works
- 1An HTTP webhook receives a request with repo path and config key.
- 2A logic step validates the input and resolves the file location.
- 3The workflow runs GitLab blame/log to find the introducing commit and message.
- 4It retrieves the matching ADR from Confluence by reference or similarity.
- 5The agent composes a concise grounded explanation tied to those sources.
- 6It returns a JSON response with value, rationale, commit SHA, author, and ADR link.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 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.