Block 1 - When chat message received
- Type / Role
- @n8n/n8n-nodes-langchain.chatTrigger - chatTrigger
- Config choices
- Version 1.1
This workflow is provided as-is. Please review and test before using in production.
Talk to Your Apps: Building a Personal Assistant MCP Server with Google Gemini Wouldn't it be cool to just tell your computer or phone to "schedule a meeting with Sarah next Tuesday at 3 PM" or "fi...
@n8n/n8n-nodes-langchain.chattrigger, @n8n/n8n-nodes-langchain.lmchatgooglegemini, @n8n/n8n-nodes-langchain.memorybufferwindow, @n8n/n8n-nodes-langchain.mcptrigger, @n8n/n8n-nodes-langchain.mcpclienttool, n8n-nodes-base.googlecalendartool, n8n-nodes-base.gmailtool, @n8n/n8n-nodes-langchain.agent
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Aitor | 1Node.
Original n8n.io sourceWouldn't it be cool to just tell your computer or phone to "schedule a meeting with Sarah next Tuesday at 3 PM" or "find John Doe's email address" and have it actually do it? That's the dream of a personal assistant!
With n8n and the power of MCP and AI models like Google Gemini, you can actually build something pretty close to that. We've put together a workflow that shows you how you can use a natural language chat interface to interact with your other apps, like your CRM, email, and calendar.
Before you dive in, you'll need a few things:
Imagine this workflow is like a helpful assistant who sits between you and your computer.
Step 1: You Talk, the AI Agent Listens
It all starts when you send a message through your connected chat interface. Think of this as you speaking directly to your assistant.
Step 2: The Assistant's Brain (Google Gemini)
Your message goes straight to the assistant's "brain." In this case, the brain is powered by a smart AI model like Google Gemini. In our template we are using the latest Gemini 2.5 Pro. But this is totally up to you. Experiment and track which model fits the kind of tasks you will pass to the agent. Its job is to understand exactly what you're asking for.
The brain also uses a "memory" so it can remember what you've talked about recently, making the conversation feel more natural. We are using the default context window, which is the past 5 interactions.
Step 3: The Assistant Decides What Tool to Use
Once the brain understands your request, the assistant figures out the best way to help you. It looks at the request and thinks, "Okay, to do this, I need to use one of my tools."
Step 4: The Assistant's Toolbox (MCP & Your Apps)
Here's where the "MCP" part comes in. Think of "MCP" (Model Context Protocol) as the assistant's special toolbox. Inside this toolbox are connections to all the different apps and services you use – your CRM for contacts, your email service, and your calendar.
The MCP system acts like a manager for these tools, making them available to the assistant whenever they're needed.
Step 5: Using the Right Tool for the Job
Based on what you asked for, the assistant picks the correct tool from the toolbox.
Step 6: The Tool Takes Action
Now, the node or set of nodes get to work! It performs the action you requested within the specific app.
Step 7: Task Completed!
And just like that, your request is handled automatically, all because you simply told your assistant what you wanted in plain language.
This kind of workflow shows the power of combining AI with automation platforms like n8n. You can move beyond clicking buttons and filling out forms, and instead, interact with your digital life using natural conversation. n8n makes it possible to visually build these complex connections between your chat, the AI brain, and all your different apps.
This is just the start! You could enhance this personal assistant by:
Imagine the dozens of hours your team could save weekly by automating repetitive tasks through a simple, natural language interface.
Feel free to contact us at 1 Node. Get instant access to a library of free resources we created.
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 | Build a personal assistant with Google Gemini, Gmail and Calendar using MCP |
|---|---|
| Complexity | advanced |
| Nodes | 20 |
| Categories | Personal Productivity, AI Chatbot |
| Author | Aitor | 1Node |
| Published | 06 May 2025 |
Use the JSON export at /data/workflows/3905/3905.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.
Talk to Your Apps: Building a Personal Assistant MCP Server with Google Gemini Wouldn't it be cool to just tell your computer or phone to "schedule a meeting with Sarah next Tuesday at 3 PM" or "fi...
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 Personal Productivity, AI Chatbot use case.