Google Calendar Manager | MCP

Google Calendar Manager Sub-Workflow Overview This workflow functions as a comprehensive, reusable "sub-workflow" for managing events on a specific Google Calendar. It is not designed to run on its own but is called by other, parent workflows to perform specific actions. It effectively acts as a centralized controller or API for all calendar-related tasks, handling the creation, retrieval, updating, and deletion (CRUD) of events, as well as checking for time-slot availability. By centralizing these functions, this workflow promotes modularity and reusability, eliminating the need to rebuild calendar logic in multiple places. It also includes built-in validation, such as checking for scheduling conflicts before creating a new event, thereby preventing double bookings and ensuring data integrity. Technologies Used - n8n: The automation platform coordinating the logic. - Google Calendar: The target application being automated for event management. What It Automates This workflow automates the core functions of calendar management. Any other automation that needs to schedule, modify, or query calendar events can simply call this workflow with the appropriate command. This is ideal for systems like: - Automated booking systems. - Task schedulers that sync with a calendar. - CRM workflows that need to create meeting events. - Reporting workflows that need to analyze calendar data. Node-by-Node Analysis The workflow's logic is controlled by an initial command, which directs the data down one of several paths to perform a specific action. H3: Trigger & Input Mapping - When Executed by Another Workflow (Trigger): This node serves as the entry point. It's configured to listen for calls from other n8n workflows, expecting several key pieces of information: operation (e.g., "createEvent"), startDate, endDate, eventId, and timeZone. - map\_data (Set Node): This node immediately processes the incoming data. Its primary function is to standardize the startDate and endDate by applying the correct timeZone. This is a critical step that prevents time-related errors and ensures all calendar operations are executed in the intended timezone.