🐋🤖 DeepSeek AI Agent + Telegram + LONG TERM Memory 🧠

n8n template #2864

Summary

This n8n workflow template is designed to integrate a DeepSeek AI agent with Telegram, incorporating long-term memory capabilities for personalized and context-aware responses. Here's a detailed breakdown: Core Features Telegram Integration Uses a webhook to receive messages from Telegram users. Validates user identity and message content before processing. AI-Powered Responses Employs DeepSeek's AI models for conversational interactions. Includes memory capabilities to personalize responses based on past interactions. Error Handling Sends an error message if the input cannot be processed. Model Options 🧠 DeepSeek-V3 Chat: Handles general conversational tasks. DeepSeek-R1 Reasoning: Provide

How to set it up

Open template #2864 on n8n.io and click Use for free, or copy the template JSON and paste it onto an empty canvas in n8n.
Create 3 credentials under Credentials → Add credential: Telegram, Google Docs, OpenAI Chat Model. Then open each of those nodes and pick the credential.
Check the model in the AI Agent node. The template may point at a model your account can't use; swap it for one you have access to.
Click Execute workflow and step through each node's output to confirm the data looks right.
Toggle the workflow to Active so its trigger runs on its own.

Hand off to your agent

Prompt

Help me set up the n8n workflow "🐋🤖 DeepSeek AI Agent + Telegram + LONG TERM Memory 🧠" (https://n8n.io/workflows/2864). It uses: Telegram, Google Docs, AI Agent, OpenAI Chat Model, Simple Memory. Import the template JSON into my n8n instance, list every credential I need to create, and walk me through testing it.

Paste into Claude Code and it will do the rest.

Apps and nodes

Telegram Google Docs AI Agent OpenAI Chat Model Simple Memory

Questions

Yes. Joseph LePage published it free on n8n.io as a verified creator, and it has 29K views. It runs on n8n Cloud or a self-hosted n8n instance.

Telegram, Google Docs, OpenAI Chat Model. The other 2 nodes are built into n8n.

Similar workflows

NameViews