Manage Google Calendar Events with OpenAI Assistant (Get, Create, Delete)

Sub-agent workflow that uses OpenAI to interpret natural language inputs and manage Google Calendar events: list (Get), create, or delete based on text and session ID.

n8n
Manage Google Calendar Events with OpenAI Assistant (Get, Create, Delete)

This n8n workflow serves as a tools layer for a parent AI agent, enabling intelligent management of Google Calendar events. It receives natural language text and a session ID via the Execute Workflow Trigger, then leverages an OpenAI assistant with short-term memory to parse the intent and select the appropriate tool: Get (list events with time filters), Create (schedule new events), or Delete (remove events by ID). The pipeline flows from trigger to sub-agent decision-making, then to dedicated Google Calendar nodes for execution.

Key benefits include hands-free calendar automation through conversational AI, reducing manual data entry and errors. It's ideal for productivity boosts in team scheduling, personal task management, or integrating into larger agentic systems. Setup is quick (~10 minutes) with OpenAI and Google Calendar OAuth credentials, supporting mostly free operation on n8n CE.

Use cases: Schedule meetings via voice/text like 'Team Sync tomorrow 10-11 AM', list upcoming events with 'Show next week's calendar', or delete with 'Remove Team Sync'. Perfect for developers building AI-powered assistants or automating routine calendar tasks in business workflows.

$19.99
Last updated October 3, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Other workflows

More from Jordi Faber

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.