New leads come in, property details get verified, the lead is scored, and the CRM is updated without manual work. High value leads get an immediate task and a team alert so sales can follow up fast. This is built for teams that sell services tied to property data.

It starts with a webhook from your CRM. The flow pulls the full lead from the CRM API, checks the address with the BatchData Property Lookup, and runs a scoring function based on value, size, age, lot size, and ownership. The score and status are written back to the CRM. A decision step routes top leads to an urgent follow up task, while standard leads get a Slack notification.

You will need CRM API access, a BatchData API key, and Slack credentials. After mapping fields and tuning the scoring thresholds, you can cut research time and speed up response. This is useful for real estate, home services, and insurance teams that rely on accurate property data to qualify and close deals.

• Webhook intake captures new leads from your CRM in real time.
• HTTP request pulls full lead details from the CRM API using secure headers.
• BatchData property lookup verifies address and returns value, size, age, and ownership.
• Custom scoring code calculates a lead score and sets a clear qualification status.
• CRM update writes score, verification results, and property data back to the lead record.
• Conditional routing sends top leads to an immediate follow up task.
• Slack notification alerts the team about new leads and next steps.
• Configurable thresholds let you adjust point values and cutoffs to match your rules.

• Reduce manual lead research from 30 minutes to 2 minutes
• Improve data quality by verifying property records before contact
• Route high value leads to sales instantly for faster response
• Connect CRM, BatchData, and Slack in one flow
• Handle more leads without adding headcount
• Keep records clean by writing scores and details back to the CRM

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Slack, BatchData and Webhook. See the Tools Required section above for links to create accounts with these services.
3. Open the Webhook trigger node and copy the webhook URL. In your CRM, add a webhook that sends new lead events to this URL. Use the example payload fields leadId, crmApiUrl, address, city, state, and zipcode.
4. Configure CRM credentials: double click the Fetch Lead Data node, choose Credential to connect with, click Create new credential, pick HTTP Header Auth, and add your Authorization header from the CRM. Save.
5. Configure BatchData credentials: double click the BatchData Property Lookup node, choose Credential to connect with, click Create new credential, pick HTTP Header Auth, and add x-api-key with your BatchData API key from the BatchData account API page. Save.
6. Map fields in Fetch Lead Data: confirm the URL uses {{ $json.crmApiUrl }} and {{ $json.leadId }}. Test the node to make sure the CRM returns address details.
7. Review the BatchData request body: confirm address, city, state, and zipcode use incoming values. Run a test to verify you get property value, size, age, and ownership.
8. Open the Score And Qualify Lead code node and adjust point values and thresholds to fit your sales rules. Keep the status labels consistent with your CRM fields.
9. Set up the Update CRM Lead node: ensure the method and URL match your CRM API, and map body fields for score, qualification status, and property attributes. Switch to PATCH if your CRM requires it.
10. Configure routing: in the Is High-Value Lead node, set the condition to match your desired score cutoff for high value leads.
11. Set the Create Immediate Follow-up Task node to your CRM or task system API. Add assignee, priority, due date, and a clear description that includes the lead score.
12. Connect Slack: double click the Send Slack Notification node, create a new Slack credential, and follow the on screen steps to authorize. Set the channel and message format.
13. Validate end to end: send a sample webhook from your CRM, check the n8n execution log, confirm the CRM record updated, see the task creation for high value leads, and verify Slack messages.
14. Troubleshoot common issues: if property data is missing, confirm BatchData API key and input fields. If CRM updates fail, check method, endpoint, and write permissions. If Slack fails, verify channel ID and credential scopes.
15. Enable the workflow in n8n and monitor initial runs. Adjust thresholds and field mappings based on early results.