Automate Real Estate Lead Replies with n8n, Claude & Gmail

Turn new real estate leads into fast, compliant replies—automatically

This n8n workflow receives incoming real estate leads, uses Anthropic Claude to qualify and draft a first message in your voice, checks quiet hours and consent/opt-out, sends the email via Gmail, then logs everything back to your CRM and triggers a follow-up if the lead stays silent.

What this workflow does

• Ingests a new lead through a webhook request with details such as name, email/phone, source, and enquiry message.
• Pulls existing CRM context by calling your CRM’s HTTP API to fetch contact history and background.
• Claude qualification extracts key signals (e.g., timeline, pre-approval, price band, intent). Low-confidence cases are routed to a manual review path.
• Claude reply drafting creates a short first reply (designed to include exactly one question). Flagged drafts go to manual review.
• Compliance checks verify quiet hours and consent/opt-out rules before any outbound messaging proceeds.
• Sends via Gmail using the generated subject and message content.
• Updates the CRM with an HTTP API call, then waits for a resume trigger to support a follow-up if there’s no response.

Use cases

• Auto-respond to real estate form submissions from your portal or website with a message that reflects lead intent.
• Pre-qualify leads against common buyer signals and route uncertain cases for human handling.
• Maintain consistent response times while respecting quiet hours and opt-out/consent requirements.
• Ensure every outreach attempt is logged in your CRM and follow-ups occur when the lead is silent.

Technical details

• Anthropic Claude (qualification + drafting)
• Gmail (send message node)
• HTTP Request nodes for CRM fetch/update via your CRM API (e.g., Follow Up Boss, kvCORE, HubSpot—replace placeholder URLs and add authentication)
• n8n nodes: if, set, code, no op, wait, gmail

Setup requirements: connect Anthropic credentials for Claude, add a Gmail credential, configure CRM API endpoints/authentication in both HTTP Request nodes, and update the workflow configuration values.