Automated email inquiry processing & routing with Gmail and Gemini AI
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: AI Agent v1 (old agent modes). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 9 nodes and runs on Gmail events. Along the way it connects Gmail, Google Gemini Chat Model and HTTP Request.
How it runs
Trigger: On Gmail events.
- AI Agent: runs an AI agent, with model: Google Gemini Chat Model; 1 tool (HTTP Request)
- Code: runs custom JavaScript code
- Wait: pauses before continuing
- If: checks a condition and branches into true / false
- availability check email (Gmail): uses Gmail
- Forward booking email (Gmail): uses Gmail
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- AI Agent v1 (old agent modes) in AI Agent (v1.9): replace with Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.
- Also check Gmail Trigger below v1.4 runs as v1.4 (drafts skipped, max emails per poll).
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| AI Agent v1 (old agent modes) AI Agent (v1.9) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (8)
- Gmail Trigger
n8n-nodes-base.gmailTrigger - AI Agent
@n8n/n8n-nodes-langchain.agent - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - Http Request Tool
n8n-nodes-base.httpRequestTool - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Gmail
n8n-nodes-base.gmail - Wait
n8n-nodes-base.wait
From the author
This automated n8n workflow processes any inquiry emails using AI-powered intelligence to determine customer intent and provide appropriate responses. The system analyzes incoming emails, performs availability checks or direct booking processing, and sends…