Build a comprehensive multimodal assistant on Telegram with OpenAI, SERP and Vector Store
Needs changesNeeds changes. This template uses 3 thing(s) that n8n 3.0 removes: HTTP Request Tool (legacy), SerpApi (Google Search), AI Agent v1 (old agent modes). 3 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 33 nodes and runs on Telegram events (message). Along the way it connects Telegram, OpenAI, Embeddings OpenAI and HTTP Request and 2 more. It also calls api.openai.com over HTTP.
How it runs
Trigger: On Telegram events (message).
- API Setup (Edit Fields (Set)): sets 1 field: JINA_API
- Switch: routes items into 4 branches
- Download Image (Telegram): work with file
- Get Audio File (Telegram): work with file
- Format-text-output (Edit Fields (Set)): sets 2 fields: chat_input, type
- Download Document (Telegram): work with file
- Fix File Extension (Code): runs custom JavaScript code
- Transcribe (OpenAI): transcribe (audio)
- J.A.R.V.I.S. (AI Agent): runs an AI agent, with model: OpenAI Chat Model; 6 tools (Think, Calculator, Image Generator, Webpage Scraper…); memory: Window Buffer Memory
- Convert Doc (Code): runs custom JavaScript code
…plus 10 more steps. See the full node list below.
Services it uses
HTTP calls to: api.openai.com
Before you upgrade to n8n 3.0
3 things in this workflow are removed in n8n 3.0. Fix them before you upgrade:
- HTTP Request Tool (legacy) in Image Generator, Webpage Scraper: replace with HTTP Request node connected to the AI Agent's Tool input.
- SerpApi (Google Search) in Basic Google Search: no direct replacement: call the SerpApi REST API with an HTTP Request tool, or use a verified community node.
- AI Agent v1 (old agent modes) in J.A.R.V.I.S. (v1.7): replace with Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| HTTP Request Tool (legacy) Image Generator, Webpage Scraper | HTTP Request node connected to the AI Agent's Tool input |
| SerpApi (Google Search) Basic Google Search | No direct replacement: call the SerpApi REST API with an HTTP Request tool, or use a verified community node |
| AI Agent v1 (old agent modes) J.A.R.V.I.S. (v1.7) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (18)
- Telegram Trigger
n8n-nodes-base.telegramTrigger - Switch
n8n-nodes-base.switch - Telegram
n8n-nodes-base.telegram - Simple Memory
@n8n/n8n-nodes-langchain.memoryBufferWindow - OpenAI
@n8n/n8n-nodes-langchain.openAi - Code
n8n-nodes-base.code - Edit Fields (Set)
n8n-nodes-base.set - Simple Vector Store
@n8n/n8n-nodes-langchain.vectorStoreInMemory - Embeddings OpenAI
@n8n/n8n-nodes-langchain.embeddingsOpenAi - Default Data Loader
@n8n/n8n-nodes-langchain.documentDefaultDataLoader - Token Splitter
@n8n/n8n-nodes-langchain.textSplitterTokenSplitter - HTTP Request Tool
@n8n/n8n-nodes-langchain.toolHttpRequest - SerpApi (Google Search)
@n8n/n8n-nodes-langchain.toolSerpApi - Calculator
@n8n/n8n-nodes-langchain.toolCalculator - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Think Tool
@n8n/n8n-nodes-langchain.toolThink - AI Agent
@n8n/n8n-nodes-langchain.agent - If
n8n-nodes-base.if
From the author
J.A.R.V.I.S. Multimodal AI assistant on Telegram with OpenAI This workflow transforms your Telegram bot into J.A.R.V.I.S., a powerful, multimodal AI assistant. It can understand and process text, voice messages, images, and documents. The assistant can search…