January 22, 2026

Gmail + Google Calendar, faster replies and meetings

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Your inbox is not the problem. The constant context switching is. You read an email, decide what it “is,” draft a reply, mark it done, then realize it’s actually a meeting request and now you’re hunting for calendar slots.

This Gmail Calendar automation hits client-facing teams hardest, but agency owners and ops leads feel it too. You will reply faster, label and log consistently, and stop losing meetings in the back-and-forth.

Below is the exact workflow: Gmail triggers it, Gemini classifies intent, n8n sends the right reply, and Google Calendar invites get created automatically when a message looks like “let’s meet.”

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: Gmail + Google Calendar, faster replies and meetings

Click to explore

flowchart LR

    subgraph sg0["Gmail Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "Gmail Trigger", pos: "b", h: 48 }
        n1@{ icon: "mdi:robot", form: "rounded", label: "Text Classifier", pos: "b", h: 48 }
        n2@{ icon: "mdi:brain", form: "rounded", label: "Google Gemini Chat Model", pos: "b", h: 48 }
        n3@{ icon: "mdi:message-outline", form: "rounded", label: "Youtube Video Inquiry", pos: "b", h: 48 }
        n4@{ icon: "mdi:message-outline", form: "rounded", label: "Send Email", pos: "b", h: 48 }
        n5@{ icon: "mdi:message-outline", form: "rounded", label: "Mark as Read", pos: "b", h: 48 }
        n6@{ icon: "mdi:message-outline", form: "rounded", label: "Apply Label", pos: "b", h: 48 }
        n7@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Emails from Existing Contracts", pos: "b", h: 48 }
        n8@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Reply", pos: "b", h: 48 }
        n9@{ icon: "mdi:message-outline", form: "rounded", label: "QuestionsReply", pos: "b", h: 48 }
        n10@{ icon: "mdi:location-exit", form: "rounded", label: "Google Calendar", pos: "b", h: 48 }
        n11@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items", pos: "b", h: 48 }
        n12@{ icon: "mdi:location-exit", form: "rounded", label: "Google Calendar1", pos: "b", h: 48 }
        n13["<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/code.svg' width='40' height='40' /></div><br/>Code"]
        n13 --> n9
        n8 --> n1
        n4 --> n5
        n5 --> n6
        n0 --> n7
        n9 --> n5
        n10 --> n11
        n11 --> n13
        n11 --> n12
        n1 --> n10
        n1 --> n3
        n1 --> n4
        n12 --> n11
        n3 --> n5
        n2 -.-> n1
        n7 --> n8
    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 trigger
    class n1 ai
    class n2 aiModel
    class n7,n8 decision
    class n13 code
    classDef customIcon fill:none,stroke:none
    class n13 customIcon

Why This Matters: Inbox triage turns into a daily bottleneck

Most inbox stress is decision fatigue, not volume. You open a message and do a quick mental sort: “Is this a question, a project update, or feedback?” Then you rewrite the same types of replies all day, trying to sound consistent while rushing. Meanwhile, the easy operational hygiene slips. Messages don’t get labeled, threads aren’t logged, and “I’ll schedule that” turns into a follow-up two days later because you never created the invite. It’s messy, and it quietly slows revenue down.

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

Meeting requests sit in the inbox because replying and scheduling are two separate tasks you have to remember.
Quick replies become inconsistent, which leads to more clarification emails and longer threads.
Labels and “mark as read” hygiene gets skipped when you’re busy, so your inbox stops being trustworthy.
Internal emails trigger accidental replies or wasted time, especially when multiple teammates monitor the same address.

What You’ll Build: AI-sorted Gmail replies with auto calendar invites

This workflow turns every new Gmail message into a clean, predictable process. It starts the moment an email hits your inbox. n8n checks whether the sender looks internal, then runs an “eligibility” filter so you only auto-reply when it makes sense. Next, Gemini (via an AI agent and chat model) classifies the email into intent types like inquiry, project update, or feedback. Based on that intent, it sends a context-specific email reply, then immediately does the housekeeping: mark the thread as read and apply labels so your inbox stays organized. If the email looks like a meeting request, the workflow also looks up calendar slots, loops through candidates in batches, and creates or updates a Google Calendar invite with a prepared payload.

The workflow begins with Gmail, makes a quick decision with Gemini, and routes the email down the right reply path. When scheduling is involved, Google Calendar becomes the “source of truth,” so a meeting goes from request to invite without you juggling tabs.

What You’re Building

What Gets Automated

What You’ll Achieve

New Gmail messages trigger triage automatically instead of sitting until you notice them.
Gemini classifies each email as an inquiry, a project update, or feedback.
Replies get generated and sent from the correct branch (update reply, feedback acknowledgement, or inquiry meeting reply).
Threads are marked as read and labeled after handling, so inbox state stays clean.

Most teams get about 1–2 hours back per day once volume picks up.
Clients receive faster responses that feel consistent across the whole team.
Fewer “just checking in” follow-ups because the first reply is timely and clear.
Meeting requests turn into actual calendar invites, not “I’ll send something soon.”
Auditability improves because correspondence is systematically processed and organized.

Expected Results

Say your shared inbox gets 30 emails on a weekday, and about 10 of them need a real reply. If you spend roughly 6 minutes reading, deciding, drafting, and then labeling/marking read, that’s about an hour of repetitive work daily. Add two meeting requests at maybe 10 minutes each to find times and send invites, and you’re around 1.5 hours. With this workflow, you’re mostly reviewing edge cases: maybe 10 minutes to scan what was sent, while the calendar invites and labels happen automatically in the background.

Before You Start

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Gmail for inbox access and sending replies
Google Calendar to create and update meeting invites
Google Gemini API access (get it from Google AI Studio / Google Cloud credentials)

Skill level: Intermediate. You’ll connect Google accounts, review AI prompts, and map a few fields for replies and calendar events.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

A new email arrives in Gmail. The Gmail trigger starts the workflow as soon as a message hits the inbox, so nothing depends on you “getting to it later.”

Internal senders and reply eligibility are checked. Two quick decision gates prevent awkward automation moments. You can keep internal threads from generating replies, and you can block auto-replies for messages that don’t meet your rules.

Gemini determines intent and routes the message. The AI classifier labels the email as inquiry, project update, or feedback, then the workflow sends the matching response through the appropriate email node.

Meeting requests trigger calendar work. For inquiries that look like “let’s meet,” Google Calendar is queried for slots, then n8n loops through options in batches and creates or updates an invite using a prepared payload.

Everything gets cleaned up after the reply. Gmail marks the thread read and applies labels, so you can trust what “done” means again. You can easily modify the eligibility rules or the labeling scheme based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Gmail Trigger

This workflow starts by polling a Gmail label for new messages and routes them into the automation.

Add the Gmail Inbox Trigger node to your canvas.
Set Simple to false.
Under Filters → Label IDs, set the label to [YOUR_ID].
Set Poll Times to everyHour.
Credential Required: Connect your gmailOAuth2 credentials.

If you want to keep the visual header, leave Flowpast Branding as a sticky note (no configuration required).

Tip: Make sure [YOUR_ID] matches a real Gmail label ID, not the label name. You can find it in Gmail settings or via the Gmail API.

Step 2: Add Sender and Reply Eligibility Checks

Filter out internal senders and prevent replies to existing threads before classifying the email intent.

Connect Gmail Inbox Trigger to Internal Sender Check.
In Internal Sender Check, set the condition to Contains with Left Value {{ $json.headers.from }} and Right Value @[YOUR_DOMAIN].
Connect the false output of Internal Sender Check to Reply Eligibility Check.
In Reply Eligibility Check, set the condition to Not Starts With with Left Value {{ $json.subject }} and Right Value Re:.

Step 3: Set Up AI Intent Classification

Classify the incoming email into questions, project updates, or feedback to determine which response path to use.

Connect Reply Eligibility Check to Email Intent Sorter.
Set Input Text in Email Intent Sorter to {{ $('Gmail Inbox Trigger').item.json.subject }} {{ $('Gmail Inbox Trigger').item.json.text }}.
Ensure the categories include Questions, Project Update, and Feedback with their descriptions.
Add Gemini Chat Engine as the language model for Email Intent Sorter and set Model Name to models/gemini-2.0-flash-exp.
Credential Required: Connect your googlePalmApi credentials to Gemini Chat Engine (credentials are added to the parent model node, not Email Intent Sorter).

Email Intent Sorter outputs to Calendar Slot Lookup, Project Update Reply, and Feedback Acknowledgement in parallel.

Step 4: Configure the Meeting Scheduling Path

When the email is a question, the workflow prepares calendar invites and sends a scheduling reply.

In Calendar Slot Lookup, set Operation to getAll, Limit to 3, and Time Max to =.
Set Options → Query to Available – Office Visit, Order By to startTime, and Recurring Event Handling to expand.
Choose the calendar as [YOUR_EMAIL] under Calendar.
Credential Required: Connect your googleCalendarOAuth2Api credentials to Calendar Slot Lookup.
Connect Calendar Slot Lookup to Batch Iterator, then set up the two outputs: Batch Iterator → Prepare Invite Payload and Batch Iterator → Calendar Invite Update.
In Calendar Invite Update, set Event ID to {{$json.id}} and add attendees with {{ $("Gmail Inbox Trigger").item.json.from.value[0].address }}; set Send Updates to all.
Credential Required: Connect your googleCalendarOAuth2Api credentials to Calendar Invite Update.
In Prepare Invite Payload, keep the provided JavaScript to build slotTimes and sender details from Gmail Inbox Trigger.
In Inquiry Meeting Reply, set Subject to Re: {{ $json.originalSub }} and To Email to {{ $json.senderName }} <{{ $json.senderEmail }}>, and keep From Email as [YOUR_EMAIL].
Credential Required: Connect your smtp credentials to Inquiry Meeting Reply.

Prepare Invite Payload → Inquiry Meeting Reply continues the meeting reply flow after calendar processing.

Step 5: Configure Acknowledgement Replies and Gmail Actions

Project updates and feedback emails receive tailored responses, and processed messages are marked and labeled.

In Project Update Reply, set Subject to Re: {{ $('Gmail Inbox Trigger').item.json.subject }}, To Email to {{ $json.from.value[0].name }} <{{ $json.from.value[0].address }}>, and From Email to [YOUR_EMAIL].
Credential Required: Connect your smtp credentials to Project Update Reply.
In Feedback Acknowledgement, set Subject to Re: {{ $('Gmail Inbox Trigger').item.json.Subject }}, To Email to {{ $json.from.value[0].name }} <{{ $json.from.value[0].address }}>, and From Email to [YOUR_EMAIL].
Credential Required: Connect your smtp credentials to Feedback Acknowledgement.
Connect Project Update Reply, Feedback Acknowledgement, and Inquiry Meeting Reply to Flag Message Read.
In Flag Message Read, set Operation to markAsRead and Message ID to {{ $('Gmail Inbox Trigger').all()[0].json.id }}.
Credential Required: Connect your gmailOAuth2 credentials to Flag Message Read.
Connect Flag Message Read to Attach Update Label and set Operation to addLabels, Label IDs to [YOUR_ID], and Message ID to {{ $('Gmail Inbox Trigger').all()[0].json.id }}.
Credential Required: Connect your gmailOAuth2 credentials to Attach Update Label.

⚠️ Common Pitfall: Feedback Acknowledgement uses {{ $('Gmail Inbox Trigger').item.json.Subject }} (capital S). If your Gmail data uses subject (lowercase), update this expression to avoid blank subjects.

Step 6: Test and Activate Your Workflow

Validate the routing, calendar invite generation, and reply templates before going live.

Click Execute Workflow and send test emails that match each category (Questions, Project Update, Feedback).
Confirm that Inquiry Meeting Reply sends a message listing three slots and that Calendar Invite Update adds the sender as an attendee.
Verify that Project Update Reply and Feedback Acknowledgement send the correct HTML responses.
Check that Flag Message Read marks the email as read and Attach Update Label adds the label [YOUR_ID].
When satisfied, toggle the workflow to Active for production use.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

Gmail credentials can expire or need specific permissions. If things break, check the n8n Credentials screen and your Google account security/app access 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.

Quick Answers

What’s the setup time for this Gmail Calendar automation?

About 30 minutes if your Google accounts are ready.

Is coding required for this Gmail Calendar automation?

No. You’ll connect Google credentials and adjust prompts and rules in n8n.

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 Google Gemini usage, which is typically small per email but depends on your prompt size and 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.

Can I modify this Gmail Calendar automation workflow for different use cases?

Yes, and you should. Most teams start by changing the “Reply Eligibility Check” rules, then rewriting the prompts used by the Gemini chat node so replies match their tone. You can also adjust the categories in the “Email Intent Sorter” to fit your inbox (like “billing,” “support,” or “partnership”). On the scheduling side, swap which calendar gets queried in “Calendar Slot Lookup,” or change what fields are written into the event in the “Prepare Invite Payload” step.

Why is my Gmail connection failing in this workflow?

Usually it’s expired or revoked Google OAuth access. Reconnect your Gmail credential in n8n, then confirm the Gmail trigger has permission to read the mailbox and the send node can send from the intended address. If it only fails for some threads, check label permissions and whether the message lives in a restricted mailbox (like another user’s shared inbox). Also watch for rate limits if you’re processing a backlog.

What volume can this Gmail Calendar automation workflow process?

For most small teams, hundreds of emails per day is fine, as long as you’re not trying to process years of history at once.

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

Often, yes, because this workflow isn’t just “if email then reply.” It has multiple decision gates (internal sender checks, eligibility rules), intent classification, and a batching loop for calendar slot handling. n8n is built for that kind of branching without turning your automation into a fragile chain of single-purpose zaps. Zapier or Make can still work if you only want a simple draft or a notification, and you don’t need the calendar loop. If you’re unsure, Talk to an automation expert and describe your inbox volume and risk tolerance for auto-sending.

Once this is running, your inbox stops being a to-do list and becomes a system. You’ll feel the difference the first week.

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": "16de00c966030c3de60297eb4689ff88b56c004b002dbe0f2a223dbece1c2dde",
"templateId": null,
"templateCredsSetupCompleted": null
},
"name": "Automated Email Response System",
"tags": [],
"nodes": [
{
"id": "flowpast-topbar-4807",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
20
],
"parameters": {
"color": 7,
"width": 1105,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "e485ab21-6c33-4cb1-9bd1-3fea3a1d431a",
"name": "Gmail Inbox Trigger",
"type": "n8n-nodes-base.gmailTrigger",
"position": [
1005,
225
],
"parameters": {
"simple": false,
"filters": {
"labelIds": [
"[YOUR_ID]"
]
},
"options": [],
"pollTimes": {
"item": [
{
"mode": "everyHour"
}
]
}
},
"credentials": {
"gmailOAuth2": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.2
},
{
"id": "d52b02ce-95aa-495f-a6b4-d5dd791f2808",
"name": "Email Intent Sorter",
"type": "@n8n/n8n-nodes-langchain.textClassifier",
"position": [
410,
235
],
"parameters": {
"options": [],
"inputText": "={{ $('Gmail Inbox Trigger').item.json.subject }}\n{{ $('Gmail Inbox Trigger').item.json.text }}",
"categories": {
"categories": [
{
"category": "Questions",
"description": "Use this category when the email is asking for information about our company, products, processes, pricing, timelines, legal terms or any other general inquiry that expects a factual explanation or guidance."
},
{
"category": "Project Update",
"description": "Choose this category when the sender is notifying us about progress or changes: signing the agreement, submitting or revising scripts, updating requirements, sharing evaluation results, or any status report that moves an ongoing project forward"
},
{
"category": "Feedback",
"description": "Select this category when the email contains compliments, complaints, suggestions, or any qualitative feedback about our service, product, communication or overall experience"
}
]
}
},
"typeVersion": 1
},
{
"id": "adfca78f-9ce5-4345-baaa-017538e433be",
"name": "Gemini Chat Engine",
"type": "@n8n/n8n-nodes-langchain.lmChatGoogleGemini",
"position": [
350,
410
],
"parameters": {
"options": [],
"modelName": "models/gemini-2.0-flash-exp"
},
"credentials": {
"googlePalmApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1
},
{
"id": "e7c91741-20d6-4c54-8dd5-efec164c29b3",
"name": "Project Update Reply",
"type": "n8n-nodes-base.emailSend",
"position": [
185,
395
],
"webhookId": "120f4cfb-cfd3-4792-b5f5-146e9f495f73",
"parameters": {
"html": "=<!DOCTYPE html>\n<html>\n<head>\n  <style>\n    body{font-family:Arial,sans-serif;line-height:1.6;color:#333;margin:0;padding:0;}\n    .container{width:100%;max-width:600px;margin:0 auto;padding:20px;}\n    .header{background:#f4f4f4;padding:10px 20px;text-align:center;border-bottom:1px solid #ddd;}\n    .header h1{margin:0;color:#555;}\n    .content{padding:20px;}\n    .content h2{color:#555;font-size:18px;margin:20px 0 10px;}\n    .content p{margin-bottom:15px;}\n    .content ul{list-style:disc;padding-left:20px;}\n    .content ul li{margin-bottom:10px;}\n    .footer{text-align:center;font-size:12px;color:#888;margin-top:20px;}\n  </style>\n<link rel="preload" as="image" href="https://flowpast.s3.eu-north-1.amazonaws.com/featured_blog_images/102578.webp"><link rel="preload" as="image" href="https://flowpast.s3.eu-north-1.amazonaws.com/featured_blog_images/102578.webp"></head>
\n<body>\n  <div class=\"container\">\n    <div class=\"header\">\n      <h1>Project Update Acknowledgement</h1>\n    </div>\n\n    <div class=\"content\">\n      <p>\n        Hi {{ $json.from.value[0].name || $('Gmail Inbox Trigger').item.json.headers.from.split('<')[0].trim() || 'there' }},\n      </p>\n\n      <p>\n        Thank you for your recent update. We\u2019ve reviewed the information and logged it in our system.\n      </p>\n\n      <h2>What we received:</h2>\n      <ul>\n        <li>Agreement confirmations or approvals.</li>\n        <li>Revised requirements or scope changes.</li>\n        <li>Draft materials or deliverables for review.</li>\n        <li>Status reports or progress updates.</li>\n      </ul>\n\n      <h2>Next steps:</h2>\n      <ul>\n        <li>Our team will review the materials within <strong>2\u20133 business days</strong>.</li>\n        <li>If clarifications are needed, we\u2019ll reach out via email.</li>\n        <li>You\u2019ll receive an updated timeline after review.</li>\n      </ul>\n\n      <p>\n        If you have additional files or questions, feel free to reply to this email.\n      </p>\n\n      <p>\n        Best regards,<br>\n        <strong>Customer Success Team</strong>\n      </p>\n    </div>\n\n    <div class=\"footer\">\n      \u00a9 2025 Company. All rights reserved.\n    </div>\n  </div>\n</body>\n</html>\n",
"options": {
"appendAttribution": false
},
"subject": "=Re: {{ $('Gmail Inbox Trigger').item.json.subject }}",
"toEmail": "={{ $json.from.value[0].name }} <{{ $json.from.value[0].address }}>",
"fromEmail": "[YOUR_EMAIL]"
},
"credentials": {
"smtp": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.1
},
{
"id": "61243957-40d1-4fb2-ad0a-6f923587c4db",
"name": "Feedback Acknowledgement",
"type": "n8n-nodes-base.emailSend",
"position": [
135,
555
],
"webhookId": "700cb9ed-bd54-4e96-8121-98a5dcffeebf",
"parameters": {
"html": "=<!DOCTYPE html>\n<html>\n<head>\n  <style>\n    body{font-family:Arial,sans-serif;line-height:1.6;color:#333;margin:0;padding:0;}\n    .container{width:100%;max-width:600px;margin:0 auto;padding:20px;}\n    .header{background:#f4f4f4;padding:10px 20px;text-align:center;border-bottom:1px solid #ddd;}\n    .header h1{margin:0;color:#555;}\n    .content{padding:20px;}\n    .content h2{color:#555;font-size:18px;margin:20px 0 10px;}\n    .content p{margin-bottom:15px;}\n    .content ul{list-style:disc;padding-left:20px;}\n    .content ul li{margin-bottom:10px;}\n    .footer{text-align:center;font-size:12px;color:#888;margin-top:20px;}\n  </style>\n<link rel="preload" as="image" href="https://flowpast.s3.eu-north-1.amazonaws.com/featured_blog_images/102578.webp"><link rel="preload" as="image" href="https://flowpast.s3.eu-north-1.amazonaws.com/featured_blog_images/102578.webp"></head>
\n<body>\n  <div class=\"container\">\n    <div class=\"header\">\n      <h1>Thank You for Your Feedback</h1>\n    </div>\n\n    <div class=\"content\">\n      <p>\n        Hi {{ $json.from.value?.[0]?.name || $('Gmail Inbox Trigger').item.json.headers.from.split('<')[0].trim() || 'there' }},\n      </p>\n\n      <p>\n        Thank you for taking the time to share your feedback. We truly value every comment because it helps us improve.\n      </p>\n\n      <h2>What happens next:</h2>\n      <ul>\n        <li>Your message has been logged in our system (<strong>Reference ID:</strong> {{ $json.id.slice(-6) }}).</li>\n        <li>Our team will review it within <strong>1 business day</strong>.</li>\n        <li>If an action is required, the appropriate team member will follow up directly with you.</li>\n      </ul>\n\n      <p>\n        If you need to add more details, simply reply to this email.\n      </p>\n    </div>\n\n    <div class=\"footer\">\n      \u00a9 2025 Company. All rights reserved.\n    </div>\n  </div>\n</body>\n</html>\n",
"options": {
"appendAttribution": false
},
"subject": "=Re:  {{ $('Gmail Inbox Trigger').item.json.Subject }}",
"toEmail": "={{ $json.from.value[0].name }} <{{ $json.from.value[0].address }}>",
"fromEmail": "[YOUR_EMAIL]"
},
"credentials": {
"smtp": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.1
},
{
"id": "a2542d02-4018-45e5-a8f2-875e669c77a3",
"name": "Flag Message Read",
"type": "n8n-nodes-base.gmail",
"position": [
460,
440
],
"webhookId": "a5bea8d3-719e-4b2b-a43d-4c6248796267",
"parameters": {
"messageId": "={{ $('Gmail Inbox Trigger').all()[0].json.id }}\n",
"operation": "markAsRead"
},
"credentials": {
"gmailOAuth2": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.1
},
{
"id": "0a1d79a3-91cf-4bf6-93bb-1482549a74dd",
"name": "Attach Update Label",
"type": "n8n-nodes-base.gmail",
"position": [
585,
410
],
"webhookId": "c3a2fc4e-d90c-463a-a356-db530e1b91b0",
"parameters": {
"labelIds": [
"[YOUR_ID]"
],
"messageId": "={{ $('Gmail Inbox Trigger').all()[0].json.id }}\n",
"operation": "addLabels"
},
"credentials": {
"gmailOAuth2": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.1
},
{
"id": "28467e9f-a730-4545-89cb-7d2c629edd71",
"name": "Internal Sender Check",
"type": "n8n-nodes-base.if",
"position": [
835,
190
],
"parameters": {
"options": [],
"conditions": {
"options": {
"version": 2,
"leftValue": "",
"caseSensitive": true,
"typeValidation": "strict"
},
"combinator": "or",
"conditions": [
{
"id": "7cffe101-333d-4ec2-a822-181fe421745b",
"operator": {
"type": "string",
"operation": "contains"
},
"leftValue": "={{ $json.headers.from }}",
"rightValue": "@[YOUR_DOMAIN]"
}
]
}
},
"typeVersion": 2.2
},
{
"id": "b150ab4d-dcbb-4ae6-9503-5914e39f41ac",
"name": "Reply Eligibility Check",
"type": "n8n-nodes-base.if",
"position": [
555,
210
],
"parameters": {
"options": [],
"conditions": {
"options": {
"version": 2,
"leftValue": "",
"caseSensitive": true,
"typeValidation": "strict"
},
"combinator": "and",
"conditions": [
{
"id": "07a6d5e2-ffc5-41d8-b69a-abd6860879c0",
"operator": {
"type": "string",
"operation": "notStartsWith"
},
"leftValue": "={{ $json.subject }}",
"rightValue": "Re:"
}
]
}
},
"typeVersion": 2.2
},
{
"id": "1f043246-cbd0-466d-bbfd-b13131a66f03",
"name": "Inquiry Meeting Reply",
"type": "n8n-nodes-base.emailSend",
"position": [
0,
305
],
"webhookId": "ed01c3d4-1fad-4098-b431-4bc3d5e05434",
"parameters": {
"html": "=<p>\n  Hi {{ $json.senderName }} <{{ $json.senderEmail }}>,\n</p>\n\n<p>Thanks for reaching out with your questions. I\u2019d love to cover everything face-to-face.</p>\n\n<p><strong>Location:</strong><br>\nOffice Address\n</p>\n\n<p>We just sent you three calendar invitations for these time slots:</p>\n\n<ul>\n  {{ $json.slotTimes.map(t => `<li>${t}</li>`).join('') }}\n</ul>\n\n<p>\n  Click <em>Yes</em> on the invite that works best for you.  \n  The selected slot will be reserved automatically; the other two will stay open.\n</p>\n\n<p>\n  If none of the times work, reply with a couple of alternatives and I\u2019ll find something that fits.\n</p>\n\n<p>Looking forward to meeting you!<br>\u2014 Support Team</p>\n",
"options": {
"appendAttribution": false
},
"subject": "=Re: {{ $json.originalSub }}",
"toEmail": "={{ $json.senderName }} <{{ $json.senderEmail }}>",
"fromEmail": "[YOUR_EMAIL]"
},
"credentials": {
"smtp": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.1
},
{
"id": "60d50fdc-4e7f-4ab1-a240-1be4c8ae7520",
"name": "Calendar Slot Lookup",
"type": "n8n-nodes-base.googleCalendar",
"position": [
195,
120
],
"parameters": {
"limit": 3,
"options": {
"query": "Available \u2013 Office Visit",
"orderBy": "startTime",
"recurringEventHandling": "expand"
},
"timeMax": "=",
"calendar": {
"__rl": true,
"mode": "list",
"value": "[YOUR_EMAIL]",
"cachedResultName": "Meeting slots"
},
"operation": "getAll"
},
"credentials": {
"googleCalendarOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.3
},
{
"id": "48a8b613-54e3-4002-8830-1726a23d24aa",
"name": "Batch Iterator",
"type": "n8n-nodes-base.splitInBatches",
"position": [
5,
180
],
"parameters": {
"options": []
},
"typeVersion": 3
},
{
"id": "de676780-43c8-476d-ab8a-a692ffe4e65f",
"name": "Calendar Invite Update",
"type": "n8n-nodes-base.googleCalendar",
"position": [
20,
430
],
"parameters": {
"eventId": "={{$json.id}}",
"calendar": {
"__rl": true,
"mode": "list",
"value": "[YOUR_EMAIL]",
"cachedResultName": "Meeting slots"
},
"operation": "update",
"updateFields": {
"attendeesUi": {
"values": {
"attendees": [
"={{ $(\"Gmail Inbox Trigger\").item.json.from.value[0].address }}\n"
]
}
},
"sendUpdates": "all"
}
},
"credentials": {
"googleCalendarOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.3
},
{
"id": "df5552fc-910b-4b13-81fa-0c9d98ce82d7",
"name": "Prepare Invite Payload",
"type": "n8n-nodes-base.code",
"position": [
120,
325
],
"parameters": {
"jsCode": "const triggerJson = $('Gmail Inbox Trigger').item.json;\nconst headersFrom  = triggerJson.headers.from;      // \"Name <[YOUR_EMAIL]>\"\n\n// Split into name and address\nconst namePart = headersFrom.split('<')[0].replace(/^From:\\s*/i, '').trim();\nconst emailPart = headersFrom.match(/<([^>]+)>/)?.[1] || headersFrom;\n\nconst slotTimes = items.map(i =>\n  new Date(i.json.start.dateTime || i.json.start.date).toLocaleString(\n    'en-US',\n    { weekday:'short', month:'short', day:'numeric', hour:'numeric',\n      minute:'2-digit', hour12:true }\n  )\n);\n\nreturn [{\n  json: {\n    slotTimes,\n    senderName:  namePart,\n    senderEmail: emailPart,\n    originalSub: triggerJson.subject               // pass the subject along\n  }\n}];\n"
},
"typeVersion": 2
}
],
"active": false,
"pinData": [],
"settings": {
"executionOrder": "v1"
},
"versionId": null,
"connections": {
"Prepare Invite Payload": {
"main": [
[
{
"node": "Inquiry Meeting Reply",
"type": "main",
"index": 0
}
]
]
},
"Reply Eligibility Check": {
"main": [
[
{
"node": "Email Intent Sorter",
"type": "main",
"index": 0
}
]
]
},
"Feedback Acknowledgement": {
"main": [
[
{
"node": "Flag Message Read",
"type": "main",
"index": 0
}
]
]
},
"Flag Message Read": {
"main": [
[
{
"node": "Attach Update Label",
"type": "main",
"index": 0
}
]
]
},
"Gmail Inbox Trigger": {
"main": [
[
{
"node": "Internal Sender Check",
"type": "main",
"index": 0
}
]
]
},
"Inquiry Meeting Reply": {
"main": [
[
{
"node": "Flag Message Read",
"type": "main",
"index": 0
}
]
]
},
"Calendar Slot Lookup": {
"main": [
[
{
"node": "Batch Iterator",
"type": "main",
"index": 0
}
]
]
},
"Batch Iterator": {
"main": [
[
{
"node": "Prepare Invite Payload",
"type": "main",
"index": 0
}
],
[
{
"node": "Calendar Invite Update",
"type": "main",
"index": 0
}
]
]
},
"Email Intent Sorter": {
"main": [
[
{
"node": "Calendar Slot Lookup",
"type": "main",
"index": 0
}
],
[
{
"node": "Project Update Reply",
"type": "main",
"index": 0
}
],
[
{
"node": "Feedback Acknowledgement",
"type": "main",
"index": 0
}
]
]
},
"Calendar Invite Update": {
"main": [
[
{
"node": "Batch Iterator",
"type": "main",
"index": 0
}
]
]
},
"Project Update Reply": {
"main": [
[
{
"node": "Flag Message Read",
"type": "main",
"index": 0
}
]
]
},
"Gemini Chat Engine": {
"ai_languageModel": [
[
{
"node": "Email Intent Sorter",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"Internal Sender Check": {
"main": [
[],
[
{
"node": "Reply Eligibility Check",
"type": "main",
"index": 0
}
]
]
}
}
}