← All N8N workflows
Messaging & emailCodeHTTP RequestIfSlackWebhook

Lead Qualification with BatchData

Configured with HTTP Request, Slack, Webhook. Review the connections and setup before adapting this template.

Workflow preview
TriggerCRM New Lead WebhookWebhookWeb / APIFetch Lead DataHTTP RequestWeb / APIBatchData PropertyLookupHTTP RequestCodeScore And Qualify LeadCodeWeb / APIUpdate CRM LeadHTTP RequestRoutingIs High-Value Lead?IfWeb / APICreate ImmediateFollow-up TaskHTTP RequestMessagingSend Slack NotificationSlack

Node categories in this workflow

  • Trigger
  • Web / API
  • Code
  • Routing
  • Messaging

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
CRM New Lead WebhookTriggerWebhookSee node parameters
Fetch Lead DataWeb / APIHTTP RequestSee node parameters
BatchData Property LookupWeb / APIHTTP RequestSee node parameters
Score And Qualify LeadCodeCodeSee node parameters
Update CRM LeadWeb / APIHTTP RequestPUT
Is High-Value Lead?RoutingIfSee node parameters
Create Immediate Follow-up TaskWeb / APIHTTP RequestPOST
Send Slack NotificationMessagingSlackSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

None declared. HTTP requests and Code nodes may still need configuration.

Workflow notes

WEBHOOK SETUP INSTRUCTIONS

WEBHOOK SETUP INSTRUCTIONS

  1. Copy this webhook URL and configure your CRM to send notifications here
  2. Expected payload format:
    {
      "leadId": "123",
      "crmApiUrl": "https://your-crm-api.com/api/v1",
      "address": "123 Main St",
      "city": "Anytown",
      "state": "CA",
      "zipcode": "90210"
    }
    
  3. All fields are required for property verification
CRM API CONFIGURATION

CRM API CONFIGURATION

  1. Create HTTP Header Auth credentials for your CRM API
  2. Include necessary authorization headers (e.g., 'Authorization: Bearer YOUR_TOKEN')
  3. This node fetches comprehensive lead data using the lead ID from the webhook
  4. Ensure your CRM API returns address information needed for property verification
BATCHDATA API SETUP

BATCHDATA API SETUP

  1. Create an account at BatchData.com to get your API key
  2. Set up HTTP Header Auth credentials with 'x-api-key: YOUR_BATCHDATA_API_KEY'
  3. This API call verifies property details using the lead's address
  4. Expected response includes property value, size, age, and ownership status
  5. Adjust API endpoint if needed based on BatchData's documentation
LEAD SCORING ALGORITHM

LEAD SCORING ALGORITHM

This function implements a sophisticated scoring system for property-based leads:

SCORING FACTORS

  • Property Value

    • $750k: 30 points

    • $500k: 20 points

    • $350k: 10 points

  • Square Footage

    • 3000 sq ft: 15 points

    • 2000 sq ft: 10 points

  • Property Age

    • <5 years old: 15 points
    • <20 years old: 10 points
  • Other Factors

    • Investment property: 15 points
    • Large lot (>0.5 acres): 10 points

QUALIFICATION THRESHOLDS

  • High-value: 50+ points
  • Qualified: 30-49 points
  • Potential: 15-29 points
  • Not qualified: <15 points
  • Unverified: No property data

Customize the scoring values and thresholds to match your specific business requirements.

CRM UPDATE CONFIGURATION

CRM UPDATE CONFIGURATION

  1. This node updates your CRM with enriched property data and lead qualification information
  2. Adjust field names in the body parameters to match your CRM's API schema
  3. Common fields to update include:
    • Lead score and qualification status
    • Property details (value, size, beds/baths)
    • Verification status
  4. If your CRM uses PATCH instead of PUT, adjust the method accordingly
  5. Make sure your CRM credentials have write access to update lead records
ROUTING LOGIC

ROUTING LOGIC

This conditional node determines the workflow path based on the lead's qualification:

  • TRUE Path (Top): Routes high-value leads for immediate follow-up
  • FALSE Path (Bottom): Routes standard leads for notification only

You can modify the condition to create different paths based on:

  • Score thresholds (e.g., >30 points)
  • Property characteristics (e.g., property value >$1M)
  • Geographic targeting (e.g., specific ZIP codes)
  • Lead source (e.g., referrals vs. web leads)
HIGH-VALUE LEAD HANDLING

HIGH-VALUE LEAD HANDLING

  1. This node creates an urgent follow-up task for premium leads
  2. Customize parameters to match your CRM/task system's API:
    • Assignee (currently "senior-agent")
    • Priority level and task type
    • Due date format
    • Task description
  3. Alternative approaches:
    • Send email alerts to sales managers
    • Create Salesforce opportunities
    • Trigger SMS notifications
    • Add to special follow-up campaign
NOTIFICATION CONFIGURATION

NOTIFICATION CONFIGURATION

  1. Set up Slack credentials in n8n's Credentials Manager
  2. Update the channel ID to match your Slack workspace
  3. Customize the notification format and content
  4. Alternative options:
    • Replace with Email notification
    • Use Microsoft Teams
    • Send SMS alerts via Twilio
    • Post to a dedicated dashboard
    • Log to monitoring system
BatchData Lead Qualification Workflow

BatchData Lead Qualification Workflow

This workflow integrates with BatchData's Property Lookup API to verify, enrich, and qualify leads based on property data. When a new lead is added to your CRM, the workflow:

  1. Retrieves the lead's address information
  2. Verifies property details using BatchData's API
  3. Scores and qualifies the lead based on property characteristics
  4. Updates the CRM with enriched data and qualification status
  5. Routes high-value leads for immediate follow-up

SETUP CHECKLIST

  • [ ] Configure CRM API credentials
  • [ ] Set up BatchData API key
  • [ ] Configure Slack/notification credentials
  • [ ] Customize scoring thresholds
  • [ ] Adjust CRM field mappings
  • [ ] Test with sample lead data
Lead Qualification with BatchData

Lead Qualification with BatchData

Purpose and structure

This folder contains the Lead Qualification with BatchData workflow. Its executable nodes use code, httpRequest, if, slack, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

CRM New Lead Webhook

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/1910_Code_Webhook_Automation_Webhook.json MIT; preserve source notices.

More in Messaging & email