AI & RAG

Slack RFC Answer-Bot Grounded in Confluence + GitHub

Answers engineering questions posted in Slack by retrieving relevant Confluence RFCs and GitHub code, then replies with a grounded answer and clickable source citations.

CategoryAI & RAG
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEngineer @-mentions bot in SlackSlack
  • ActionRetrieve matching RFC + code chunks from vector storeSupabaseSupabase
  • LogicGate: any chunk above similarity threshold?
  • ActionCompose grounded answer with citation markersOpenAI
  • OutputReply in Slack thread with linked citationsSlack

What it does

Turns a Slack channel into a self-serve engineering knowledge desk. When someone asks "how does our auth token refresh work?", the bot searches your Confluence RFC space and indexed GitHub code, composes an answer strictly from what it found, and posts back with inline citations linking to the exact page and file.

When to use it

When senior engineers keep answering the same architecture questions in Slack, or when onboarding hires need design context that lives across wikis and repos. Best when your RFCs are in Confluence and the implementation is in GitHub.

How it works

  1. 1An engineer @-mentions the bot in Slack with a question.
  2. 2The question is embedded and matched against a Supabase vector store of Confluence RFCs and GitHub source chunks.
  3. 3A relevance gate checks whether any chunk clears the similarity threshold; if nothing does, the bot replies that it has no grounded source and stops.
  4. 4OpenAI composes an answer constrained to the retrieved passages, with numbered citation markers.
  5. 5The bot posts the answer in-thread with each citation rendered as a Confluence/GitHub deep link.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect ConfluenceSpaces, pages, blueprints.
  3. 3
    Connect GitHubRepos, issues, pull requests, actions.
  4. 4
    Connect SupabaseTables, auth, storage, edge functions.
  5. 5
    Connect OpenAIModels, embeddings, files.
  6. 6
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  7. 7
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  8. 8
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.