A Zillow lead hits your shared inbox at 6:47 PM on a Tuesday. The buyer wants a showing this weekend in the 90210 zip. Your office admin left at 5. By 9 AM Wednesday, the lead has been forwarded twice, claimed by the agent who happened to check email first, and duplicated in your CRM because someone else manually entered it "just in case."

This is what lead routing looks like at a typical 25-agent brokerage. Leads arrive from Zillow, Realtor.com, your website contact form, Facebook ads, and open-house sign-in sheets. They land in a shared Gmail inbox, a Slack channel, or a CRM notification queue. Then they sit — until an agent with time (or hunger) grabs them.

The problem isn't agent motivation. It's that nobody owns the first 60 seconds. Buyers who contact an agent within five minutes are dramatically more likely to convert than buyers who wait an hour. In our experience, brokerages without automated routing average 35–45 minutes from lead arrival to first human contact. The agents who respond fastest aren't always the right agents — they're just the ones who happened to be looking at their phone.

Speed-to-lead dies in the handoff between "lead arrived" and "right agent notified." n8n fixes that handoff without replacing your CRM.

Where Manual Routing Breaks

Before you wire anything, map what actually happens today. At most independent brokerages we work with, the flow looks like this:

1. Lead arrives from a portal (Zillow, Realtor.com) or website form
2. Notification goes to a shared inbox or office admin
3. Admin forwards to an agent — often based on who's available, who asked last, or who covers that zip code in their head
4. Agent enters the lead into the CRM (maybe)
5. Agent calls or texts the buyer (maybe today, maybe tomorrow)

The failure modes are predictable:

• Cherry-picking. Top producers check the inbox constantly. Newer agents get the leftovers — or nothing.
• Duplicate entries. Two agents see the same lead and both create CRM records. Your pipeline reports lie.
• Territory drift. The buyer asked about 90210, but the agent who grabbed it covers 90212. Now you're reassigning mid-conversation.
• After-hours black holes. Portal leads peak evenings and weekends. Your fastest responder is whoever has kids in bed early.

The operations manager knows the fix: round-robin by zip, instant SMS to the on-call agent, auto-create the CRM record, log the timestamp. They've pitched it twice. The broker-owner said "we'll look into it" and bought another ChatGPT license instead.

What Good Routing Looks Like

Good routing isn't complicated. It does four things within 60 seconds of a lead arriving:

1. Normalizes the payload — name, phone, email, source, property interest, zip code
2. Matches an agent — by zip, price band, language, or round-robin within a team
3. Creates the CRM record — one record, one owner, source tagged correctly
4. Notifies the assigned agent — SMS + Slack + CRM task, with a 15-minute escalation if no response

The matching logic should be explicit and written down before you build anything. A typical 25-agent brokerage might use:

• Zip-based assignment for geographic farms
• Round-robin fallback when no zip match exists
• Overflow to the broker or TC when the assigned agent doesn't acknowledge within 15 minutes

Write these rules in a Google Sheet or Notion table first. n8n reads the sheet; you change routing without redeploying code.

Building the Workflow in n8n

This is a 6-node core workflow. Most brokerages connect it to Follow Up Boss, kvCORE, or Sierra Interactive — all have APIs or webhook receivers. The pattern is the same regardless of CRM.

Node 1: Webhook Trigger

Every lead source gets its own webhook URL in n8n. Zillow, your website form (via Typeform or native), and Facebook Lead Ads each POST to a dedicated endpoint. n8n normalizes the different payload shapes into one internal format:

{
  "name": "Sarah Chen",
  "phone": "+13105551234",
  "email": "sarah@example.com",
  "source": "zillow",
  "zip": "90210",
  "message": "Interested in 742 Evergreen Terrace",
  "received_at": "2026-07-31T18:47:00Z"
}

Use n8n's Set node to map each source's field names into this schema. Zillow calls it contactPhone; your website calls it phone_number — same destination field.

Node 2: Routing Lookup

An HTTP Request or Google Sheets node reads your routing table. Match on zip first; if no match, fall back to round-robin. Store the last-assigned agent index in a simple n8n static data store or a cell in the sheet so round-robin rotates fairly.

Return: assigned_agent_id, assigned_agent_phone, assigned_agent_slack_id.

Node 3: Duplicate Check

Before creating anything, query your CRM for an existing contact with the same phone or email. An IF node branches:

• Match found → update the existing record, reassign if the owner is inactive, skip creation
• No match → proceed to create

This single check eliminates most duplicate-entry problems.

Node 4: CRM Create

HTTP Request to your CRM's contact-create endpoint. Tag the source (zillow, website, facebook), set the assigned agent as owner, and add a note with the original message and arrival timestamp.

For Follow Up Boss, that's a POST to /v1/people with the assigned_user_id field. For kvCORE, it's their lead-ingest webhook with agent routing parameters.

Node 5: Agent Notification

Parallel branches from the CRM create:

• Twilio SMS to the assigned agent: "New Zillow lead: Sarah Chen, 90210. Interested in 742 Evergreen Terrace. CRM link: [url]"
• Slack message to the agent's DM or a #leads channel with the same info
• CRM task due in 15 minutes: "Call Sarah Chen — Zillow lead"

Node 6: Escalation Timer

A Wait node pauses 15 minutes, then checks whether the agent logged a call or status change in the CRM. If not, an IF node fires an escalation SMS to the broker or TC: "Lead Sarah Chen uncontacted after 15 min — reassigning to overflow."

The escalation path is what makes this work. Agents learn quickly that ignoring a lead means losing it.

What You Need to Get Started

• n8n: Self-hosted (free) or n8n Cloud at roughly €20/month. Self-hosted keeps lead data on your infrastructure.
• CRM with an API: Follow Up Boss, kvCORE, Sierra Interactive, or BoomTown all work. If your CRM only supports email parsing, n8n can still normalize and forward — but you lose duplicate detection.
• Twilio account: For SMS notifications. Roughly $0.01 per message.
• Routing table: A Google Sheet with columns for zip, agent name, agent CRM ID, agent phone, agent Slack ID.

A typical build takes 4–6 hours including testing edge cases: duplicate phones with different formatting, leads with no zip code, agents on vacation. The routing table is the part you'll update most — keep it somewhere non-technical staff can edit.

What Still Needs a Human

Automation owns the first 60 seconds. It does not:

• Negotiate or qualify. A lead who says "I need to sell by Friday" needs a conversation, not an auto-reply.
• Handle reassignment disputes. When two agents claim the same buyer from an open house, that's a broker decision.
• Replace the follow-up sequence. Routing gets the lead to the right agent instantly. What happens on day 3, 7, and 14 is still your CRM drip — or the next workflow you build.

For 80% of inbound portal and website leads — buyers and sellers who filled out a form and expect a call back — this workflow handles everything between arrival and agent notification.

The Math

A typical 25-agent brokerage generating 150–200 leads per month spends 3–5 hours per week on manual routing, forwarding, and duplicate cleanup. At an ops manager's loaded cost, that's roughly $400–$600 per month in time that produces zero closings.

The workflow infrastructure runs about $30–$50 per month. The ROI isn't the subscription cost — it's the leads your agents actually call within five minutes instead of forty-five.

If you're running a brokerage where leads sit in a shared inbox until someone notices, this is the highest-ROI automation you can build in an afternoon.

Start with a Free Quick Assessment at cloudbeast.io/schedule and we'll map your current lead sources to a routing table. If you already know the gaps and want a scoped build plan, the AI Audit at cloudbeast.io/audit walks through your full intake stack — CRM, portals, and escalation rules — and delivers a prioritized implementation plan.