Block 1 - New File Trigger
- Type / Role
- n8n-nodes-base.googleDriveTrigger - googleDriveTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
How it works This workflow creates an intelligent Telegram bot with a knowledge base powered by Qdrant vector database. The bot automatically processes documents uploaded to Google Drive, stores th...
n8n-nodes-base.googledrivetrigger, n8n-nodes-base.googledrive, @n8n/n8n-nodes-langchain.documentdefaultdataloader, @n8n/n8n-nodes-langchain.textsplitterrecursivecharactertextsplitter, @n8n/n8n-nodes-langchain.vectorstoreqdrant, n8n-nodes-base.telegramtrigger, n8n-nodes-base.filter, @n8n/n8n-nodes-langchain.embeddingsopenai
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Konstantin.
Original n8n.io sourceThis workflow creates an intelligent Telegram bot with a knowledge base powered by Qdrant vector database. The bot automatically processes documents uploaded to Google Drive, stores them as embeddings, and uses this knowledge to answer questions in Telegram. It consists of two independent flows: document processing (Google Drive → Qdrant) and chat interaction (Telegram → AI Agent → Telegram).
Document Processing Flow:
Telegram Chat Flow:
Estimated set up time: 15 minutes
Google Drive Setup:
Qdrant Setup:
OpenAI Setup:
gpt-4-turbo.Telegram Setup:
26899549 with your Telegram user ID).Customize System Prompt (Optional):
Activate the Workflow:
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 | Create an AI Telegram bot using Google Drive, Qdrant, and OpenAI GPT-4.1 |
|---|---|
| Complexity | advanced |
| Nodes | 19 |
| Categories | Internal Wiki, AI RAG |
| Author | Konstantin |
| Published | 28 Dec 2025 |
Use the JSON export at /data/workflows/12228/12228.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.
How it works This workflow creates an intelligent Telegram bot with a knowledge base powered by Qdrant vector database. The bot automatically processes documents uploaded to Google Drive, stores th...
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.