Capture and route real estate leads with Google Sheets, Gmail, and Slack

Quick overview This workflow captures real estate property inquiries via a webhook, validates and normalizes lead details, upserts the lead into Google Sheets, sends an auto-reply through Gmail, and notifies your team in Slack, with separate handling for high-priority leads and workflow failure alerts.

How it works Receives a website property inquiry via a POST webhook. Extracts the lead fields (name, email, phone, property ID, message, source, and timestamp) and rejects invalid submissions with a 400 JSON response explaining what’s missing. Normalizes the lead data by lowercasing the email address and stripping non-numeric characters from the phone number. Classifies the inquiry as high or standard priority based on keywords found in the message and property text. Appends or updates the lead in a Google Sheets CRM table, matching on email to avoid duplicates. Sends a Gmail auto-reply and posts a Slack notification, routing high-priority leads to a senior-agent message and standard leads to the general team. Returns a JSON confirmation to the webhook caller and posts a Slack alert if the workflow errors.

Setup Copy the webhook URL from the trigger and configure your website form/app to send a POST request with fields like name, email, phone, property_id, message, and source. Add a Google Sheets credential, replace the spreadsheet and sheet selection, and ensure the sheet has headers for Email, Name, Phone, Source, Message, Priority, Property, and Submitted At. Add a Gmail credential for sending the auto-reply emails and adjust the sender account and email copy if needed. Add a Slack OAuth2 credential and set the target channels for standard lead notifications, priority lead notifications, and failure alerts.

0
Downloads
0
Views
8.52
Quality Score
beginner
Complexity
Author:Redowan Ahmed Farhan(View Original →)
Created:7/5/2026
Updated:7/28/2026

🔒 Please log in to import templates to n8n and favorite templates

Workflow Visualization

Loading...

Preparing workflow renderer

Comments (0)

Login to post comments