Real Estate Lead-to-Viewing Desk

From first property enquiry to broker handoff.

A multi-channel real-estate workflow starter for Meta lead forms, WhatsApp enquiries, and an optional voice provider. Qualify stated location, budget, property type, and intent against client-supplied listings; prepare broker-assignment and viewing-request drafts with duplicate and opt-out checks. The supplied reference dashboard is a separate mockup, not a live connected dashboard.

Workflow

1. Receive approved channel payload
2. Normalize stated preferences
3. Look up client inventory
4. Prepare agent-owned viewing request
5. Route drafts for human approval

Operational contract

Trigger

Approved Meta lead-form, WhatsApp Business, or optional client voice-provider event; optional client-owned reviewed follow-up run.

Source data

Consent/source, phone and supplied enquiry, stated location/budget/BHK/property type/intent, client-supplied listing records, broker roster and source-confirmed viewing slots.

Action

Normalize a lead, look up approved client inventory, and prepare a broker assignment or viewing request. Writes, booking confirmation, WhatsApp reply and outbound follow-up require staff approval and authorized APIs.

What to measure

Time from eligible source event to broker review; eligible lead-to-staff-confirmed viewing rate; duplicate/opt-out/exception counts. Do not treat fixture dashboard values as real metrics.

AI + rules

Starter Code nodes validate synthetic data and prepare drafts using explicit rules. Included prompts and JSON schemas guide a separately configured, approved AI classification/extraction step; starter rules are not presented as AI execution.

Human fallback

Missing facts, uncertain answers, unsupported actions, and provider failures go to the named business owner’s review queue.

Logging

The starter returns a workflow name, correlation ID, status, and audit/action draft. Production adapters must persist event/version/owner/timestamps and communication outcomes in the approved source or log store.

Errors & duplicate prevention

Recheck current source status before writes/sends. Use a durable idempotency store keyed to event/record and action; demo flags are not production deduplication. Failed adapters must create an owned exception, not silently retry consequential actions.

Inside your kit

• Inactive, synthetic-data n8n starters for channel parsing, qualification, broker handoff, and follow-up review
• Inventory, booking, broker-routing, and CRM/Sheets data schemas
• Client API checklist for Meta/WhatsApp/voice, inventory, messaging, and notifications
• Setup guide with human approval, opt-out, rate-limit, and durable-dedup rules

Before you connect it

• Client-owned Meta lead access and/or WhatsApp Business API provider credentials stored in n8n
• Documented property inventory/CRM and broker roster; Google Sheets is one optional source, not included
• Optional voice provider (e.g. VAPI/Twilio or a supported client alternative) and approved transfer destination
• Client-approved consent, message templates, provider plans, staff approval, and persistent idempotency store

$399 · One-time configurable workflow kit · Draft test price. Third-party subscriptions, usage, and implementation are separate.

Two-step guide and API checklist · Cart and secure test checkout · Request implementation