Build a Pipedrive MCP server with Google Gemini AI
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: AI Agent v1 (old agent modes). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 25 nodes and runs on Telegram events (message) (plus 1 other trigger). Along the way it connects Telegram, Google Gemini Chat Model, MCP Client and Pipedrive and 1 more.
How it runs
Trigger: On Telegram events (message) (plus 1 other trigger).
- AI Agent: runs an AI agent, with model: Google Gemini Chat Model; 1 tool (MCP Client); memory: Simple Memory
- Send summary (Gmail): uses Gmail
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- AI Agent v1 (old agent modes) in AI Agent (v1.9): 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 |
|---|---|
| AI Agent v1 (old agent modes) AI Agent (v1.9) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (8)
- Telegram Trigger
n8n-nodes-base.telegramTrigger - AI Agent
@n8n/n8n-nodes-langchain.agent - Simple Memory
@n8n/n8n-nodes-langchain.memoryBufferWindow - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - MCP Client Tool
@n8n/n8n-nodes-langchain.mcpClientTool - MCP Server Trigger
@n8n/n8n-nodes-langchain.mcpTrigger - Pipedrive Tool
n8n-nodes-base.pipedriveTool - Gmail
n8n-nodes-base.gmail
From the author
This n8n workflow leverages the power of AI and automation to streamline Pipedrive's CRM operations using natural language commands. It allows you to interact with your Deals, Leads, Persons, and Organizations simply by sending a message. How it Works The…