Personal Assistant MCP server
Configured with Agent, Chat Trigger, Gmail Tool, Google Calendar Tool, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- AI & models
- Data store
- Integration
- Messaging
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| When chat message received | Trigger | Chat Trigger | See node parameters |
| Google Gemini Chat Model | AI & models | LM Chat Google Gemini | See node parameters |
| Simple Memory | Data store | Memory Buffer Window | See node parameters |
| MCP Server Trigger | Trigger | Mcp Trigger | See node parameters |
| MCP Client | Integration | Mcp Client Tool | See node parameters |
| Create event | Integration | Google Calendar Tool | See node parameters |
| Update event | Integration | Google Calendar Tool | update |
| Draft email | Messaging | Gmail Tool | draft |
| Personal Assistant | AI & models | Agent | See node parameters |
| Add new row | Data store | Google Sheets Tool | append |
| Find row | Data store | Google Sheets Tool | See node parameters |
| Update row | Data store | Google Sheets Tool | update |
| Find emails | Messaging | Gmail Tool | getAll |
| Find single event | Integration | Google Calendar Tool | get |
| Find multiple events | Integration | Google Calendar Tool | getAll |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
gmailOAuth2googleCalendarOAuth2ApigooglePalmApigoogleSheetsOAuth2Api
Workflow notes
Calendar nodes
Calendar nodes
You could order your agent to create a new event in your Google Calendar, find a specific event, get multiple events or update an event's details.
The true power of these nodes regarding Email, CRM and Calendar remains in combining multiple into one set of instructions.
Examples:
- Find the contact for Jhon for A. Corp and send him an email asking saying that you have scheduled the meeting for next Wednesday at 9AM. Draft an email to remind him of the details and the topic of discussion being the weekly update call and the main company bottlenecks.
- Update the contact details for Jhon since he changed his email and company to B corp and john[at]bcorpfakeemail[dot]com and please update me about my upcoming meetings with him next month.
- Send me a summary for all my meetings today. Draft one email for each different person that I'll meet with today, reminding them about today's meeting
Email nodes
Email nodes
Your AI Agent will be able to search through your email inbox to find specific email content for you. Based on this records you can fetch information quickly and order to draft responses to review later.
Examples:
- hey what were the last 5 emails sent to Jon from X corp?
- Draft an email with these details to Jon sharing I can't make it today and propose a new time for 9AM tomorrow.
CRM nodes
CRM nodes
With these node operations your AI agent will be able to do the following:
- Add a new row with contact data
- Find a row and its details in the table
- Update a value or group of values
Examples:
- Add a new contact data with Rick as first name his cell is +1 XXX XXX XXXX. I will tell you the email later on.
- Can you tell me the details and email for Jon Doe? I want to send him an email reminder.
- Update Rick's email to rick[at]someemail[dot]com from X corp. please.
MCP Client
MCP Client
Paste your MCP client URL from the MCP server trigger node.
Customize your output node to receive the workflow completion notifications (eg. Telegram, Gmail) from your personal assistant
Personal Assistant MCP server
Personal Assistant MCP server
Purpose and structure
This folder contains the Personal Assistant MCP server workflow. Its executable nodes use agent, chatTrigger, gmailTool, googleCalendarTool, googleSheetsTool, lmChatGoogleGemini, mcpClientTool, mcpTrigger, memoryBufferWindow. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When chat message received, MCP Server Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Stickynote/1534_Stickynote_Googlecalendartool_Automation_Triggered.json MIT; preserve source notices.