Templates / Qualify and route real estate leads with Google Gemini, Gmail, Slack and Sheets

Qualify and route real estate leads with Google Gemini, Gmail, Slack and Sheets

Ready for 3.0

by Hassan ✓ · 2 views · created 2026-10-02 · Lead Generation, AI Summarization

Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.

Nodes used (11)

Google GeminiGoogle SheetsGmailSlack

What it does

Quick overview Automatically qualifies incoming leads with Gemini AI, routes each one to the best available agent by speciality and workload, notifies via Gmail and Slack, escalates to the broker if unacknowledged within 15 minutes, and delivers a weekly performance report, covering every lead from arrival to assignment to follow-up. How it works 1. Section A — Lead Qualification and Routing: 2. A lead arrives via webhook from any source — a website form, a CRM, or any previous QualMatic template passing a Hot lead automatically. 3. Gemini AI qualifies the lead as Hot, Warm, or Cold based on intent, timeline, budget, and message content. 4. Cold leads are logged to a cold queue and held for manual review — no agent is disturbed for low-quality leads. 5. Hot and Warm leads route immediately. The workflow selects the best agent by matching the lead's intent to agent speciality (Buyer / Seller / Rental / Investment / General), then load-balancing within matching agents by active lead count — the least busy specialist gets the lead. 6. Three notifications fire simultaneously — a detailed Gmail to the assigned agent with a click-to-acknowledge link, a Slack DM for instant mobile alert, and a broker copy email for full visibility. 7. Optionally creates a Pipedrive contact and deal automatically. 8. Section B — Acknowledgement: 9. When the agent clicks the acknowledgement link, a webhook records the acknowledgement timestamp, calculates the response time in minutes, and sends a confirmation email. 10. Section C — Escalation: 11. If the agent has not acknowledged within the configured timeout (default 15 minutes), the broker receives an escalation alert via Gmail and Slack — flagging the unacknowledged lead for immediate action. 12. Section D — Weekly Performance Digest: 13. Every Monday at 8 am, a performance report is delivered to the broker — leads assigned per agent, acknowledgement rates, average response times, score breakdown, and escalation count. Setup 1. Add credentials for Google Gemini (PaLM) API, Google Sheets OAuth2, Gmail OAuth2, and Slack OAuth2. 2. Create or choose a Google Sheets spreadsheet with tabs for Lead Assignments, Agents, and Weekly Performance Log, and set the document ID and sheet tabs in all Google Sheets nodes. 3. Update the brokerage configuration values (broker email/name, broker Slack channel, escalation minutes, N8NWEBHOOKBASEURL, and AGENTSJSON with real agent emails and Slack user IDs) and keep the separate weekly-digest broker configuration in sync. 4. Copy the “New Lead Received” webhook URL into your lead source (website form/CRM) and ensure the public base URL is set so acknowledgement links resolve externally. 5. If using Pipedrive, set USEPIPEDRIVE to true and fill in PIPEDRIVEDOMAIN and PIPEDRIVEAPITOKEN in the configuration. Requirements - Google Sheets setup: Create the Brokerage Lead Router sheet template and link its ID to all Sheets nodes. Three tabs required. Tab 1 — Lead Assignments — columns: Assignment ID, Timestamp, Lead Name, Email, Phone, Lead Source, Intent, Budget, Timeline, Message, AI Score, Score Reasoning, Assigned Agent ID, Assigned Agent Name, Assignment Method, Acknowledged, Acknowledged At, Response Time (mins), Escalated, Pipedrive Deal ID, Status, Notes. Tab 2 — Agents — columns: Agent ID, Agent Name, Email, Phone, Slack User ID, Speciality, Active Leads, Total Assigned, Avg Response Time (mins), Status. Tab 3 — Weekly Performance Log. - Agent roster setup: Populate the Agents tab with your team before activating. Each agent needs an Agent ID, name, email, Slack User ID, speciality (Buyer / Seller / Rental / Investment / General), starting Active Leads count, and Status (Available). Update AGENTSJSON in the Configuration node to match — this is the roster the routing logic reads at runtime. - Slack User ID: Each agent's Slack User ID is required for direct message notifications. Find it in Slack → click the agent's profile → three-dot menu → Copy member ID. Format: U1

View the original on n8n.io → Check your own copy

Get the weekly “what broke” email

New templates, newly broken ones, and n8n release changes. One short email a week.

Form not loading? Subscribe here.