Telegram RAG pdf
Configured with Chain Retrieval Qa, Document Default Data Loader, Embeddings Open Ai, Limit, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- AI & models
- Files / media
- Transform
- Routing
- Data store
- Code
- Messaging
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Telegram Trigger | Trigger | Telegram Trigger | See node parameters |
| Embeddings OpenAI | AI & models | Embeddings Open Ai | See node parameters |
| Default Data Loader | Files / media | Document Default Data Loader | See node parameters |
| Recursive Character Text Splitter | Transform | Text Splitter Recursive Character Text Splitter | See node parameters |
| Stop and Error | Routing | Stop And Error | See node parameters |
| Question and Answer Chain | AI & models | Chain Retrieval Qa | See node parameters |
| Vector Store Retriever | AI & models | Retriever Vector Store | See node parameters |
| Pinecone Vector Store1 | Data store | Vector Store Pinecone | See node parameters |
| Groq Chat Model | AI & models | LM Chat Groq | See node parameters |
| Check If is a document | Routing | If | See node parameters |
| Change to application/pdf | Code | Code | See node parameters |
| Telegram get File | Messaging | Telegram | file |
| Embeddings | AI & models | Embeddings Open Ai | See node parameters |
| Telegram Response | Messaging | Telegram | See node parameters |
| Telegram Response about Database | Messaging | Telegram | See node parameters |
| Stop and Error1 | Routing | Stop And Error | See node parameters |
| Pinecone Vector Store | Data store | Vector Store Pinecone | See node parameters |
| Limit to 1 | Transform | Limit | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
groqApiopenAiApipineconeApitelegramApi
Workflow notes
Load data into database
Load data into database
Fetch file from Telegram, split it into chunks and insert into Pinecone index, a message from Telegram will be sent just to let the user know that the process finished
Chat with Database
Chat with Database
- Receive the incoming chat message.
- Retrieve relevant chunks from the vector store.
- Pass these chunks to the model.
The model will use the retrieved information to formulate a precise response.
Telegram RAG pdf
Telegram RAG pdf
Purpose and structure
This folder contains the Telegram RAG pdf workflow. Its executable nodes use chainRetrievalQa, code, documentDefaultDataLoader, embeddingsOpenAi, if, limit, lmChatGroq, retrieverVectorStore, stopAndError, telegram, telegramTrigger, textSplitterRecursiveCharacterTextSplitter, vectorStorePinecone. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Telegram Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Stopanderror/1689_Stopanderror_Telegram_Automation_Triggered.json MIT; preserve source notices.