# Real Estate Lead Automation Blueprint **Platform:** n8n **Use Case:** Website Lead Processing **Status:** Design Only — Not Deployed ## 1. Business Objective Automatically organize incoming real estate inquiries and route them to the sales team without sending unsolicited customer messages. ## 2. Workflow Architecture ```text Website Form ↓ Webhook Trigger ↓ Validate Input ↓ Check Duplicate Lead ↓ AI Lead Classification ↓ Validate AI Output ↓ Route by Category ↓ Create or Update CRM Record ↓ Notify Sales Team ↓ Record Execution Status ``` ## 3. Node-by-Node Blueprint | Node | Function | |---|---| | Webhook | Receive website form data | | Edit Fields | Normalize incoming fields | | IF | Validate required information | | CRM Lookup | Check for existing leads | | AI Model | Classify property inquiry | | Structured Output Validator | Check classification schema | | Switch | Route buyer, renter, or unclear | | CRM Create/Update | Save lead details | | Notification | Alert assigned sales team | | Error Handler | Record and route failures | The exact CRM and notification nodes depend on the selected applications. ## 4. AI Agent Instructions **Role:** Real Estate Inquiry Classifier Classify the supplied inquiry using only its content. Allowed categories: - buyer - renter - unclear Return JSON with: ```json { "category": "buyer", "reason": "Customer explicitly requests a property purchase", "requires_review": false } ``` Do not infer buying intent solely from budget. Do not invent customer details. Use `unclear` when the inquiry lacks enough information. ## 5. Data Mapping | Source Field | Destination | |---|---| | name | CRM Contact Name | | email | CRM Email | | phone | CRM Phone | | budget | CRM Budget | | property_interest | CRM Interest | | AI category | CRM Inquiry Type | | received_at | CRM Submission Timestamp | ## 6. Decision Logic **IF required contact information is missing:** Route to manual review. **IF a matching CRM lead exists:** Update the existing record according to the CRM's duplicate policy. **IF classification is unclear:** Assign to manual qualification. **IF CRM creation fails:** Log the error and notify the workflow owner. ## 7. Security - Authenticate or otherwise protect the webhook. - Validate all incoming fields. - Store API credentials in the platform's credential manager. - Limit access to customer contact information. - Avoid logging unnecessary personal data. ## 8. Test Cases | Test | Expected Result | |---|---| | Buyer inquiry | Classified as buyer | | Rental inquiry | Classified as renter | | Ambiguous inquiry | Manual review | | Duplicate lead | No unintended duplicate | | Missing email and phone | Validation failure | | CRM unavailable | Error logged and owner notified | | Invalid AI response | Fallback to manual review | ## 9. Deployment Checklist - [ ] Configure webhook - [ ] Verify input schema - [ ] Connect CRM - [ ] Configure AI credentials - [ ] Validate classification output - [ ] Test duplicate detection - [ ] Configure notifications - [ ] Test failure recovery - [ ] Review data access permissions **Final Status:** Architecture prepared. No external systems have been connected or modified.