January 22, 2026

Gmail + Google Calendar: scheduling without back and forth

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Scheduling through email sounds simple until it turns into a 14-message thread, a missed detail, and a calendar that’s suddenly wrong. Then you’re digging for “what time did we agree on?” while trying not to double-book yourself.

Marketing leads coordinating partners feel this constantly. A founder running sales calls does too. And an operations manager trying to protect everyone’s calendars will appreciate this Gmail Calendar automation because it turns messy requests into clean bookings.

This workflow uses n8n to add an AI assistant between your messages and your calendar. You’ll see what it automates, what results you can expect, and how to adapt it to the way you already schedule.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Gmail + Google Calendar: scheduling without back and forth

Click to explore

flowchart LR

    subgraph sg0["AI Agent 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:message-outline", form: "rounded", label: "Send a message in Gmail", pos: "b", h: 48 }
        n3@{ icon: "mdi:message-outline", form: "rounded", label: "Get many messages in Gmail", pos: "b", h: 48 }
        n4@{ icon: "mdi:location-exit", form: "rounded", label: "Get many events in Google Ca..", pos: "b", h: 48 }
        n5@{ icon: "mdi:cog", form: "rounded", label: "Date & Time", pos: "b", h: 48 }
        n6@{ icon: "mdi:location-exit", form: "rounded", label: "Get availability in a calend..", pos: "b", h: 48 }
        n7@{ icon: "mdi:location-exit", form: "rounded", label: "Create an event in Google Ca..", pos: "b", h: 48 }
        n8@{ icon: "mdi:location-exit", form: "rounded", label: "Update an event in Google Ca..", pos: "b", h: 48 }
        n9["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Webhook"]
        n10@{ icon: "mdi:swap-vertical", form: "rounded", label: "Prepare Reply", pos: "b", h: 48 }
        n11@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set", pos: "b", h: 48 }
        n12["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Respond to Webhook"]
        n13@{ icon: "mdi:memory", form: "rounded", label: "Simple Memory", pos: "b", h: 48 }
        n11 --> n0
        n9 --> n11
        n0 --> n10
        n5 -.-> n0
        n10 --> n12
        n13 -.-> n0
        n2 -.-> n0
        n1 -.-> n0
        n3 -.-> n0
        n7 -.-> n0
        n4 -.-> n0
        n8 -.-> n0
        n6 -.-> 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 n0 ai
    class n1 aiModel
    class n13 ai
    class n9,n12 api
    classDef customIcon fill:none,stroke:none
    class n9,n12 customIcon

The Problem: Scheduling Turns Into Inbox Chaos

Inbox scheduling breaks down in the tiny gaps. Someone says “tomorrow afternoon,” you reply with two options, they respond with a third time, and now you’re scanning your calendar while trying to remember if “3” meant 3 PM your time or theirs. Multiply that by a few requests a day and it becomes a low-grade stress you carry all week. Worse, the thread usually lacks a single “source of truth,” so your final calendar event (if you even create it) is missing the right title, attendees, or a Meet link.

It adds up fast. Here’s where it breaks down in real life.

You re-read the same email chain multiple times just to confirm a time, which steals focus and creates avoidable mistakes.
Natural language like “next Friday morning” is interpreted differently, so you end up clarifying instead of booking.
Double booking happens when you schedule from memory, then realize your calendar had a conflict you missed.
Even when you do book it, the event details are inconsistent, so people show up without context or the right link.

The Solution: An AI Scheduling Assistant Connected to Gmail + Calendar

This n8n workflow acts like a chat-based assistant that can read what you’re asking, check your Google Calendar, and take the right next action in Gmail. It starts from a simple webhook endpoint (think “chat entry point”), so you can connect it to a chatbot in Telegram, Discord, WhatsApp, or even a lightweight internal tool. When a scheduling request comes in, the AI agent interprets it, converts vague time phrases into real timestamps, checks availability to prevent conflicts, and then creates or updates a calendar event. If key details are missing, it asks questions instead of guessing. And importantly, it confirms actions before doing anything, which keeps your inbox and calendar from getting “creative.”

The workflow begins when you send a message to the webhook. The AI agent then decides if it needs to read emails, send a reply, check your calendar, or book a meeting with a Meet link. Finally, it returns a clean response back to the chat interface so you can approve, clarify, or move on.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

It turns chat or webhook messages into structured scheduling commands.
It converts “tomorrow at 3” style text into exact date and time.
It checks Google Calendar availability before booking anything.
It creates or modifies Calendar events (including Google Meet links) and can send Gmail replies.

Most teams get about 2 hours back each week from fewer scheduling threads.
Fewer “sorry, I missed that” moments because the workflow asks for missing details.
Less double booking since conflicts are checked automatically.
Cleaner, more consistent confirmations, so attendees show up prepared.
A single intake channel for scheduling, even if requests come from different places.

Example: What This Looks Like

Say you handle 10 scheduling requests a week and each one takes about 12 minutes of reading, proposing times, checking conflicts, and sending confirmations. That’s roughly 2 hours of admin work, and it usually arrives in annoying little chunks. With this workflow, you send a single message like “Book a call with John tomorrow at 3 PM for 30 minutes” to your webhook chat, then wait for the confirmation prompt and approve it. Most weeks, you’ll cut that down to a few minutes per request plus whatever time it takes to clarify edge cases.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Gmail for sending, reading, and summarizing emails.
Google Calendar to check availability and create events.
AI provider API key (get it from Gemini, OpenAI, Claude, etc.).

Skill level: Intermediate. You’ll connect OAuth credentials, edit a prompt, and test the webhook with your chat tool.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A message hits your webhook endpoint. You send a scheduling request from a chatbot or frontend to the workflow’s /chat webhook, and n8n maps the incoming fields into a format the agent can reliably understand.

The AI agent interprets intent and fills gaps. The agent uses an LLM (the included setup uses a Gemini chat model, but you can swap it) and a short memory buffer to keep the conversation coherent. If the request is missing duration, attendee, timezone, or even which calendar to use, it asks instead of guessing. Honestly, this is where most “AI scheduling” setups fail, so the guardrails matter.

Calendar and Gmail actions run only after confirmation. When the user’s request is clear, the workflow resolves natural language time into a real timestamp, checks Google Calendar for conflicts, and then creates or modifies the event (optionally generating a Meet link). It can also retrieve Gmail messages or dispatch an email when that’s the right response.

A clean reply is returned to the chat. n8n assembles a human-readable confirmation message and sends it back through the webhook response, which means your chat interface can display a neat “Booked for Tuesday at 3 PM” instead of raw API output.

You can easily modify the assistant’s tone and booking rules to match your business (for example, only scheduling within business hours, or always creating 30-minute meetings). See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Webhook Trigger

Start the workflow with a public webhook endpoint that accepts incoming chat requests.

Add and open Incoming Webhook.
Set Path to chat.
Set HTTP Method to POST.
Set Response Mode to responseNode.
Keep Allowed Origins as * if you need cross-origin calls.

Step 2: Map the Incoming Payload

Normalize incoming text so the AI can always read it from a single field.

Open Map Input Fields and add a string assignment named input.
Set the Value to = {{$json["body"]?.text || $json["text"] || $json["body"]?.input || $json["text"]}}.
Connect Incoming Webhook → Map Input Fields.

Execution Flow: Incoming Webhook → Map Input Fields → Cognitive Agent → Assemble Response → Return Webhook Response.

Step 3: Set Up the AI Agent and Memory

Configure the agent to use the mapped input, memory, and Gemini model.

Open Cognitive Agent and set Text to ={{ $json.input }}.
Connect Gemini Chat Engine to Cognitive Agent as the language model. Credential Required: Connect your googlePalmApi credentials.
Connect Brief Memory Buffer to Cognitive Agent as the memory store. (Credentials for memory are set on the parent node; none are required here.)
Ensure Brief Memory Buffer is set to Context Window Length 10 and Session ID Type customKey.

Credential Note: The AI tools below are connected to Cognitive Agent. Set credentials on those tool nodes (not on the agent): Dispatch Gmail Email, Retrieve Gmail Messages, List Calendar Events, Resolve Date Time, Check Calendar Availability, Generate Calendar Event, Modify Calendar Event.

Step 4: Connect Gmail and Calendar Tools

These tool nodes power email and calendar actions called by the agent.

Open Dispatch Gmail Email and confirm fields are expressions: Send To ={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('To', ``, 'string') }}, Subject ={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Subject', ``, 'string') }}, Message ={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Message', ``, 'string') }}. Credential Required: Connect your gmailOAuth2 credentials.
Open Retrieve Gmail Messages, keep Operation as getAll, and verify Limit and Simplify expressions. Credential Required: Connect your gmailOAuth2 credentials.
Open List Calendar Events and set Time Min to ={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('After', ``, 'string') }} and Time Max to ={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Before', ``, 'string') }}. Select your calendar ID. Credential Required: Connect your googleCalendarOAuth2Api credentials.
Open Check Calendar Availability and set 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') }}. Select your calendar ID. Credential Required: Connect your googleCalendarOAuth2Api credentials.
Open Generate Calendar Event and set Start to ={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Start', ``, 'string') }}, End to ={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('End', ``, 'string') }}, and attendee/description fields as provided. Select your calendar ID. Credential Required: Connect your googleCalendarOAuth2Api credentials.
Open Modify Calendar Event and set Event ID to ={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Event_ID', ``, 'string') }}. Select your calendar ID. Credential Required: Connect your googleCalendarOAuth2Api credentials.

⚠️ Common Pitfall: The calendar nodes use [YOUR_ID] as placeholders. Replace these with your real calendar IDs or the nodes will fail at runtime.

Step 5: Assemble and Return the Webhook Response

Finalize the AI response and send it back to the caller via the webhook.

Open Assemble Response and set an assignment named reply to ={{ $json.output }}.
Ensure Include Other Fields is enabled.
Connect Cognitive Agent → Assemble Response → Return Webhook Response.
In Return Webhook Response, keep Response Code set to 200.

Step 6: Test and Activate Your Workflow

Run a manual test to confirm the webhook and AI chain work end-to-end, then activate for production use.

Click Test Workflow in n8n and send a POST request to the Incoming Webhook URL with a JSON body like {"text":"Check my calendar tomorrow"}.
Verify Map Input Fields creates the input field and Cognitive Agent returns output.
Confirm Assemble Response sets reply to the AI response and Return Webhook Response returns a 200 status with the response text.
When satisfied, toggle the workflow to Active to enable the webhook for live requests.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

Google Calendar OAuth credentials can expire or lack the right scope. If event creation suddenly fails, check the n8n credential status and Google’s consent permissions first.
If you’re using a chat frontend (Telegram/Discord/WhatsApp) plus the webhook, processing times can vary when the LLM is slow. Increase any waits or timeout handling if your Respond to Webhook fires before the agent finishes.
Default AI prompts are bland and sometimes too permissive. Add your booking rules early (timezones, working hours, required attendees), or you will be correcting the assistant’s “helpfulness” constantly.

Frequently Asked Questions

How long does it take to set up this Gmail Calendar automation?

About 45 minutes if your Gmail and Google Calendar logins are ready.

Do I need coding skills to automate Gmail Calendar scheduling?

No. You’ll mainly connect accounts, paste an API key, and test a few example messages.

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 provider usage, which is usually a few cents per request.

Where can I host n8n to run this Gmail Calendar 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.

Can I customize this Gmail Calendar automation workflow for scheduling rules like business hours only?

Yes, and you should. Update the AI Agent’s system prompt (the guardrails) to enforce business hours, required meeting duration, and how to handle timezones. You can also adjust the Simple Memory buffer to keep longer conversations coherent, which helps when someone changes details mid-thread. If you want stricter enforcement, add an If/Switch rule before event creation to block anything outside your allowed windows.

Why is my Gmail connection failing in this workflow?

Usually it’s OAuth scope or an expired credential in n8n. Reconnect the Gmail credential, confirm it has permission to read and send mail, then re-run a test message through the webhook. If you’re processing a lot of messages at once, Gmail rate limits can also trigger intermittent failures, so slowing down requests can help.

How many requests can this Gmail Calendar automation handle?

On n8n Cloud Starter, you can handle a few thousand executions per month, which is plenty for most small teams. If you self-host, there’s no fixed execution cap, so the real limit is your server and how fast your AI provider responds. In practice, scheduling requests are lightweight; the workflow is usually waiting on the LLM or Google APIs, not burning CPU. If you expect spikes, add basic queueing and longer webhook timeouts.

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

It depends on what “better” means for you. If you want a real conversational layer that can ask clarifying questions, remember context briefly, and run conditional logic before booking, n8n is a stronger fit for this workflow. You also get self-hosting, which can be a big deal if you don’t want per-task pricing to creep up as volume grows. Zapier and Make can be quicker for a simple “email arrives → create event” rule, but they get awkward when you add confirmation loops and conflict checks. If you’re unsure, Talk to an automation expert and describe your scheduling volume and channels.

Once this is running, scheduling stops being a daily distraction. The workflow handles the repetitive back-and-forth so you can stay in your actual work.

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,
"versionId": null,
"meta": {
"instanceId": "adc56c066ab16ddd197619d99b24ab44177ec9be8ed64fa0669b70de051983d9",
"templateId": null,
"templateCredsSetupCompleted": null
},
"name": "Webhook-Based AI Assistant Flow",
"tags": [],
"nodes": [
{
"id": "flowpast-topbar-8234",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
20
],
"parameters": {
"color": 7,
"width": 1080,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"name": "Cognitive Agent",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
450,
130
],
"parameters": {
"text": "={{ $json.input }}",
"options": {
"systemMessage": "\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 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 'user@example.com'. 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\n* **Description:** Retrieves the current date and time. This is often a dependency for other tools.\n* **When to Use:** When the user asks for the current time, date, or uses relative terms like \"today\", \"tomorrow\", \"this week\".\n* **Parameters:**\n    * `timezone` (string, optional): The IANA timezone identifier (e.g., 'America/New_York', 'Asia/Kolkata').\n* **Protocol:** If the `timezone` is not provided, you **MUST** ask the user for their location to infer it. For example: \"Certainly. To give you the correct time, could you let me know where you are located?\" If the user provides a location (e.g., \"India\", \"New York\"), use the corresponding IANA timezone. You will output the time in `HH:MM` format as requested.\n\n#### Tool: `googleCalendar_getEvents`\n\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.\n    * **\"Today\"** means the last 24 hours from the current time.\n    * **\"This week\"** means from today's date for the next 7 days.\n    * **\"This month\"** means from today's date for the next 30 days.\n\n#### Tool: `googleCalendar_createEvent`\n\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\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\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. For example, \"retrieve emails sent today\" means fetching emails from the last 24 hours.\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."
},
"promptType": "define"
},
"retryOnFail": true,
"typeVersion": 2.2
},
{
"name": "Gemini Chat Engine",
"type": "@n8n/n8n-nodes-langchain.lmChatGoogleGemini",
"position": [
730,
350
],
"parameters": {
"options": []
},
"credentials": {
"googlePalmApi": {
"id": "credential-id",
"name": ""
}
},
"notesInFlow": true,
"typeVersion": 1
},
{
"name": "Dispatch Gmail Email",
"type": "n8n-nodes-base.gmailTool",
"position": [
360,
360
],
"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') }}"
},
"credentials": {
"gmailOAuth2": {
"id": "credential-id",
"name": ""
}
},
"notesInFlow": true,
"typeVersion": 2.1
},
{
"name": "Retrieve Gmail Messages",
"type": "n8n-nodes-base.gmailTool",
"position": [
150,
340
],
"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"
},
"credentials": {
"gmailOAuth2": {
"id": "credential-id",
"name": ""
}
},
"notesInFlow": true,
"typeVersion": 2.1
},
{
"name": "List Calendar Events",
"type": "n8n-nodes-base.googleCalendarTool",
"position": [
360,
520
],
"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_ID]",
"cachedResultName": "[YOUR_ID]"
},
"operation": "getAll"
},
"credentials": {
"googleCalendarOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.3
},
{
"name": "Resolve Date Time",
"type": "n8n-nodes-base.dateTimeTool",
"position": [
520,
500
],
"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": [
690,
540
],
"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_ID]",
"cachedResultName": "[YOUR_ID]"
},
"resource": "calendar"
},
"credentials": {
"googleCalendarOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.3
},
{
"name": "Generate Calendar Event",
"type": "n8n-nodes-base.googleCalendarTool",
"position": [
860,
500
],
"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_ID]",
"cachedResultName": "[YOUR_ID]"
},
"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') }}"
},
"credentials": {
"googleCalendarOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"notesInFlow": true,
"typeVersion": 1.3
},
{
"name": "Modify Calendar Event",
"type": "n8n-nodes-base.googleCalendarTool",
"position": [
980,
340
],
"parameters": {
"eventId": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Event_ID', ``, 'string') }}",
"calendar": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultName": "[YOUR_ID]"
},
"operation": "update",
"updateFields": []
},
"credentials": {
"googleCalendarOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.3
},
{
"name": "Incoming Webhook",
"type": "n8n-nodes-base.webhook",
"position": [
900,
120
],
"parameters": {
"path": "chat",
"options": {
"allowedOrigins": "*"
},
"httpMethod": "POST",
"responseMode": "responseNode"
},
"typeVersion": 2.1
},
{
"name": "Assemble Response",
"type": "n8n-nodes-base.set",
"position": [
230,
190
],
"parameters": {
"options": [],
"assignments": {
"assignments": [
{
"name": "reply",
"type": "string",
"value": "={{ $json.output }}"
}
]
},
"includeOtherFields": true
},
"typeVersion": 3.4
},
{
"name": "Map Input Fields",
"type": "n8n-nodes-base.set",
"position": [
680,
170
],
"parameters": {
"options": [],
"assignments": {
"assignments": [
{
"name": "input",
"type": "string",
"value": "= {{$json[\"body\"]?.text || $json[\"text\"] || $json[\"body\"]?.input || $json[\"text\"]}}"
}
]
}
},
"typeVersion": 3.4
},
{
"name": "Return Webhook Response",
"type": "n8n-nodes-base.respondToWebhook",
"position": [
0,
140
],
"parameters": {
"options": {
"responseCode": 200
}
},
"typeVersion": 1.4
},
{
"name": "Brief Memory Buffer",
"type": "@n8n/n8n-nodes-langchain.memoryBufferWindow",
"position": [
520,
320
],
"parameters": {
"sessionKey": "=\"parameters\": {\n  \"memoryKey\": \"history\",\n  \"inputKey\": \"input\",\n  \"outputKey\": \"reply\"\n}\n",
"sessionIdType": "customKey",
"contextWindowLength": 10
},
"typeVersion": 1.3
}
],
"active": true,
"pinData": [],
"settings": {
"executionOrder": "v1"
},
"connections": {
"Map Input Fields": {
"main": [
[
{
"node": "Cognitive Agent",
"type": "main",
"index": 0
}
]
]
},
"Incoming Webhook": {
"main": [
[
{
"node": "Map Input Fields",
"type": "main",
"index": 0
}
]
]
},
"Cognitive Agent": {
"main": [
[
{
"node": "Assemble Response",
"type": "main",
"index": 0
}
]
]
},
"Resolve Date Time": {
"ai_tool": [
[
{
"node": "Cognitive Agent",
"type": "ai_tool",
"index": 0
}
]
]
},
"Assemble Response": {
"main": [
[
{
"node": "Return Webhook Response",
"type": "main",
"index": 0
}
]
]
},
"Brief Memory Buffer": {
"ai_memory": [
[
{
"node": "Cognitive Agent",
"type": "ai_memory",
"index": 0
}
]
]
},
"Dispatch Gmail Email": {
"ai_tool": [
[
{
"node": "Cognitive Agent",
"type": "ai_tool",
"index": 0
}
]
]
},
"Gemini Chat Engine": {
"ai_languageModel": [
[
{
"node": "Cognitive Agent",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"Retrieve Gmail Messages": {
"ai_tool": [
[
{
"node": "Cognitive Agent",
"type": "ai_tool",
"index": 0
}
]
]
},
"Generate Calendar Event": {
"ai_tool": [
[
{
"node": "Cognitive Agent",
"type": "ai_tool",
"index": 0
}
]
]
},
"List Calendar Events": {
"ai_tool": [
[
{
"node": "Cognitive Agent",
"type": "ai_tool",
"index": 0
}
]
]
},
"Modify Calendar Event": {
"ai_tool": [
[
{
"node": "Cognitive Agent",
"type": "ai_tool",
"index": 0
}
]
]
},
"Check Calendar Availability": {
"ai_tool": [
[
{
"node": "Cognitive Agent",
"type": "ai_tool",
"index": 0
}
]
]
}
}
}