January 22, 2026

Gmail meets Google Calendar for effortless scheduling

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Your inbox fills up with “Can we meet next week?” and suddenly you’re doing the same little dance again. Open Gmail. Switch to Google Calendar. Scan for gaps. Propose a time. Realize you forgot the timezone. Start over.

This Gmail Calendar automation hits founders and freelancers hardest, because scheduling steals the exact hours you should be using to do real work. Client-facing teams feel it too. The outcome is simple: requests turn into calendar actions and ready-to-send email drafts, with a confirmation check so you’re not praying you booked the right slot.

Below you’ll see how this n8n workflow turns natural language (“book a call with Alex tomorrow”) into checked availability, created or updated events, and a clean Gmail message when it’s time to notify someone.

How This Automation Works

See how this solves the problem:

n8n Workflow Template: Gmail meets Google Calendar for effortless scheduling

Click to explore

flowchart LR

    subgraph sg0["Chat Node Flow"]
        direction LR
        n0@{ icon: "mdi:robot", form: "rounded", label: "AI Agent", pos: "b", h: 48 }
        n1@{ icon: "mdi:brain", form: "rounded", label: "Google Gemini Chat Model", pos: "b", h: 48 }
        n2@{ icon: "mdi:memory", form: "rounded", label: "Simple Memory", pos: "b", h: 48 }
        n3@{ icon: "mdi:message-outline", form: "rounded", label: "Send a message in Gmail", pos: "b", h: 48 }
        n4@{ icon: "mdi:message-outline", form: "rounded", label: "Get many messages in Gmail", pos: "b", h: 48 }
        n5@{ icon: "mdi:location-exit", form: "rounded", label: "Get many events in Google Ca..", pos: "b", h: 48 }
        n6@{ icon: "mdi:cog", form: "rounded", label: "Date & Time", pos: "b", h: 48 }
        n7@{ icon: "mdi:location-exit", form: "rounded", label: "Get availability in a calend..", pos: "b", h: 48 }
        n8@{ icon: "mdi:location-exit", form: "rounded", label: "Create an event in Google Ca..", pos: "b", h: 48 }
        n9@{ icon: "mdi:location-exit", form: "rounded", label: "Update an event in Google Ca..", pos: "b", h: 48 }
        n10@{ icon: "mdi:play-circle", form: "rounded", label: "Chat Node", pos: "b", h: 48 }
        n10 --> n0
        n6 -.-> n0
        n2 -.-> n0
        n3 -.-> n0
        n1 -.-> n0
        n4 -.-> n0
        n8 -.-> n0
        n5 -.-> n0
        n9 -.-> n0
        n7 -.-> n0
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n10 trigger
    class n0 ai
    class n1 aiModel
    class n2 ai

The Challenge: Scheduling Requests Turn Into Inbox Debt

Most scheduling problems aren’t “hard.” They’re just constant. One email asks for a meeting. Another asks to move it. Someone replies with a new time, but you’re already on a different thread. You check your calendar, forget what you saw, then check again to be safe. And when you do finally send the reply, it’s easy to miss a detail like meeting duration or timezone, which is how double-bookings and awkward follow-ups happen.

The friction compounds because the work is scattered across tabs, tools, and half-finished drafts.

You lose about 10 minutes per request just context-switching between Gmail and Google Calendar.
Small missing details (timezone, duration, attendees) force another email round-trip you didn’t have time for.
When meetings get changed, updating the event and notifying people becomes two separate chores.
Manual replies vary in tone and clarity, which means more “wait, what are we meeting about?” messages later.

The Fix: An AI Assistant That Actually Schedules (and Checks First)

This workflow gives you a chat-style assistant inside n8n that can read your natural-language request and choose the right action: check your upcoming events, verify availability, create a new meeting, update an existing one, or draft and send an email through Gmail. It uses a short-term memory buffer so your follow-up messages like “make it 30 minutes” or “invite Sam too” still make sense. A Date & Time step converts phrases such as “tomorrow at 3” into proper calendar times. And importantly, it has guardrails: when the request is missing something essential, the assistant asks you instead of guessing. Before it creates an event or emails someone, it confirms what it’s about to do.

The flow begins with an incoming chat message (from Telegram or another chat trigger you connect). From there, the AI agent interprets intent, pulls context from memory, and routes the request to Gmail or Google Calendar. Finally, you get a clear response back, plus a drafted or sent email and a calendar change when appropriate.

What Changes: Before vs. After

What This Eliminates

Impact You’ll See

Checking your calendar manually every time someone suggests a slot.
Copying meeting details from email into a new Google Calendar event.
Writing the same “confirming our meeting” email from scratch.
Forgetting to update the event and notify attendees when plans change.

Most teams get about 3 hours back each week once this is part of the routine.
Fewer double-bookings because availability checks happen before creating the event.
Cleaner, more consistent email replies with clear subjects and summaries.
Less mental load, since the assistant asks for missing details instead of guessing.
A simple chat request becomes an event, an invite, and a confirmation message.

Real-World Impact

Say you handle 10 scheduling requests a week. Manually, you typically spend about 10 minutes per request jumping between Gmail and Google Calendar, plus another 5 minutes writing or rewriting the reply. That’s roughly 2.5 hours weekly. With this workflow, you send a single chat message (about a minute), wait for the availability check and event creation, then approve the drafted reply. You get back around 2 hours most weeks, and the quality is steadier.

Requirements

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Google Calendar to check availability and create/update events
Gmail to retrieve messages and send replies
AI model API key (get it from OpenAI or Google Gemini)

Skill level: Intermediate. You’ll connect OAuth credentials and adjust a few defaults like timezone and your calendar email.

Need help implementing this? Talk to an automation expert (free 15-minute consultation).

The Workflow Flow

A chat message kicks things off. You ask for what you want in plain English, like “Schedule a meeting with [email protected] tomorrow at 3 PM” or “What’s on my calendar next week?”

The assistant interprets intent and keeps context. The AI Agent uses the chat model plus a small memory window (roughly your last few interactions) so follow-ups don’t feel like starting over.

Time gets resolved, then your calendar is checked. Natural phrases are converted into real timestamps, and Google Calendar is queried to catch conflicts before anything is booked.

Gmail and Calendar actions happen with confirmation. If you’re creating or updating an event, the workflow prepares the details and asks you to confirm before it creates data or notifies someone. Email replies are generated with a clear subject and body, then dispatched via Gmail once approved.

You can easily modify the default meeting duration and email tone based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Chat Trigger

Set up the entry point that starts the assistant when a user sends a chat message.

Add the Incoming Chat Trigger node as your workflow trigger.
Keep Options as the default empty object to accept standard chat inputs.
Confirm the execution flow is Incoming Chat Trigger → Intelligent Assistant.

Step 2: Connect Google Services

Prepare Gmail and Google Calendar access for the assistant’s tools. These nodes act as AI tools connected to Intelligent Assistant.

Open Dispatch Gmail Email and ensure the tool is connected to Intelligent Assistant.
Open Retrieve Gmail Messages and ensure the tool is connected to Intelligent Assistant.
Open Fetch Calendar Events, Check Calendar Availability, Create Calendar Event, and Modify Calendar Event and ensure each is connected to Intelligent Assistant.
Update each Google Calendar node’s Calendar to your address: [YOUR_EMAIL].

Credential Required: Connect your Gmail credentials. These Gmail tools are attached to Intelligent Assistant, so ensure the parent has access to Gmail.

Credential Required: Connect your Google Calendar credentials. These Calendar tools are attached to Intelligent Assistant, so ensure the parent has access to Google Calendar.

⚠️ Common Pitfall: If Gmail or Google Calendar credentials are missing, the agent will not be able to call tools even though the nodes are connected.

Step 3: Set Up the Intelligent Assistant

Configure the AI agent, its language model, and memory so it can interpret user requests and call the right tools.

Open Intelligent Assistant and keep the System Message as provided to enforce tool-first behavior and confirmation logic.
Attach Gemini Chat Engine as the language model for Intelligent Assistant.
Attach Compact Memory Buffer as the memory for Intelligent Assistant and set Context Window Length to 10.

Credential Required: Connect your Google Gemini credentials in Gemini Chat Engine.

Tip: The memory window length of 10 keeps recent context tight—raise it if you want longer multi-turn sessions.

Step 4: Configure Output and Action Tools

Define how the assistant sends email, fetches email, resolves dates, and manages calendar events.

In Dispatch Gmail Email, set Send To to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('To', ``, 'string') }}, Subject to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Subject', ``, 'string') }}, and Message to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Message', ``, 'string') }}. Keep Append Attribution enabled.
In Retrieve Gmail Messages, set Operation to getAll, Limit to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Limit', `If the User Specifies a certain time frame, lets make it so that it returns it from that specific time frame and not from other than that time frame. ALSO IF IT ASKS FOR A CERTAIN TIME FRAME GIVE ALL IN THAT TIME FRAME `, 'number') }}, Simplify to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Simplify', `Dont give a very short summary, give a more detailed Summary than a breif summary`, 'boolean') }}, and Filters → Query to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Search', ``, 'string') }}.
In Date Time Resolver, set Timezone to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Timezone', ``, 'string') }} and Output Field Name to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Output_Field_Name', ``, 'string') }}.
In Fetch Calendar Events, set Operation to getAll, Time Min to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('After', ``, 'string') }}, and Time Max to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Before', ``, 'string') }}.
In Check Calendar Availability, set Resource to calendar, Time Min to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Start_Time', ``, 'string') }}, and Time Max to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('End_Time', ``, 'string') }}.
In Create Calendar Event, set Start to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Start', ``, 'string') }} and End to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('End', ``, 'string') }}. Under Additional Fields, set Attendees to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('attendees0_Attendees', `you add attendees here, add there email here`, 'string') }}, Description to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Description', ``, 'string') }}, and keep Conference Solution as hangoutsMeet. Set Use Default Reminders to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Use_Default_Reminders', ``, 'boolean') }}.
In Modify Calendar Event, set Operation to update and Event ID to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Event_ID', ``, 'string') }}.

⚠️ Common Pitfall: Leaving [YOUR_EMAIL] as the calendar value will create or modify events in the wrong account. Replace it with your actual calendar address.

Step 5: Test and Activate Your Workflow

Validate that the assistant can interpret requests, call tools, and return results correctly.

Click Execute Workflow and send a test chat message to Incoming Chat Trigger (e.g., “Check my calendar tomorrow” or “Email Sam about the meeting”).
Confirm that Intelligent Assistant responds with clarification when needed and calls tools like Fetch Calendar Events or Dispatch Gmail Email.
Verify successful output: emails should appear in Gmail, and events should appear in Google Calendar with correct times and attendees.
When satisfied, toggle the workflow to Active to enable production use.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Watch Out For

Google Calendar OAuth credentials can expire or need specific permissions. If things break, check the credential status inside n8n (and your Google Cloud OAuth consent settings) first.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Common Questions

How quickly can I implement this Gmail Calendar automation automation?

About 30 minutes if your Google credentials are ready.

Can non-technical teams implement this scheduling automation?

Yes, but you will need someone comfortable connecting Google OAuth. After that, it’s mostly editing defaults like timezone and email templates.

Is n8n free to use for this Gmail Calendar automation workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in AI model API costs (often just a few dollars a month at typical inbox volume).

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

How do I adapt this Gmail Calendar automation solution to my specific challenges?

You can swap the chat model (Gemini vs. OpenAI) by changing the Chat Model node the agent uses. Most customization happens in the AI Agent system prompt: add your preferred meeting length, your timezone rules, and the exact wording you want in Gmail replies. If you want extra notifications, route the “event created” outcome to Discord or Telegram. For stricter control, keep the confirmation behavior in place and tighten what counts as “enough details” to proceed.

Why is my Google Calendar connection failing in this workflow?

Usually it’s expired or mis-scoped OAuth consent. Reconnect the Google Calendar credential in n8n, confirm the correct Google account is selected, and make sure the Calendar API is enabled in your Google Cloud project. If it only fails sometimes, rate limits can also show up when you run lots of requests quickly.

What’s the capacity of this Gmail Calendar automation solution?

On most setups, it easily handles dozens of requests per day.

Is this Gmail Calendar automation automation better than using Zapier or Make?

For an assistant-style flow, n8n is frankly a better fit because it can branch, hold short-term memory, and run “ask a clarifying question” loops without turning into a fragile maze of zaps. Zapier and Make shine when the automation is linear, like “email received → create event” with fixed rules. Here, the request can be “create,” “update,” “check my week,” or “email this person,” and the workflow needs to decide. Also, self-hosting means you’re not paying per tiny step in the same way. If you want help choosing, Talk to an automation expert and we’ll sanity-check your use case.

Once this is running, scheduling stops being a daily interruption. The workflow takes the repetitive back-and-forth, and you keep control with a simple confirmation before anything goes out.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

{
"id": null,
"meta": {
"instanceId": "4ff571114aba785cb959bc22493b076bdaf42a7b4d5ee9f9ae3863d8916cd832"
},
"name": "Automated Calendar and Email Assistant",
"tags": [],
"nodes": [
{
"id": "flowpast-topbar-8159",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
140,
20
],
"parameters": {
"color": 7,
"width": 1180,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"name": "Intelligent Assistant",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
540,
240
],
"parameters": {
"options": {
"systemMessage": "# n8n AI Agent System Prompt: Personal Assistant\n\nYou are an advanced AI Personal Assistant operating within an n8n workflow. Your primary function is to serve as a cognitive engine that translates user requests into specific, executable tool calls. You are precise, methodical, and you do not act without sufficient information.\n\n---\n\n## Core Operating Principles\n\n1.  **Tool-Centric Operation:** You can only perform actions for which you have been explicitly provided a tool. Before acting, you will review the `Tool Manifest` to confirm you have the required capability. If a user's request does not map to any available tool, you **MUST** clearly state that you cannot perform the action and why. For example: \"I am sorry, but I cannot set a reminder as I do not have a tool for that function.\"\n2.  **Clarification Mandate:** If a user's request is ambiguous or is missing a required parameter for a tool, you **MUST** ask clarifying questions before proceeding. Never guess or assume details like timezones, email recipients, or event durations.\n3.  **Single-Focus Execution:** Handle one primary task at a time. If a user asks to schedule a meeting and check emails, process the meeting first unless the user specifies otherwise.\n4.  **User Confirmation:** Before executing actions that create data or notify others (e.g., creating an event, sending an email), briefly state your plan of action for the user to confirm. Example: \"I will schedule an event titled 'Project Sync' for 3 PM tomorrow and invite '[YOUR_EMAIL]'. Is that correct?\"\n\n---\n\n## Tool Manifest & Usage Protocols\n\nYou have access to the following tools. Adhere strictly to their parameters and usage triggers.\n\n#### Tool: `system_getCurrentTime`\n* **Description:** Retrieves the current date and time.\n* **When to Use:** When the user asks for the current time, date, or uses relative terms like \"today\", \"tomorrow\", \"this week\". This tool is often a dependency for other tools.\n* **Parameters:**\n    * `timezone` (string, required): The IANA timezone identifier (e.g., 'America/New_York', 'Asia/Kolkata').\n* **Protocol:** If the user asks for the time without providing a `timezone`, you **MUST** respond by asking: \"Certainly. In which timezone would you like the time?\" You will output the time in `HH:MM` format as requested.\n\n#### Tool: `googleCalendar_getEvents`\n* **Description:** Fetches a list of events from the user's Google Calendar within a specified date range.\n* **When to Use:** When the user asks \"What's on my schedule?\", \"Am I busy?\", or asks about events for a specific day, week, or month.\n* **Parameters:**\n    * `startDate` (string, ISO 8601 format, required): The start of the time period.\n    * `endDate` (string, ISO 8601 format, required): The end of the time period.\n* **Protocol:** Use `system_getCurrentTime` to establish the date for relative queries. \"This week\" means from today's date for the next 7 days. \"Today\" means from the start of the current day to the end of the current day.\n\n#### Tool: `googleCalendar_createEvent`\n* **Description:** Creates a new event on the user's Google Calendar.\n* **When to Use:** When the user asks to \"schedule\", \"book\", \"create\", or \"add\" an event, meeting, or appointment.\n* **Parameters:**\n    * `summary` (string, required): The title of the event.\n    * `startTime` (string, ISO 8601 format, required): The start time of the event.\n    * `endTime` (string, ISO 8601 format, required): The end time of the event.\n    * `attendees` (array of strings, optional): A list of attendee email addresses.\n* **Protocol:** If the user mentions other people in the scheduling request, automatically include their names/emails in the `attendees` parameter. You must have all required parameters before calling this tool.\n\n#### Tool: `gmail_sendMessage`\n* **Description:** Composes and sends an email via Gmail.\n* **When to Use:** When the user asks to \"email\", \"send a message\", or \"contact\" someone.\n* **Parameters:**\n    * `recipient` (string, required): The primary recipient's email address.\n    * `subject` (string, required): The email subject line.\n    * `body` (string, required): The content of the email.\n* **Protocol:** The `subject` must be detailed and relevant to the body's content. The `body` should be professionally written and clearly articulate the user's message without unnecessary embellishment.\n\n#### Tool: `gmail_getMessages`\n* **Description:** Retrieves a list of emails from the user's Gmail account.\n* **When to Use:** When the user asks to \"check my email\", \"see recent emails\", or \"find an email from someone\".\n* **Parameters:**\n    * `startDate` (string, ISO 8601 format, optional): The start date to filter emails from.\n    * `endDate` (string, ISO 8601 format, optional): The end date to filter emails to.\n    * `from` (string, optional): Filter emails from a specific sender.\n* **Protocol:** Use `system_getCurrentTime` to define date ranges for requests like \"emails from this morning\".\n\n---\n\n## Defined Workflow: \"Schedule a Meeting and Send Invite\"\n\nWhen a user's request involves both scheduling a meeting and notifying the attendees, you **MUST** follow this exact sequence of tool calls:\n\n1.  **Acknowledge and Gather:** Acknowledge the request. Check if you have all the necessary information (`topic/summary`, `attendees`, `proposed time/date`, `duration`). If not, ask for the missing details.\n2.  **Step 1: Check Availability (`googleCalendar_getEvents`)**: Use the `googleCalendar_getEvents` tool to check the user's schedule for the proposed `startTime` and `endTime`.\n3.  **Step 2: Report & Decide**:\n    * **If Conflict Exists:** Report the scheduling conflict to the user, mentioning the existing event. State: \"You already have '[Existing Event Title]' scheduled at that time. Would you like to find a different time?\" Await further instructions.\n    * **If No Conflict:** Proceed to the next step.\n4.  **Step 3: Create Event (`googleCalendar_createEvent`)**: Once the time is confirmed to be free, call this tool with the gathered `summary`, `startTime`, `endTime`, and `attendees`.\n5.  **Step 4: Notify Attendees (`gmail_sendMessage`)**: After the event is successfully created, immediately call this tool to send an invitation email.\n    * `recipient`: The `attendees` from the event.\n    * `subject`: \"Meeting Invitation: [Event Summary]\".\n    * `body`: \"Hello,\\n\\nThis is an invitation to schedule '[Event Summary]' on [Date] at [Time]. Please check your calendar for the official Google Calendar invite.\\n\\nBest regards,\"\n6.  **Step 5: Final Confirmation**: Report to the user that the event has been scheduled and the invitation email has been sent."
}
},
"retryOnFail": true,
"typeVersion": 2.2
},
{
"name": "Gemini Chat Engine",
"type": "@n8n/n8n-nodes-langchain.lmChatGoogleGemini",
"position": [
300,
120
],
"parameters": {
"options": []
},
"notesInFlow": true,
"typeVersion": 1
},
{
"name": "Compact Memory Buffer",
"type": "@n8n/n8n-nodes-langchain.memoryBufferWindow",
"position": [
320,
360
],
"parameters": {
"contextWindowLength": 10
},
"typeVersion": 1.3
},
{
"name": "Dispatch Gmail Email",
"type": "n8n-nodes-base.gmailTool",
"position": [
760,
140
],
"parameters": {
"sendTo": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('To', ``, 'string') }}",
"message": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Message', ``, 'string') }}",
"options": {
"appendAttribution": true
},
"subject": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Subject', ``, 'string') }}"
},
"notesInFlow": true,
"typeVersion": 2.1
},
{
"name": "Retrieve Gmail Messages",
"type": "n8n-nodes-base.gmailTool",
"position": [
860,
320
],
"parameters": {
"limit": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Limit', `If the User Specifies a certain time frame, lets make it so that it returns it from that specific time frame and not from other than that time frame. ALSO IF IT ASKS FOR A CERTAIN TIME FRAME GIVE ALL IN THAT TIME FRAME `, 'number') }}",
"simple": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Simplify', `Dont give a very short summary, give a more detailed Summary than a breif summary`, 'boolean') }}",
"filters": {
"q": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Search', ``, 'string') }}"
},
"options": [],
"operation": "getAll"
},
"notesInFlow": true,
"typeVersion": 2.1
},
{
"name": "Fetch Calendar Events",
"type": "n8n-nodes-base.googleCalendarTool",
"position": [
760,
500
],
"parameters": {
"options": [],
"timeMax": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Before', ``, 'string') }}",
"timeMin": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('After', ``, 'string') }}",
"calendar": {
"__rl": true,
"mode": "list",
"value": "[YOUR_EMAIL]",
"cachedResultName": "[YOUR_EMAIL]"
},
"operation": "getAll"
},
"typeVersion": 1.3
},
{
"name": "Date Time Resolver",
"type": "n8n-nodes-base.dateTimeTool",
"position": [
1020,
220
],
"parameters": {
"options": {
"timezone": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Timezone', ``, 'string') }}"
},
"outputFieldName": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Output_Field_Name', ``, 'string') }}"
},
"typeVersion": 2
},
{
"name": "Check Calendar Availability",
"type": "n8n-nodes-base.googleCalendarTool",
"position": [
1020,
420
],
"parameters": {
"options": [],
"timeMax": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('End_Time', ``, 'string') }}",
"timeMin": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Start_Time', ``, 'string') }}",
"calendar": {
"__rl": true,
"mode": "list",
"value": "[YOUR_EMAIL]",
"cachedResultName": "[YOUR_EMAIL]"
},
"resource": "calendar"
},
"typeVersion": 1.3
},
{
"name": "Create Calendar Event",
"type": "n8n-nodes-base.googleCalendarTool",
"position": [
1200,
300
],
"parameters": {
"end": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('End', ``, 'string') }}",
"start": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Start', ``, 'string') }}",
"calendar": {
"__rl": true,
"mode": "list",
"value": "[YOUR_EMAIL]",
"cachedResultName": "[YOUR_EMAIL]"
},
"additionalFields": {
"attendees": [
"={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('attendees0_Attendees', `you add attendees here, add there email here`, 'string') }}"
],
"description": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Description', ``, 'string') }}",
"conferenceDataUi": {
"conferenceDataValues": {
"conferenceSolution": "hangoutsMeet"
}
}
},
"useDefaultReminders": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Use_Default_Reminders', ``, 'boolean') }}"
},
"notesInFlow": true,
"typeVersion": 1.3
},
{
"name": "Modify Calendar Event",
"type": "n8n-nodes-base.googleCalendarTool",
"position": [
1220,
520
],
"parameters": {
"eventId": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Event_ID', ``, 'string') }}",
"calendar": {
"__rl": true,
"mode": "list",
"value": "[YOUR_EMAIL]",
"cachedResultName": "[YOUR_EMAIL]"
},
"operation": "update",
"updateFields": []
},
"typeVersion": 1.3
},
{
"name": "Incoming Chat Trigger",
"type": "@n8n/n8n-nodes-langchain.chatTrigger",
"position": [
140,
220
],
"parameters": {
"options": []
},
"typeVersion": 1.3
}
],
"active": false,
"pinData": [],
"settings": {
"executionOrder": "v1"
},
"versionId": null,
"connections": {
"Incoming Chat Trigger": {
"main": [
[
{
"node": "Intelligent Assistant",
"type": "main",
"index": 0
}
]
]
},
"Date Time Resolver": {
"ai_tool": [
[
{
"node": "Intelligent Assistant",
"type": "ai_tool",
"index": 0
}
]
]
},
"Compact Memory Buffer": {
"ai_memory": [
[
{
"node": "Intelligent Assistant",
"type": "ai_memory",
"index": 0
}
]
]
},
"Dispatch Gmail Email": {
"ai_tool": [
[
{
"node": "Intelligent Assistant",
"type": "ai_tool",
"index": 0
}
]
]
},
"Gemini Chat Engine": {
"ai_languageModel": [
[
{
"node": "Intelligent Assistant",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"Retrieve Gmail Messages": {
"ai_tool": [
[
{
"node": "Intelligent Assistant",
"type": "ai_tool",
"index": 0
}
]
]
},
"Create Calendar Event": {
"ai_tool": [
[
{
"node": "Intelligent Assistant",
"type": "ai_tool",
"index": 0
}
]
]
},
"Fetch Calendar Events": {
"ai_tool": [
[
{
"node": "Intelligent Assistant",
"type": "ai_tool",
"index": 0
}
]
]
},
"Modify Calendar Event": {
"ai_tool": [
[
{
"node": "Intelligent Assistant",
"type": "ai_tool",
"index": 0
}
]
]
},
"Check Calendar Availability": {
"ai_tool": [
[
{
"node": "Intelligent Assistant",
"type": "ai_tool",
"index": 0
}
]
]
}
}
}