n8n for Real Estate: Capture and Route Portal Inquiries Automatically

If your real estate agency gets inquiries from Zillow, Realtor.com, Idealista or any other portal and someone copies them by hand into a spreadsheet or CRM, you are losing leads every single day. n8n lets you automatically capture every inquiry that arrives from property portals, clean it, classify it, and route it to the right agent in under 60 seconds, with zero copy-paste. It is a low-code automation tool that connects to the inbox where inquiries land (or to the portal's API when one exists), turns each message into structured data, and triggers the first response and follow-up. The typical outcome: response time drops from hours to seconds, and no inquiry slips through the cracks.

Why real estate agencies lose portal leads

The problem is rarely a lack of inquiries. It is what happens after they arrive. The usual journey inside a mid-sized agency looks like this:

1. An email from Zillow arrives with a buyer's inquiry.
2. It lands in a shared inbox (leads@ or the front-desk address).
3. Someone sees it when they can: sometimes in 10 minutes, sometimes the next day.
4. They copy it into a spreadsheet or CRM, often incompletely.
5. They decide which agent should handle it and forward the email.
6. The agent replies after finishing the showing they were on.

Between step 1 and step 6, hours go by on average. And the industry data is blunt: reaching a lead within the first 5 minutes massively increases your odds of actually connecting compared to waiting 30 minutes or more. Every hour the lead waits, it cools off and sends the same inquiry to three other agencies.

n8n attacks exactly that bottleneck: it removes manual steps 2 through 5 and automates the first touch.

How the n8n capture flow works

A well-built capture-and-route flow has five stages. Let's walk through each with enough detail to actually build it.

1. Capture: read inquiries from the portals

Most portals (Zillow, Realtor.com, Trulia, Idealista, Rightmove) send an email for every inquiry. n8n uses the IMAP Email node to watch that inbox and trigger the flow whenever a new message arrives. If the portal offers a webhook or API (some pro plans do), you use a Webhook node, which is even cleaner.

2. Extraction: turn the email into data

The email body contains name, phone, the listing in question, and a message, but in free-form text that differs by portal. There are two paths:

• Regex / Code node: fast and free, but brittle when a portal changes its email format.
• AI layer: a node that passes the text to a cheap model (GPT-4o-mini or similar) and returns clean JSON with name, phone, email, listing_id, area, and message. It is far more robust to format changes and costs cents per inquiry.

For agencies juggling several portals, AI-powered extraction usually wins because it stops breaking every time a portal tweaks its email template.

3. Enrichment and deduplication

Before routing, cross-check the inquiry against your CRM: does this phone number already exist? Is this a returning lead? A node that queries your database prevents duplicates and lets you greet a repeat contact differently.

4. Routing: to the correct agent

This is the heart of it. Depending on your operation, a Switch node or a Code node routes the inquiry:

Assignment rule	How it works	Best for
By territory	Each area has a responsible agent	Teams split by zone
By price band	Luxury to one team, standard to another	Wide property mix
By property type	Commercial, residential, land	Diversified portfolios
Round-robin	Even split across active agents	Homogeneous teams
By current load	To the agent with the fewest open leads	Large CRM-integrated teams

The "who handles what" table can live in Google Sheets, Airtable, or your own CRM. n8n reads it, decides, and moves on.

5. Notification and logging

Once assigned, the flow does three things in parallel:

• Notifies the agent via SMS, WhatsApp, Slack or email, with all the data and a direct link to the listing.
• Inserts the lead into the CRM, already assigned, with no manual entry.
• Fires an instant auto-reply to the prospect ("Hi, we received your inquiry about listing X, an agent will be in touch shortly") so they know they're being handled within seconds.

Want to see how this flow would look against your own listings and portals? Book a presentation call and we'll show you a concrete design for your agency, built around the portals you already use.

A real example: a mid-sized agency

Take an agency with 4 agents that publishes around 120 listings and receives roughly 700 inquiries per month across three portals. Before automating:

• Average first-response time: ~4 hours.
• Inquiries that never made it into the CRM: ~15%.
• One person spent ~2 hours a day classifying and forwarding emails.

After implementing the n8n flow with AI classification and territory-based routing:

• Automatic first response: under 1 minute.
• Lost inquiries: close to 0%.
• Those 2 daily hours freed up for actual selling.
• Monthly automation cost: VPS + AI tokens under USD 25.

The point is not the technology, it's the math: if you recover even 10% of leads that used to cool off, at a typical real estate commission that pays for itself on the first closed deal.

A typical stack for the flow

These are the pieces we usually combine when building this automation:

1. n8n (self-hosted on a VPS or n8n Cloud) as the orchestrator.
2. A dedicated IMAP inbox for portal inquiries.
3. A cheap AI model for extraction and classification.
4. An existing CRM (HubSpot, Follow Up Boss, kvCORE) or a custom-built one when the operation justifies it.
5. WhatsApp Business API, SMS or Slack to notify agents.
6. Google Sheets / Airtable as the assignment table if you don't want to touch the CRM at first.

For agencies that also want to answer basic questions 24/7 before an agent picks up, we add an AI chatbot on top of the same flow, so the prospect gets listing info instantly while the agent is being assigned.

When this does NOT make sense

Being honest sells better than overpromising. This automation is not worth it if:

• You get fewer than 30-40 inquiries a month. At that volume one person handles them comfortably and the setup effort won't amortize quickly.
• You have no defined follow-up process. n8n routes faster, but if nobody follows up afterward, you're just automating chaos. Fix the sales process first.
• Your portals send no email and have no API. If you depend on logging into a dashboard to copy inquiries by hand with no email notification, there's no clean trigger. Scraping exists, but it's brittle and should be evaluated separately.
• You want a zero-maintenance solution. Portals change their email formats now and then; the flow needs occasional review. It is not "set and forget" forever.

If you fall into any of these, you may get more value from sorting out your CRM or a custom CRM before automating portals.

n8n vs. other options

Option	Monthly cost	Flexibility	Learning curve
n8n self-hosted	USD 5-20	Very high	Medium
n8n Cloud	USD 20-50	Very high	Medium
Zapier / Make	USD 30-100+	Medium	Low
Native CRM integration	Variable	Low	Low
Fully custom build	High upfront	Total	High

n8n wins when you want full control of the flow, predictable costs, and complex routing logic without paying per task executed like Zapier. For very specific cases or uncommon integrations, a custom build with your own APIs sometimes makes more sense.

Bottom line: response speed is conversion

In real estate, leads are won on speed and on order. n8n gives you both: it captures every portal inquiry, understands it, routes it to the right agent, and replies in seconds, all without manual entry. The investment is modest and the return is measured in deals that used to cool off in a shared inbox.

At Deepyze we design and implement these n8n flows integrated with your CRM and your portals, tailored to how your team actually works. If you're ready to stop losing leads between browser tabs, let's start your project and build the capture-and-route flow for your agency.