Every growing company ends up answering the same questions over and over: the leave policy, the expense process, how the refund flow works. This template gives you a chatbot that answers from your own documents instead of guessing. It has two chains. The answer chain takes a question from the Chat Trigger, turns it into an embedding, searches your vector database for the most relevant chunks, and has the Answer from Docs agent reply using only that retrieved context — if the answer is not in the documents, it says so instead of hallucinating. The ingestion chain is separate: POST document text to the Ingest Webhook Trigger and it gets embedded and upserted into your docs collection, ready for retrieval.
The HR lead onboarding at a 40-person agency
New hires ask the same ten questions for their first month: notice period, work-from-home rules, the leave approval chain. The HR lead ingests the employee handbook through the Ingest Webhook Trigger — Prepare Document normalizes the text and passes the document ID through — and embeds it with the same model used for questions, text-embedding-3-small. From then on, new joiners ask the chat and get answers grounded in the actual handbook. Practical tip: when the handbook is updated, re-POST the revised text with the same doc_id so the vector store always reflects the current policy, and the honest fallback means the bot says it does not know rather than inventing a policy.
The SaaS support team with a sprawling help center
A support team of five fields tickets about a product with hundreds of help articles. They ingest the articles once, and agents use the chat internally to pull exact answers instead of searching the help center mid-ticket. Because Search Vector DB returns the most relevant chunks and Build Context assembles them with the original question, the agent answers with the evidence in front of it. Practical tip: raise the limit in Search Vector DB when answers need broader context, or lower it for faster responses on simple lookups — and edit the system prompt in Answer from Docs to require citations from specific chunks when support needs to quote chapter and verse.
The franchise network with a 300-page operations manual
Franchisees call headquarters about procedures that are all written down — in a manual nobody opens. The franchisor ingests the operations manual section by section through the webhook, and franchise owners ask the chat about everything from opening checklists to supplier escalation. The doc-ID passthrough in Prepare Document keeps each section addressable, so updates to one chapter do not require re-ingesting the whole manual. Practical tip: add a Code node after Prepare Document to split long chapters into overlapping chunks before embedding, which keeps retrieval precise on very long documents.
The compliance officer who needs sourced answers
A compliance officer answering "what does our policy say about data retention" needs the actual policy language, not a paraphrase. The Build Context node formats retrieved chunks into clean fields, and the agent answers only from that evidence. Practical tip: harden the grounding further by editing the agent's system prompt to quote the source chunk verbatim for policy questions, and schedule ingestion from Google Drive or Notion by swapping the Ingest Webhook Trigger for a Schedule Trigger so policy updates flow in on a cadence.
The consultancy productizing internal knowledge
A 25-person consultancy keeps its playbooks in scattered docs that only seniors know. Ingesting them into the docs collection turns tribal knowledge into something every junior can query on day one. The vector database can be Qdrant, Pinecone, or similar — Search Vector DB and Build Context expect Qdrant-style results, so if your provider returns a different shape, adjust the expression in Build Context. Practical tip: keep the embedding model identical in Embed Question and Embed Document — mismatched models silently break retrieval, which is the single most common setup mistake with this template.