n8n Real Estate Lead Automation: Portal Alerts to Leads

An n8n real estate lead workflow reads the alert emails that portals and your website already send you, extracts each lead with AI, drops duplicates, scores the lead and alerts you the moment a hot one arrives. Below are the five copyable templates for that flow, sized for a solo agent, plus the consent and portal rules that decide which parts you can automate.

Checked October 2026 against n8n's docs for the Email Trigger (IMAP), Remove Duplicates and Twilio nodes, the FCC's robocalls and robotexts guide, the FTC's Do Not Call Q&A for sellers and Twilio's A2P 10DLC docs. This is not legal advice; state rules can be stricter, so check with your brokerage.

The design choice that matters most: the workflow automates the work around the lead (reading, sorting, scoring, alerting you) and keeps contact with the lead behind a consent gate. That keeps the speed advantage without turning a portal inquiry into an unlawful automated text. For more n8n builds in this style, start at the n8n templates and automation library.

The real estate lead automation workflow at a glance

The five n8n real estate templates

Template 1: the workflow skeleton

Build these nodes in order. Every node named here is in n8n's docs; the Email Trigger reads a mailbox over IMAP and can mark each email as read, and Remove Duplicates can compare items against previous executions so a lead seen yesterday is not processed again today.

1. Email Trigger (IMAP)    mailbox: Leads, action: Mark as Read
2. Information Extractor   -> name, phone, email, property, intent, timeline, budget
3. Code / Set              normalise phone to E.164, lowercase email, build lead_id
4. Remove Duplicates       Remove Items Processed in Previous Executions
                           Keep Items Where: Value Is New, Value to Dedupe On: lead_id
5. Basic LLM Chain         qualification prompt (template 2) -> score + reason
6. Switch on score         hot | warm | nurture
7a. hot   -> Twilio SMS to YOU (agent alert) + consent-gated SMS to lead
7b. warm  -> CRM / sheet row + follow-up task for tomorrow
7c. nurture -> email list only (no texts, no calls)
8. Error Trigger workflow  alerts you if any step fails

Template 2: the AI qualification prompt

Paste this into a Basic LLM Chain or similar AI node. Fill the braces with your area and price range, and pass the extracted lead as JSON.

You qualify real estate inquiries for a solo agent in {AREA}.
Return JSON only: {"score": "hot|warm|nurture", "reason": "...", "questions": ["..."]}

Score "hot" only if ALL are true:
- intent is buy or sell (not rent, not "just browsing")
- timeline is within 3 months, or the lead asked for a viewing
- property or budget fits {AREA} and {PRICE_RANGE}
Score "nurture" if the timeline is over 12 months or unknown and no viewing was requested.
Otherwise score "warm".
Never invent details. If a field is missing, say so in "reason".
"questions": up to 2 questions the agent should ask on the first call.

Lead: {LEAD_JSON}

Template 3: the lead record

Keep the same fields in your sheet or CRM so scoring and reporting stay consistent. The sms_consent field is the one that protects you.

Template 4: the first text (consent-gated)

Send this with the Twilio node only when sms_consent is true. It names you and your brokerage and tells the lead how to opt out.

Hi {FIRST_NAME}, this is {AGENT_NAME} with {BROKERAGE}.
Thanks for asking about {PROPERTY_SHORT}. Are you free for a quick
call today or tomorrow? Reply STOP to opt out.

Template 5: the agent brief

This goes to your own phone, which needs no consent from the lead. It is the real handoff: you read it, then call.

HOT LEAD - {SOURCE} - {TIME_RECEIVED}
{NAME}  {PHONE}  {EMAIL}
Asked about: {PROPERTY} ({INTENT}, timeline: {TIMELINE}, budget: {BUDGET})
Why hot: {REASON}
Ask first: {QUESTION_1} / {QUESTION_2}
SMS consent on file: {SMS_CONSENT}  -> if "no", call or email manually

How to fill the templates for your market

If you want the dedupe and scoring pattern in a broader sales setting, our guide to lead generation automation covers it, and the n8n CRM automation guide shows how to push the lead record into Pipedrive, HubSpot or Salesforce instead of a sheet.

Real estate lead automation workflow: which rules apply?

Three sets of rules decide what the automation may do. None of them stop you automating the inside of your business; they govern how you contact people.

• Texts and calls (FCC). The FCC's guide says autodialed texts to a mobile phone need the owner's prior consent, commercial texts need written consent (which can be given electronically, such as through a website form), and people may opt out of any robocall or robotext at any time in any reasonable manner. It also states that AI-generated voice calls are illegal unless the consumer agreed to receive them or the caller is exempt, and that prerecorded or artificial-voice calls must give the caller's name, number and business name at the start (checked October 2026).
• Do Not Call (FTC). Per the FTC's seller Q&A, a company may call a consumer for up to three months after an inquiry even if the number is on the National Do Not Call Registry, but must stop if the person asks not to be called. That covers you calling an inquiry yourself; it is a separate question from the consent needed for automated texts or AI voices.
• Portals. Each listing portal sets its own terms of use. Read them before automating anything that touches the portal itself. This template stays on the safe side: it only reads the emails the portal sends to you, and it does not scrape listings or log in on your behalf.

On the sending side, Twilio's docs say anyone sending application-to-person SMS over a US 10-digit long code must register for A2P 10DLC, and unregistered traffic gets extra carrier fees and filtering. Twilio also handles standard opt-out replies such as STOP, UNSUBSCRIBE and CANCEL by default on long code numbers, per its opt-out docs (checked October 2026). Write opted-out numbers back to your lead record too, so no other channel contacts them.

Weak vs strong setup

Where voice AI fits for a solo agent

Voice AI receptionists come up in every conversation about real estate automation. The FCC position above makes outbound AI calls to cold leads a poor fit. The better fit is inbound: an assistant that answers when a lead calls your number, takes details and books a time, with the caller told they are speaking to an AI. Our guide to building AI phone agents covers that setup. In this template, the n8n Twilio node's text-to-speech call is best used to ring you, not the lead.

If you want to turn workflows like this into a product other agents pay for, with onboarding, billing and a dashboard around it, our AI SaaS Builder program walks through that build.

What to check in the first month

A lead workflow fails quietly. Nothing crashes when a portal changes its alert email layout; the extractor simply returns empty phone numbers and the leads stop reaching you. Three habits catch that early.

• Count leads per source each week. Add a row to a sheet for every lead the workflow processes, with the source and the score. If one source drops to zero while the portal still shows inquiries, the alert format changed.
• Review every nurture score once. Read the reason field the prompt returns. If buyers with near-term plans keep landing in nurture, a rule in the prompt is too strict, and the fix is a clearer sentence, not a bigger model.
• Keep a human override. Give yourself a quick way to re-score a lead by hand, for example a dropdown column in the sheet, and use the overrides to improve the prompt each month.

None of this needs extra tooling. It is the same discipline you would apply to a new assistant: trust grows with evidence, and the workflow earns more autonomy only after its scores match yours.

Before you switch it on

For that last item, our n8n error handling guide shows how to set up an error workflow, so a broken extractor never silently loses a hot lead.

n8n real estate automation: FAQ