January 22, 2026

WhatsApp + Google Calendar: book meetings by chat

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Your calendar and inbox don’t fall apart because you can’t schedule. They fall apart because scheduling is scattered across chats, email threads, and “quick” calendar checks that never stay quick. That’s why WhatsApp calendar automation is such a relief when your day is already packed.

Client-facing teams feel it first. Then it hits agency owners and ops leads who end up playing human router between meetings, follow-ups, and reschedules. This workflow turns WhatsApp into the place where meetings get booked, availability gets checked, and Gmail follow-ups get sent, without the copy-paste.

You’ll see what it does, how it works, what you need to run it, and the small setup details that usually trip people up.

How This Automation Works

See how this solves the problem:

n8n Workflow Template: WhatsApp + Google Calendar: book meetings by chat

Click to explore

flowchart LR

    subgraph sg0["WhatsApp 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["<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/whatsapp.svg' width='40' height='40' /></div><br/>WhatsApp Trigger"]
        n11@{ icon: "mdi:swap-vertical", form: "rounded", label: "Extract User Context", 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/whatsapp.svg' width='40' height='40' /></div><br/>Send WhatsApp Response"]
        n0 --> n12
        n6 -.-> n0
        n2 -.-> n0
        n10 --> n11
        n11 --> 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
    classDef customIcon fill:none,stroke:none
    class n10,n12 customIcon

The Challenge: Scheduling Without Losing the Thread

Booking a meeting sounds simple until it’s happening inside a WhatsApp chat while you’re also juggling Gmail threads and a calendar that changes hourly. You ask a few questions, someone replies late, the time you suggested is gone, and now you’re back to “How about Thursday?” Meanwhile, you still have to create the event, add a Meet link, and send a confirmation message that actually matches what got booked. It’s not hard work. It’s brittle work, which means small mistakes become real headaches.

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

You check availability in Google Calendar, then return to WhatsApp and realize the conversation already moved on.
Reschedules turn into mini projects because the event update, the Meet link, and the follow-up email don’t stay in sync.
Natural language like “next Monday afternoon” creates errors when someone has to interpret time zones and formats manually.
Inbox follow-ups get forgotten because the “I’ll email you the details” moment gets buried in chat.

The Fix: An AI Assistant That Schedules From WhatsApp

This workflow listens for incoming WhatsApp messages, understands what the person is asking, and then takes the right action in Google Calendar or Gmail. If someone says, “Book 30 minutes tomorrow at 5,” the assistant converts that into a proper date/time, checks your calendar availability, and creates the meeting when the slot works. If they ask what’s on your calendar, it retrieves events and replies in plain English. If they say “Email Alex confirming the meeting,” it can send that email through Gmail without you leaving the chat. Context is remembered per phone number, so you can say “make it 30 minutes instead” and it knows what “it” refers to.

The workflow starts with a WhatsApp trigger, then an AI agent (using OpenAI GPT or Google Gemini) chooses the right tool for the request. Google Calendar nodes handle listing, creating, updating, and availability checks. Gmail nodes send messages or summarize recent threads. Finally, the workflow replies via WhatsApp with a clear confirmation.

What Changes: Before vs. After

What This Eliminates

Impact You’ll See

Manually switching between WhatsApp, Google Calendar, and Gmail for a single request.
Guessing what “next Monday at 3” means and reformatting it into ISO time by hand.
Creating events first, then separately sending confirmation messages and hoping they match.
Losing context when a chat thread goes quiet and restarts later.

Most teams get about 5 hours back each week once this is used daily.
Fewer booking mistakes because availability is checked before anything is created.
Faster responses in chat, which means fewer “just checking in” messages.
Cleaner follow-ups since Gmail can send the recap right after scheduling.
More consistent client experience because confirmations follow the same structure every time.

Real-World Impact

Say you schedule 10 meetings a week from WhatsApp. Manually, each one often takes about 10 minutes: check Google Calendar, create the event, add conferencing, return to chat, then send an email recap. That’s roughly 100 minutes weekly, plus the rework when something is booked wrong. With this workflow, you message once in WhatsApp and wait for the confirmation; figure about 1 minute of your time per booking, so you claw back around 1.5 hours a week and cut the “oops, wrong time” moments dramatically.

Requirements

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
WhatsApp Business Cloud to receive and reply to messages.
Google Calendar to check availability and create events.
Gmail to send confirmations and read/summarize threads.
OpenAI API key or Google Gemini API key (get it from your OpenAI or Google AI Studio account).

Skill level: Intermediate. You won’t code, but you will connect OAuth credentials and configure WhatsApp webhooks.

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

The Workflow Flow

A WhatsApp message kicks it off. When someone sends a message to your WhatsApp Business number, the workflow captures it instantly, along with the sender’s phone number.

Context gets cleaned up and remembered. A short parsing step organizes the message and basic metadata, then Simple Memory stores conversational context per user so follow-up messages still make sense.

The AI agent chooses the right “tool.” Using OpenAI GPT or Google Gemini, the assistant decides if this is a scheduling request, an availability check, an “update the meeting” request, or an email task. Natural language time gets converted into a proper date/time so Google Calendar actions don’t misfire.

Google Calendar and Gmail do the work, then WhatsApp confirms it. Calendar nodes list events, check availability, create meetings (with Google Meet links), or modify existing ones. Gmail nodes can send a recap email or summarize recent threads. The final message goes back to the same WhatsApp chat so the user sees a clear “booked” or “here are your free times” response.

You can easily modify the assistant’s “personality” to match your brand voice based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the WhatsApp Trigger

Set up the WhatsApp webhook trigger so the workflow can receive incoming messages and pass them into the automation.

Add and open WhatsApp Incoming Trigger.
Keep Updates set to messages.
Copy the webhook URL generated by WhatsApp Incoming Trigger and register it in your WhatsApp Business settings.

If you don’t see incoming data during testing, verify your WhatsApp webhook setup and confirm the correct phone number is linked to the Business API.

Step 2: Parse Incoming Message Context

Extract the message text and sender information so the AI agent can respond and send replies to the correct number.

Open Parse WhatsApp Context and set Include Other Fields to true.
Confirm the assignments map fields correctly:
Set chatInput to {{ $json.entry[0].changes[0].value.messages[0].text.body }}.
Set sessionId to {{ $json.entry[0].changes[0].value.messages[0].from }}.
Set userPhone to {{ $json.entry[0].changes[0].value.messages[0].from }}.
Connect WhatsApp Incoming Trigger → Parse WhatsApp Context.

⚠️ Common Pitfall: If your WhatsApp payload structure differs, these expressions will break. Validate the incoming JSON in a test run before going live.

Step 3: Set Up the AI Assistant and Memory

Configure the AI agent to interpret user requests, reference memory, and call connected tools for email and calendar actions.

Open Intelligent Assistant and review the System Message to match your operating rules and tool protocol.
Connect Parse WhatsApp Context → Intelligent Assistant to pass the parsed message into the agent.
Open Conversation Memory and set Context Window Length to 10.
Ensure Conversation Memory is connected as an ai_memory tool to Intelligent Assistant.
Open Gemini Chat Engine and connect it as the ai_languageModel for Intelligent Assistant.
Credential Required: Connect your googlePalmApi credentials in Gemini Chat Engine.

AI tool nodes like Conversation Memory and Time Conversion do not store credentials themselves. Add credentials to the parent node or the connected model node (e.g., Gemini Chat Engine).

Step 4: Configure AI Tools for Gmail, Calendar, and Time

These tool nodes provide the AI agent with the ability to check emails, send messages, and manage calendar events.

Open Time Conversion and set Output Field Name to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Output_Field_Name', ``, 'string') }}, with Timezone set to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Timezone', ``, 'string') }}.
Open Dispatch Gmail Email and confirm:
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 for Dispatch Gmail Email.
Open Retrieve Gmail Threads and keep Operation set to getAll, with Limit and Simple using the provided AI expressions.
Credential Required: Connect your gmailOAuth2 credentials for Retrieve Gmail Threads.
Open Fetch Calendar Events and 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') }}.
Credential Required: Connect your googleCalendarOAuth2Api credentials for Fetch Calendar Events, Create Calendar Meeting, Modify Calendar Entry, and Check Calendar Availability.
Open Create Calendar Meeting and set Start to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Start', ``, 'string') }} and End to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('End', ``, 'string') }}, and confirm the attendee field uses {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('attendees0_Attendees', `you add attendees here, add there email here`, 'string') }}.
Open Modify Calendar Entry and keep Operation set to update with Event ID set to {{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Event_ID', ``, 'string') }}.
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') }}.

⚠️ Common Pitfall: The Gmail and Calendar nodes are AI tools. Ensure they are connected to Intelligent Assistant as ai_tool nodes and that credentials are added to each tool node (not to the agent itself).

Step 5: Configure the WhatsApp Reply Action

Return the AI’s final response to the user via WhatsApp.

Open Send WhatsApp Reply and set Operation to send.
Set Text Body to {{ $json.output }} so the AI response is returned to the user.
Set Recipient Phone Number to {{ $('Parse WhatsApp Context').item.json.userPhone }}.
Connect Intelligent Assistant → Send WhatsApp Reply.

Execution flow is linear: WhatsApp Incoming Trigger → Parse WhatsApp Context → Intelligent Assistant → Send WhatsApp Reply.

Step 6: Test and Activate Your Workflow

Run a complete test to verify WhatsApp input, AI processing, and outgoing messages, then activate the workflow.

Click Execute Workflow and send a test message to your WhatsApp Business number.
Verify that Parse WhatsApp Context produces chatInput and userPhone, and that Intelligent Assistant returns an output.
Confirm that Send WhatsApp Reply delivers the response back to the sender.
If testing Gmail or Calendar actions, verify the email sends or calendar updates in the target accounts.
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

WhatsApp Business Cloud configuration is picky, and webhook URLs must match exactly. If replies stop, check your Meta Developer webhook setup and token validity 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.
Google Calendar and Gmail OAuth scopes matter. If the assistant can “read” but can’t “create,” review the connected Google credentials inside n8n and re-auth with the correct permissions.

Common Questions

How quickly can I implement this WhatsApp calendar automation?

About 60–90 minutes once your WhatsApp and Google credentials are ready.

Can non-technical teams implement this WhatsApp calendar automation?

Yes, but you’ll want someone comfortable with connecting OAuth and copying webhook URLs. No coding is required inside n8n.

Is n8n free to use for this WhatsApp 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 OpenAI or Gemini API usage, which is usually small per message unless you’re summarizing lots of email text.

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 WhatsApp calendar automation solution to my specific challenges?

Start with the AI Agent instructions and the memory settings, because that’s what controls how “human” the chat feels. You can swap the Gemini Chat Engine for an OpenAI Chat Model (or the other way around) without changing the calendar and Gmail actions. Common tweaks include setting rules for working hours, adding a default meeting length, and changing the confirmation message format so it matches your brand tone.

Why is my WhatsApp connection failing in this workflow?

Most of the time it’s a webhook or token issue in Meta Developer settings, not n8n. Confirm the webhook URL, verify token, and that the WhatsApp app is subscribed to message events. If incoming messages arrive but replies fail, check the WhatsApp Business Cloud credentials inside n8n and make sure your phone number is approved for the environment you’re using. Rate limits can also show up when you test too aggressively in a short window, honestly.

What’s the capacity of this WhatsApp calendar automation solution?

On most n8n Cloud plans, the limit is based on monthly executions, so capacity depends on how many chat messages you process. If you self-host, there’s no execution cap; your server resources become the limiter.

Is this WhatsApp calendar automation better than using Zapier or Make?

Often, yes, because this isn’t a simple “message in, event out” zap. You need memory, branching logic, and tool selection based on intent, and those flows get expensive or awkward in Zapier/Make. n8n also gives you a clean path to self-host for unlimited runs, which matters when WhatsApp becomes your default interface. Zapier or Make can still win for very basic two-step automations and quick prototypes. Talk to an automation expert if you want a sanity check before you commit.

Once this is running, your chat becomes the front door and your calendar stays accurate. The workflow handles the busywork so you can get back to real 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": "",
"meta": {
"instanceId": "8dd9f6b2166720f22a6680dcaf61908065543fc7e858049cbb6549e2c58b972e",
"templateId": "",
"templateCredsSetupCompleted": null
},
"name": "Automated Messaging and Calendar Assistant",
"tags": [],
"nodes": [
{
"id": "flowpast-topbar-9931",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
20
],
"parameters": {
"color": 7,
"width": 1170,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "7deeccc8-b302-4137-8191-87bfdc0cd9ac",
"name": "Conversation Memory",
"type": "@n8n/n8n-nodes-langchain.memoryBufferWindow",
"position": [
650,
120
],
"parameters": {
"contextWindowLength": 10
},
"typeVersion": 1.3
},
{
"id": "62b57ef0-5aa4-4ec9-8871-09b02e56ac31",
"name": "Time Conversion",
"type": "n8n-nodes-base.dateTimeTool",
"position": [
400,
130
],
"parameters": {
"options": {
"timezone": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Timezone', ``, 'string') }}"
},
"outputFieldName": "={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Output_Field_Name', ``, 'string') }}"
},
"typeVersion": 2
},
{
"id": "6f78ccad-6f12-4422-9107-abb2b954a0ae",
"name": "Gemini Chat Engine",
"type": "@n8n/n8n-nodes-langchain.lmChatGoogleGemini",
"position": [
820,
190
],
"parameters": {
"options": []
},
"credentials": {
"googlePalmApi": {
"id": "credential-id",
"name": ""
}
},
"notesInFlow": true,
"typeVersion": 1
},
{
"id": "0a7a5f2e-46a8-4690-a253-5c83c907f44a",
"name": "WhatsApp Incoming Trigger",
"type": "n8n-nodes-base.whatsAppTrigger",
"position": [
1060,
160
],
"webhookId": "75b76607-d6ae-4d34-9bf7-51ec3ca377d1",
"parameters": {
"options": [],
"updates": [
"messages"
]
},
"typeVersion": 1
},
{
"id": "546be615-c664-4b72-9bd1-3f4646dea698",
"name": "Parse WhatsApp Context",
"type": "n8n-nodes-base.set",
"position": [
790,
230
],
"parameters": {
"options": [],
"assignments": {
"assignments": [
{
"id": "id-1",
"name": "chatInput",
"type": "string",
"value": "={{ $json.entry[0].changes[0].value.messages[0].text.body }}"
},
{
"id": "id-2",
"name": "sessionId",
"type": "string",
"value": "={{ $json.entry[0].changes[0].value.messages[0].from }}"
},
{
"id": "id-3",
"name": "userPhone",
"type": "string",
"value": "={{ $json.entry[0].changes[0].value.messages[0].from }}"
}
]
},
"includeOtherFields": true
},
"typeVersion": 3.4
},
{
"id": "40efd41a-fe5b-49e3-b055-043df556d376",
"name": "Intelligent Assistant",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
520,
270
],
"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?\"\n5.  **User Personalization:** You have access to the user's phone number through the sessionId field. Use this information to personalize your interactions when appropriate. The sessionId contains the user's phone number which can be used to identify and personalize responses for returning users.\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
},
{
"id": "e5bcb4c2-f6c3-4076-8449-e59a399efb8e",
"name": "Send WhatsApp Reply",
"type": "n8n-nodes-base.whatsApp",
"position": [
260,
320
],
"webhookId": "ce5f4fde-c2eb-4a64-a25b-4e1ec1a5f928",
"parameters": {
"textBody": "={{ $json.output }}",
"operation": "send",
"additionalFields": [],
"recipientPhoneNumber": "={{ $('Parse WhatsApp Context').item.json.userPhone }}"
},
"typeVersion": 1.1
},
{
"id": "5a1fcb2e-eaa1-483b-bf1c-c79e8fb87021",
"name": "Dispatch Gmail Email",
"type": "n8n-nodes-base.gmailTool",
"position": [
900,
420
],
"webhookId": "d133d04b-d6c0-4ddd-86b7-c983c8ea0a33",
"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
},
{
"id": "ae6efff9-33f3-4b0f-847e-5175ee56ba92",
"name": "Retrieve Gmail Threads",
"type": "n8n-nodes-base.gmailTool",
"position": [
1070,
510
],
"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,
"notes": "",
"typeVersion": 2.1
},
{
"id": "c492bf76-9592-40b1-96a7-24725deb7ef2",
"name": "Fetch Calendar Events",
"type": "n8n-nodes-base.googleCalendarTool",
"position": [
720,
590
],
"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"
},
"credentials": {
"googleCalendarOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.3
},
{
"id": "ce2011b1-f2aa-4dba-a647-96879495f60d",
"name": "Create Calendar Meeting",
"type": "n8n-nodes-base.googleCalendarTool",
"position": [
470,
620
],
"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') }}"
},
"credentials": {
"googleCalendarOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"notesInFlow": true,
"typeVersion": 1.3
},
{
"id": "c374dc52-33bd-4b09-928e-1ef3f7ffb9f2",
"name": "Modify Calendar Entry",
"type": "n8n-nodes-base.googleCalendarTool",
"position": [
230,
580
],
"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": []
},
"credentials": {
"googleCalendarOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.3
},
{
"id": "7b448ce5-73fc-4f08-bc48-677be74d9c53",
"name": "Check Calendar Availability",
"type": "n8n-nodes-base.googleCalendarTool",
"position": [
0,
530
],
"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"
},
"credentials": {
"googleCalendarOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.3
}
],
"active": false,
"pinData": [],
"settings": [],
"versionId": "",
"connections": {
"Intelligent Assistant": {
"main": [
[
{
"node": "Send WhatsApp Reply",
"type": "main",
"index": 0
}
]
]
},
"Time Conversion": {
"ai_tool": [
[
{
"node": "Intelligent Assistant",
"type": "ai_tool",
"index": 0
}
]
]
},
"Conversation Memory": {
"ai_memory": [
[
{
"node": "Intelligent Assistant",
"type": "ai_memory",
"index": 0
}
]
]
},
"WhatsApp Incoming Trigger": {
"main": [
[
{
"node": "Parse WhatsApp Context",
"type": "main",
"index": 0
}
]
]
},
"Parse WhatsApp Context": {
"main": [
[
{
"node": "Intelligent Assistant",
"type": "main",
"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 Threads": {
"ai_tool": [
[
{
"node": "Intelligent Assistant",
"type": "ai_tool",
"index": 0
}
]
]
},
"Create Calendar Meeting": {
"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 Entry": {
"ai_tool": [
[
{
"node": "Intelligent Assistant",
"type": "ai_tool",
"index": 0
}
]
]
},
"Check Calendar Availability": {
"ai_tool": [
[
{
"node": "Intelligent Assistant",
"type": "ai_tool",
"index": 0
}
]
]
}
}
}