Skip to content
FlowHubFluxonLab
W
General Automationfree

Google Calendar MCP server for AI Agent with Dynamic Scheduling

by Luciano Gutierrezadapted from n8n official workflow galleryUpdated Aug 2026
Share Post Share
McMCP_CALENDARGCGET_CALENDARGCGET_ALL_CALENDARGCDELETE_CALENDARGCUPDATE_CALENDARGCAVALIABILITY_CALENDARAVALIABILITY_CA…GCCREATE_CALENDAR123456
1/5
STEPS · 6
Starts on a Mcp event

Google Calendar AI Agent with Dynamic Scheduling Version: 1.0.0 n8n Version: 1.88.0+ Author: Koresolucoes License: MIT Description An AI-powered workflow to automate Google Calendar operations using dynamic parameters and MCP (Model Control Plane) integration. Enables event creation, availability checks, updates, and deletions with timezone-aware scheduling [[1]][[2]][[8]]. Key Features: 📅 Full Calendar CRUD: Create, read, update, and delete events in Google Calendar. ⏰ Availability Checks: Verify time slots using AVALIABILITY_CALENDAR node with timezone support (e.g., America/Sao_Paulo). 🤖 AI-Driven Parameters: Use $fromAI() to inject dynamic values like Start_Time, End_Time, and Description [[3]][[4]]. 🔗 MCP Integration: Connects to an MCP server for centralized AI agent control [[5]][[6]]. Use Cases Automated Scheduling: Book appointments based on AI-recommended time slots. Meeting Coordination: Sync calendar events with CRM/task management systems. Resource Management: Check room/equipment availability before event creation. Instructions 1. Import Template Go to n8n > Templates > Import from File and upload this workflow. 2.

Tags

n8nreference-only
CategoryGeneral Automation
Triggermanual
Complexitymedium
Nodes7
AddedApr 23, 2025
W
free

Tiny tiny Rss (aka tt-rss) Feed to Mastodon

Every 10 minutes look at your published news in your Tiny tiny RSS public feed and make a toot on your mastodon. You'll need: Your mastondon URL instance Your mastondon access token Your Tiny Tiny RSS public published feed URL

by dev
free

Using the Merge Node - Merge by Key

This is an example of how you can make Merge by Key work. The “Data 1” and “Data 2” nodes simply provide mock data. You can replace them with your own data sources. Then the “Convert Data” nodes are important. They make sure that the different array items are actually different items in n8n. After that, you have then the merge with the merged data.

by mike
free

Write JSON to Disk (Binary)

The “Write Binary File” expects binary data. The JSON data is, however, JSON ;) There should really be a node that allows moving data around between both of them. For now, it can be done with a Function-Node. At least till a proper one is in place. The first node is example data, wich you can customize or replace. The second node named “Make Binary” is the important one with the custom code which makes the data binary and writes it to the correct location.

by mike