AI & RAG
Weekly runbook citation freshness auditor
Scans every runbook page the answer bot cites, flags pages not updated since their referenced code last changed in GitHub.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires the freshness audit
- ActionList runbook pages and edit dates from ConfluenceConfluence
- ActionFetch latest commit date for each cited repo pathGitHub
- LogicFlag pages where code changed after the doc's last edit
- ActionRecord staleness scores in Postgres audit tablePostgres
- OutputPost worst-offenders digest to docs Slack channelSlack
What it does
Keeps the knowledge base honest by detecting runbook pages whose cited procedures may be out of date. It cross-references each Confluence page's last-edited date against the most recent change to the GitHub paths it documents, surfacing drift before it misleads an engineer.
When to use it
Run it weekly when your runbook wiki is large enough that no one manually reviews freshness, and you need confidence that cited answers reflect the current system rather than last quarter's architecture.
How it works
- 1A weekly schedule kicks off the audit.
- 2The flow pulls the list of runbook pages and their last-modified timestamps from Confluence.
- 3For each page, it reads the referenced repo paths and queries GitHub for the latest commit touching them.
- 4A comparison flags any page whose code moved after the doc's last edit, scoring severity by how far behind it is.
- 5Flagged pages are written to a Postgres audit table for trend tracking.
- 6A digest of the worst offenders posts to the docs channel in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect ConfluenceSpaces, pages, blueprints.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.