Block 1 - AI Agent
- Type / Role
- @n8n/n8n-nodes-langchain.agent - agent
- Config choices
- Version 1.8
This workflow is provided as-is. Please review and test before using in production.
Description This workflow automates the creation of a Retrieval Augmented Generation (RAG) pipeline using content from the GLPI Knowledge Base. It retrieves and processes FAQ articles directly via ...
@n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatgooglegemini, @n8n/n8n-nodes-langchain.chattrigger, @n8n/n8n-nodes-langchain.embeddingsgooglegemini, n8n-nodes-base.stickynote, @n8n/n8n-nodes-langchain.vectorstorepgvector, @n8n/n8n-nodes-langchain.memorybufferwindow
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Thiago Vazzoler Loureiro.
Original n8n.io sourceThis workflow automates the creation of a Retrieval-Augmented Generation (RAG) pipeline using content from the GLPI Knowledge Base. It retrieves and processes FAQ articles directly via the GLPI API, cleans and vectorizes the content using pgvector in PostgreSQL, and prepares the data for use by LLM-powered AI agents.
Manually building a RAG pipeline from a GLPI knowledge base requires integrating multiple tools, cleaning data, and managing embeddings—tasks that are often complex and repetitive. This subworkflow simplifies the entire process by automating data retrieval, transformation, and vector storage, allowing you to focus on building intelligent support agents or chatbots powered by your internal documentation.
Connects to GLPI via API to fetch FAQ articles
Cleans and normalizes content for better embedding quality
Generates vector embeddings using Google Gemini (or another model)
Stores embeddings in a PostgreSQL database with pgvector
Fully modular: easily integrate with any RAG-ready LLM pipeline
Before using this subworkflow, make sure you have:
A GLPI instance installed on a Linux server with API access enabled
A PostgreSQL database with the pgvector extension installed
An OpenAI API key (or alternative embedding provider)
n8n instance (self-hosted or cloud)
This subworkflow is intended to be part of a larger AI pipeline. Attach it to a scheduled workflow (e.g. daily sync) or use it in response to updates in your GLPI base. Ideal for internal support bots, IT documentation assistants, and help desk AI agents that rely on up-to-date knowledge.
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.
| Workflow | Build a GLPI knowledge base RAG pipeline with Google Gemini and PostgreSQL |
|---|---|
| Complexity | intermediate |
| Nodes | 9 |
| Categories | Internal Wiki, Multimodal AI |
| Author | Thiago Vazzoler Loureiro |
| Published | 08 Aug 2025 |
Use the JSON export at /data/workflows/7171/7171.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.
Description This workflow automates the creation of a Retrieval Augmented Generation (RAG) pipeline using content from the GLPI Knowledge Base. It retrieves and processes FAQ articles directly via ...
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, Multimodal AI use case.