AgeBridge
AgeBridge Guided Project · IntermediateAbout 9 hoursPro

Internal knowledge assistant for a team

Anyone in the team types /ask in Slack and gets the answer from the company's own procedures with a link to the document, or a clear 'not in our documents, ask this person'.

What you'll have at the end

An n8n workflow behind a Slack /ask command that answers from five procedure documents indexed from a Drive folder, links the document it used, refuses anything the folder does not cover by name, logs every refusal, and re-indexes itself every night.

What it proves

retrieval from documentsnot-found fallbacknightly refresh

Accounts to create

n8nNode-based workflows; cloud trial or self-hostedDocsFree offerGoogle DriveFolders that trigger workflowsDocsSupabasePostgres, auth and vectors, free tierDocsFree offerOpenAI APISubstitute for Claude in chat steps; provides the embeddingsDocsFree offerClaude APIThe model behind the steps; pay per useDocsFree offerSlackAlerts and approval buttonsDocs

What it costs: Free tiers everywhere, plus a few cents: OpenAI is used only to turn text into vectors, Claude writes the answers.

Have this ready

  • A made-up company with procedures, described in one line
  • A Slack workspace where you are allowed to install an app
  • The name of the person an unanswered question should go to

How it fits together

Drive: Proceduresfive documents, the only sourcen8n indexnightly, empties and refillsprocedures in Supabasetext plus vector plus link/ask in Slackanyone in the teamClaudeanswers only from the four closest chunksAnswer with the linkor: not in our documentsunanswered tablewhat the folder is missing
  1. Drive: Procedures: five documents, the only source
  2. n8n index: nightly, empties and refills
  3. procedures in Supabase: text plus vector plus link
  4. /ask in Slack: anyone in the team
  5. Claude: answers only from the four closest chunks
  6. Answer with the link: or: not in our documents
  7. unanswered table: what the folder is missing

The steps

  1. 1. Five procedures and a place to keep them

    A Drive folder that is the only source of truth for the assistant, and a Supabase project with the table, the search function and the log of questions nobody could answer.

  2. 2. From the folder to plain text

    One n8n item per document, holding the document's title, its link and its words. Getting this right is most of the work; the vectors in the next step are the easy part.

  3. 3. The procedures become vectors

    The same five items written into procedures as text plus a vector plus the link, after the table is emptied. Emptying first is what makes the nightly run safe to repeat.

  4. 4. /ask in Slack reaches n8n

    A slash command anyone in the team can type, an instant acknowledgement so Slack does not time out, and the question waiting in n8n as a plain field.

  5. 5. The answer, or an honest refusal

    Four pieces of procedure, one answer that may use nothing else, a link to the document it came from, and a written refusal with a name on it when the folder does not cover the question.

  6. 6. Nightly refresh, then live

    The index rebuilds itself while nobody is watching, the slash command points at the production URL, and you prove that editing a document changes tomorrow's answer.