Block 1 - On form submission
- Type / Role
- n8n-nodes-base.formTrigger - formTrigger
- Config choices
- Version 2.5
This workflow automatically converts uploaded documents and text into an AI powered searchable knowledge base using semantic vector embeddings and Retrieval Augmented Generation (RAG). Users can up...
n8n-nodes-base.formtrigger, @n8n/n8n-nodes-langchain.vectorstorepgvector, @n8n/n8n-nodes-langchain.embeddingsollama, @n8n/n8n-nodes-langchain.documentdefaultdataloader, @n8n/n8n-nodes-langchain.chainretrievalqa, @n8n/n8n-nodes-langchain.lmchatollama, @n8n/n8n-nodes-langchain.retrievervectorstore, n8n-nodes-base.extractfromfile
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Jyothish S L.
Original n8n.io sourceThis workflow automatically converts uploaded documents and text into an AI-powered searchable knowledge base using semantic vector embeddings and Retrieval-Augmented Generation (RAG). Users can upload PDFs, JSON, CSV, XLS, XLSX, or raw text files, which are automatically processed, chunked, embedded, and stored in PostgreSQL PGVector for intelligent retrieval.Questions can then be asked directly through Telegram, where the system retrieves relevant context and generates AI-powered responses using Ollama and Llama 3.
⚙️ How it works
Users can upload files or raw text through an n8n form interface. The workflow automatically extracts content from supported formats such as PDF, JSON, CSV, XLS, XLSX, and plain text, then splits the content into searchable chunks. Using the nomic-embed-text embedding model, vector embeddings are generated and stored in PostgreSQL with PGVector for semantic retrieval. Users can then ask questions through Telegram, where the system performs semantic similarity search to retrieve the most relevant document context. Finally, Llama 3 running via Ollama generates an AI-powered contextual response, which is sent back to the user through the Telegram bot.
📦 Requirements
• Ollama • Llama 3 model • nomic-embed-text embedding model • PostgreSQL with PGVector extension • Telegram Bot API credentials • Docker • Cloudflare Tunnel or ngrok (optional for public access)
📚 Supported File Types
• PDF • JSON • CSV • XLS • XLSX • Plain Text
🚀 Use Cases
• Personal AI knowledge base • AI document assistant • Semantic document search • Internal company knowledge retrieval • Telegram AI chatbot • Private/self-hosted RAG system
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 40 workflow blocks. Download the JSON for the full node graph.
| Workflow | Create an AI knowledge base assistant using Ollama, PGVector and Telegram |
|---|---|
| Complexity | advanced |
| Nodes | 40 |
| Categories | Internal Wiki, AI RAG |
| Author | Jyothish S L |
| Published | 14 May 2026 |
Use the JSON export at /data/workflows/15707/15707.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
This workflow automatically converts uploaded documents and text into an AI powered searchable knowledge base using semantic vector embeddings and Retrieval Augmented Generation (RAG). Users can up...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Internal Wiki, AI RAG use case.