January 22, 2026

Gmail + Slack: qualify leads and route them fast

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Leads land in your inbox, you skim them between meetings, and somehow the “good ones” still sit too long. Then the follow-up is late, context gets lost, and the pipeline turns into a guessing game.

This Gmail Slack leads automation hits sales managers first, but agency owners and ops folks feel it too. You get a consistent lead score, clean routing, and a Slack alert that actually tells your team what to do next.

Below, you’ll see how the workflow captures leads from email or forms, uses AI to extract the important details, pushes the record into your CRM, and logs everything to Google Sheets (including failures).

How This Automation Works

See how this solves the problem:

n8n Workflow Template: Gmail + Slack: qualify leads and route them fast

Click to explore

flowchart LR

    subgraph sg0["Email Intake Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "Email Intake Trigger", pos: "b", h: 48 }
        n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Form Intake Webhook"]
        n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/merge.svg' width='40' height='40' /></div><br/>Combine Intake Streams"]
        n3@{ icon: "mdi:swap-vertical", form: "rounded", label: "Workflow Settings", pos: "b", h: 48 }
        n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Input Data Validation"]
        n5@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Validation Gate", pos: "b", h: 48 }
        n6@{ icon: "mdi:robot", form: "rounded", label: "AI Lead Extraction", pos: "b", h: 48 }
        n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Interpret AI Output"]
        n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Lead Scoring Logic"]
        n9@{ icon: "mdi:swap-horizontal", form: "rounded", label: "CRM Routing Switch", pos: "b", h: 48 }
        n10["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/hubspot.svg' width='40' height='40' /></div><br/>Generate HubSpot Contact"]
        n11["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/salesforce.svg' width='40' height='40' /></div><br/>Generate Salesforce Lead"]
        n12["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Slack Channel Notification"]
        n13@{ icon: "mdi:database", form: "rounded", label: "Append Lead to Sheets", pos: "b", h: 48 }
        n14@{ icon: "mdi:swap-vertical", form: "rounded", label: "Prepare Validation Log", pos: "b", h: 48 }
        n15@{ icon: "mdi:database", form: "rounded", label: "Record Failed Leads", pos: "b", h: 48 }
        n2 --> n3
        n0 --> n2
        n12 --> n13
        n5 --> n6
        n5 --> n14
        n7 --> n8
        n9 --> n10
        n9 --> n11
        n4 --> n5
        n8 --> n9
        n10 --> n12
        n11 --> n12
        n14 --> n15
        n3 --> n4
        n1 --> n2
        n6 --> n7
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n0 trigger
    class n6 ai
    class n5,n9 decision
    class n13,n15 database
    class n1 api
    class n4,n7,n8 code
    classDef customIcon fill:none,stroke:none
    class n1,n2,n4,n7,n8,n10,n11,n12 customIcon

The Challenge: inbound leads get missed, misrouted, or mishandled

Inbound leads are “easy” in theory. In reality, they arrive as messy email threads, half-filled form submissions, and vague “can you help?” requests with no budget or context. Someone has to read them, figure out what the person actually needs, decide if they fit your ideal customer profile, and then pick the right owner. Do that manually for a few leads a day and it becomes a constant interruption. Do it at higher volume and you’ll start dropping the ball, because humans are not built to triage a sales inbox all day.

It adds up fast. And the annoying part is how predictable the failure points are.

Leads get “handled” in Slack with no CRM record, so the next person can’t see what happened.
Good-fit prospects wait hours because someone wanted to “read it properly later.”
Routing is inconsistent, which means the wrong rep follows up and the handoff feels sloppy.
When a submission is missing key fields, it quietly fails and nobody knows until it’s too late.

The Fix: AI qualification from Gmail/forms, routed to Slack + CRM

This workflow gives your inbound leads one reliable path from “message received” to “someone owns it.” It starts when a new email hits your Gmail sales inbox or when a web form posts to a webhook. Both sources get merged into the same intake pipeline so you don’t end up maintaining two separate processes. From there, the workflow checks the basics (is there usable text, an email address, the minimum required info). Then OpenAI extracts the details humans normally hunt for: company, role, industry, region, problem statement, and budget signals. That structured data is parsed, scored on a clear 0–100 rubric, and tiered (Hot, Warm, Cold, or Unqualified) before the lead is created in Salesforce or HubSpot and posted to Slack for fast follow-up.

The workflow begins with Gmail or a form webhook, then normalizes the input and validates it. AI handles extraction, a scoring node assigns a tier, and a switch routes the lead to the CRM you’ve selected. Finally, Slack gets a rich summary and Google Sheets gets a clean log (plus a separate DLQ tab for failures).

What Changes: Before vs. After

What This Eliminates

Impact You’ll See

Reading every inbound message just to extract basics like company and role.
Copy-pasting lead details into Salesforce or HubSpot by hand.
Ad-hoc “routing” decisions that change depending on who checked the inbox.
Silent failures when submissions are missing required information.

Most teams get about 1–2 hours back per week for every 20 leads.
Faster first response because Slack gets notified immediately after scoring.
More consistent qualification, so your pipeline looks like a pipeline again.
Cleaner handoffs because the Slack message includes the reasoning and tier.
Better reporting since every lead (and failure) is logged in Google Sheets.

Real-World Impact

Say you get 15 inbound leads a week from Gmail and forms. Manually, it’s easy to spend about 10 minutes per lead just to read, extract details, pick an owner, post a summary in Slack, and then log it somewhere. That’s roughly 2–3 hours a week, and it’s scattered time. With this workflow: the trigger is instant, AI extraction and scoring usually finishes in a minute or two, and your team gets the Slack alert plus a CRM record without the busywork. You still review the best leads, but you’re not doing admin work to get there.

Requirements

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Gmail for polling new inbound lead emails.
Slack to alert your team with lead context.
Google Sheets to log leads and failures.
Salesforce or HubSpot for creating lead/contact records.
OpenAI API key (get it from your OpenAI dashboard).

Skill level: Intermediate. You’ll connect accounts, paste an API key, and tweak a few configuration fields like ICP criteria and Slack channel ID.

Need help implementing this? Talk to an automation expert (free 15-minute consultation).

The Workflow Flow

New lead arrives via Gmail or a form. A Gmail trigger watches your inbox for new inbound messages, while a webhook receives submissions from any online form tool. Both streams feed the same pipeline so you can scale sources without rebuilding the logic.

Basic validation and normalization. The workflow applies your settings (target industries, buyer roles, size ranges) and checks for required fields like email or usable text. If the submission is invalid, it gets routed into a “dead letter queue” log in Google Sheets so you can audit what went wrong.

AI extracts structure from messy text. OpenAI pulls out the fields your team needs to qualify quickly: company name, industry, role, region, problem statement, and budget signals. That output is parsed so downstream tools receive clean data instead of a blob of text.

Scoring, routing, and notifications. A scoring node assigns a 0–100 score and a tier (Hot/Warm/Cold/Unqualified), then a switch routes the lead into Salesforce or HubSpot based on your configuration. Slack receives a rich message summarizing the lead, the score, and why it got that score, and Google Sheets logs the final outcome.

You can easily modify the scoring rubric to match your ICP, then route by territory, service line, or region based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Gmail Trigger

Set up inbound lead intake from both email and form submissions so the workflow can normalize and validate each payload.

Open Email Intake Trigger and confirm the polling schedule (default is every minute). Credential Required: Connect your Gmail credentials.
Open Form Intake Webhook and set the Path to 648db646-76c1-44b4-bab0-5955971721e5, then copy the Test URL for your form integration.
Ensure both Email Intake Trigger and Form Intake Webhook connect into Combine Intake Streams, which feeds into Workflow Settings.

⚠️ Common Pitfall: If your form sender does not match the webhook’s test URL, the Form Intake Webhook won’t receive data—use the Production URL when you activate.

Step 2: Connect Google Sheets

Configure centralized settings and storage destinations to ensure scoring and logging run against the correct configuration.

In Workflow Settings, set targetIndustries to technology,software,saas,fintech,healthcare,manufacturing,retail,ecommerce and update buyerRoles to match your ICP.
Set slackChannel to [YOUR_ID], googleSheetUrl to https://docs.google.com/spreadsheets/d/[YOUR_ID]/edit, and crmSystem to hubspot or salesforce.
Open Append Lead to Sheets and set Document to {{ $('Workflow Settings').first().json.googleSheetUrl }}. Credential Required: Connect your Google Sheets credentials.
Open Record Failed Leads and set Document to {{ $('Workflow Settings').first().json.googleSheetUrl }}. Credential Required: Connect your Google Sheets credentials.

Use separate sheet tabs for qualified leads and validation failures to keep reporting clean. Both Append Lead to Sheets and Record Failed Leads can point to different tabs within the same document.

Step 3: Set Up Processing and AI Extraction

Validate input, extract structured lead data with AI, and enrich it with scoring logic.

In Input Data Validation, keep Mode set to runOnceForEachItem and review the JavaScript rules for required fields and email format.
In Validation Gate, ensure the condition uses {{ $('Input Data Validation').item.json.validation.isValid }} equals true to route valid leads forward.
Configure AI Lead Extraction with Model gpt-4o-mini and confirm JSON Output is enabled. Credential Required: Connect your OpenAI credentials.
Confirm the AI prompt includes the input expression {{ JSON.stringify($json) }} to pass email or form content into the model.
Review Interpret AI Output and Lead Scoring Logic scripts to ensure fields align with your inbound data and desired scoring rubric.

⚠️ Common Pitfall: If the AI response is not valid JSON, Interpret AI Output will throw an error. Keep jsonOutput enabled in AI Lead Extraction to minimize parsing issues.

Step 4: Configure Output and CRM Routing

Route scored leads to the correct CRM, send Slack notifications, and log results.

In CRM Routing Switch, confirm the routing rule compares {{ $('Workflow Settings').first().json.crmSystem }} to hubspot and salesforce.
Open Generate HubSpot Contact and set Email to {{ $json.email }}, with additional fields like firstName {{ $json.firstName }} and companyName {{ $json.companyName }}. Credential Required: Connect your HubSpot credentials.
Open Generate Salesforce Lead and set Company to {{ $json.companyName }} and Last Name to {{ $json.role }}, then map Email to {{ $json.email }}. Credential Required: Connect your Salesforce credentials.
Configure Slack Channel Notification with Channel ID {{ $('Workflow Settings').first().json.slackChannel }} and keep Message Type as block. Credential Required: Connect your Slack credentials.
Ensure Slack Channel Notification outputs to Append Lead to Sheets to record qualified leads after CRM creation.

Slack Channel Notification uses a block payload with dynamic fields like {{ $json.leadScore }}—test with sample data to verify formatting before going live.

Step 5: Configure Validation Failure Logging

Handle invalid inbound leads by logging validation errors to a separate sheet.

From Validation Gate, use the false branch to connect to Prepare Validation Log.
In Prepare Validation Log, keep status set to validation_failed, timestamp to {{ $now.toISO() }}, and errorMessage to {{ $json.validation.errors }}.
Confirm Prepare Validation Log outputs to Record Failed Leads so invalid submissions are captured for review.

Step 6: Test and Activate Your Workflow

Run a full test of both intake methods to validate routing, AI extraction, CRM creation, and logging.

Click Execute Workflow and send a sample email to trigger Email Intake Trigger, then submit a test payload to Form Intake Webhook.
Verify that valid leads pass from Validation Gate to AI Lead Extraction, then into Interpret AI Output and Lead Scoring Logic.
Confirm that CRM Routing Switch sends the lead to either Generate HubSpot Contact or Generate Salesforce Lead, followed by Slack Channel Notification and Append Lead to Sheets.
Test invalid data and verify the false branch routes to Prepare Validation Log and writes to Record Failed Leads.
When successful, toggle the workflow to Active so it runs continuously in production.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Watch Out For

Gmail credentials can expire or need specific permissions. If things break, check your connected account status in n8n Credentials and confirm the trigger can still read the right mailbox/label.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Common Questions

How quickly can I implement this Gmail Slack leads automation?

Usually about an hour if your accounts are ready.

Can non-technical teams implement this lead qualification and routing?

Yes, but someone should be comfortable with connecting accounts and testing a few sample leads. No coding is required unless you want to change the scoring logic in detail.

Is n8n free to use for this Gmail Slack leads workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs, which are usually a few cents per lead depending on the model and prompt size.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

How do I adapt this Gmail Slack leads solution to my specific challenges?

Start in the Workflow Settings node where you define your target industries, buyer roles, company size, and Slack channel. If you want different qualification criteria, adjust the Lead Scoring Logic code node (for example, weight budget signals higher, or downgrade certain industries). You can also swap the CRM branch by changing the CRM Routing Switch so Salesforce is skipped and HubSpot becomes the default.

Why is my Slack connection failing in this workflow?

Most of the time it’s a token or permission issue in your Slack app, especially missing chat:write access to the target channel. Double-check the channel ID, then re-authenticate the Slack credential inside n8n. If you’re sending a high volume of leads at once, Slack rate limits can also cause intermittent failures.

What’s the capacity of this Gmail Slack leads solution?

On n8n Cloud Starter, you can handle a few thousand executions per month, which is plenty for many small teams. If you self-host, executions aren’t capped, so capacity mainly depends on your server and how fast you want OpenAI + CRM calls to run. Practically, most teams run this comfortably at “dozens of leads a day” without touching performance settings. If you expect spikes from campaigns, add basic retry/backoff on the CRM and Slack nodes so one temporary API hiccup doesn’t send leads to the DLQ. Logging to Google Sheets is convenient, but it can become the slowest step at higher volume, so consider batching later if you scale hard.

Is this Gmail Slack leads automation better than using Zapier or Make?

It depends. n8n is a better fit when you want branching logic (Gmail vs webhook), validation paths, and a DLQ log without paying extra for every conditional step. Zapier or Make can be simpler for a basic “email comes in → send Slack message” flow, but they get awkward when you add scoring, CRM switching, and error logging. If you’re unsure, Talk to an automation expert and map it to your lead volume and tools.

This is what “fast follow-up” looks like when it’s systemized. Set it up once, then let your team spend their attention on conversations, not triage.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

{
"id": null,
"meta": {
"instanceId": "daa0333f9738fbc0c418ee8c12e31579a7d5660c90abb220b6985308efbd8827",
"templateId": null,
"templateCredsSetupCompleted": null
},
"name": "Automated Lead Qualification Pipeline",
"tags": [],
"nodes": [
{
"id": "flowpast-topbar-9739",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
10,
45
],
"parameters": {
"color": 7,
"width": 1320,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "87b304de-91b5-45a3-bda0-901812662913",
"name": "Email Intake Trigger",
"type": "n8n-nodes-base.gmailTrigger",
"position": [
995,
145
],
"parameters": {
"filters": [],
"pollTimes": {
"item": [
{
"mode": "everyMinute"
}
]
}
},
"credentials": [],
"typeVersion": 1.3
},
{
"id": "a65a643f-5daa-4a1b-9056-b475d15f088a",
"name": "Form Intake Webhook",
"type": "n8n-nodes-base.webhook",
"position": [
750,
300
],
"webhookId": "648db646-76c1-44b4-bab0-5955971721e5",
"parameters": {
"path": "648db646-76c1-44b4-bab0-5955971721e5",
"options": []
},
"typeVersion": 2.1
},
{
"id": "3bfe7c3d-3ffc-423e-98ac-882115871880",
"name": "Combine Intake Streams",
"type": "n8n-nodes-base.merge",
"position": [
620,
155
],
"parameters": [],
"typeVersion": 3.2
},
{
"id": "a6b72464-b3c4-4737-8205-9695b54def91",
"name": "Workflow Settings",
"type": "n8n-nodes-base.set",
"position": [
375,
195
],
"parameters": {
"options": [],
"assignments": {
"assignments": [
{
"id": "id-1",
"name": "targetIndustries",
"type": "string",
"value": "technology,software,saas,fintech,healthcare,manufacturing,retail,ecommerce"
},
{
"id": "id-2",
"name": "minCompanySize",
"type": "string",
"value": "100"
},
{
"id": "id-3",
"name": "buyerRoles",
"type": "string",
"value": "ceo,cto,cfo,vp,director,head,manager,founder,owner"
},
{
"id": "id-4",
"name": "taskDueHours",
"type": "string",
"value": "24"
},
{
"id": "id-5",
"name": "slackChannel",
"type": "string",
"value": "[YOUR_ID]"
},
{
"id": "id-6",
"name": "googleSheetUrl",
"type": "string",
"value": "https://docs.google.com/spreadsheets/d/[YOUR_ID]/edit"
},
{
"id": "id-7",
"name": "crmSystem",
"type": "string",
"value": "hubspot"
},
{
"id": "id-8",
"name": "note",
"type": "string",
"value": "SETUP REQUIRED: Configure all parameters below with your specific values. This centralizes all workflow settings for easy maintenance."
}
]
},
"includeOtherFields": true
},
"typeVersion": 3.4
},
{
"id": "c27ff33d-3ffa-474b-9ce2-3a691b3099fb",
"name": "Input Data Validation",
"type": "n8n-nodes-base.code",
"position": [
230,
160
],
"parameters": {
"mode": "runOnceForEachItem",
"jsCode": "// Validate input data from email or form submission\nconst item = $input.item.json;\n\n// Initialize validation result\nlet isValid = true;\nlet errors = [];\n\n// Check for required fields\nif (!item.email && !item.text && !item.body && !item.content) {\n  isValid = false;\n  errors.push('Missing required field: email or text content');\n}\n\n// Validate email format if present\nif (item.email) {\n  const emailRegex = /^[^\\s@]+@[^\\s@]+\\.[^\\s@]+$/;\n  if (!emailRegex.test(item.email)) {\n    isValid = false;\n    errors.push('Invalid email format');\n  }\n}\n\n// Check for text content\nconst textContent = item.text || item.body || item.content || '';\nif (textContent.trim().length === 0) {\n  isValid = false;\n  errors.push('Missing text content');\n}\n\n// Return validation result\nreturn {\n  ...item,\n  validation: {\n    isValid: isValid,\n    errors: errors,\n    timestamp: new Date().toISOString()\n  }\n};",
"notice": "Validates incoming data to ensure required fields are present and properly formatted. Invalid data is routed to the failure logging branch."
},
"typeVersion": 2
},
{
"id": "e770dba1-d250-4af5-9286-c11e37b21c92",
"name": "Validation Gate",
"type": "n8n-nodes-base.if",
"position": [
10,
205
],
"parameters": {
"options": [],
"conditions": {
"options": {
"leftValue": "",
"caseSensitive": true,
"typeValidation": "strict"
},
"combinator": "and",
"conditions": [
{
"id": "id-1",
"operator": {
"type": "boolean",
"operation": "equals"
},
"leftValue": "={{ $('Input Data Validation').item.json.validation.isValid }}",
"rightValue": true
}
]
}
},
"typeVersion": 2.2
},
{
"id": "e5414e6c-3e26-4e49-9659-ba5a99034ced",
"name": "AI Lead Extraction",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
25,
410
],
"parameters": {
"modelId": {
"__rl": true,
"mode": "id",
"value": "gpt-4o-mini"
},
"options": [],
"messages": {
"values": [
{
"content": "=Extract lead information from the following input and return a structured JSON object.\n\nRequired fields:\n- firstName: First name of the contact\n- lastName: Last name of the contact  \n- email: Email address\n- phone: Phone number\n- company: Company name\n- jobTitle: Job title or role\n- industry: Industry sector\n- companySize: Number of employees (numeric)\n- country: Country\n- state: State or region\n- city: City\n- budget: Budget information or signals\n- timeline: Purchase timeline or urgency\n- painPoints: Array of pain points or challenges mentioned\n- interests: Array of products/services interested in\n- source: Source of the lead (email or form)\n\nInput data:\n={{ JSON.stringify($json) }}"
}
]
},
"jsonOutput": true
},
"credentials": [],
"typeVersion": 1.8
},
{
"id": "cad2ba36-5c01-45c9-b018-2f6b02a5d0b4",
"name": "Interpret AI Output",
"type": "n8n-nodes-base.code",
"position": [
185,
360
],
"parameters": {
"mode": "runOnceForEachItem",
"jsCode": "// Parse AI Response and extract structured lead data\n// Note: Parses AI response into structured fields for downstream processing\nconst aiResponse = $input.item.json;\n\n// If the AI response is a string, parse it as JSON\nlet leadData;\nif (typeof aiResponse === 'string') {\n  try {\n    leadData = JSON.parse(aiResponse);\n  } catch (error) {\n    // If parsing fails, try to extract JSON from the string\n    const jsonMatch = aiResponse.match(/\\{[\\s\\S]*\\}/);\n    if (jsonMatch) {\n      leadData = JSON.parse(jsonMatch[0]);\n    } else {\n      throw new Error('Unable to parse AI response as JSON');\n    }\n  }\n} else {\n  leadData = aiResponse;\n}\n\n// Extract and structure the lead data fields\nconst structuredLead = {\n  firstName: leadData.firstName || leadData.first_name || '',\n  lastName: leadData.lastName || leadData.last_name || '',\n  email: leadData.email || '',\n  phone: leadData.phone || leadData.phoneNumber || '',\n  company: leadData.company || leadData.companyName || '',\n  jobTitle: leadData.jobTitle || leadData.title || '',\n  industry: leadData.industry || '',\n  companySize: leadData.companySize || leadData.company_size || '',\n  country: leadData.country || leadData.location || '',\n  state: leadData.state || leadData.region || '',\n  city: leadData.city || '',\n  budget: leadData.budget || '',\n  timeline: leadData.timeline || leadData.purchaseTimeline || '',\n  painPoints: leadData.painPoints || leadData.pain_points || [],\n  interests: leadData.interests || leadData.products_interested || [],\n  source: leadData.source || 'unknown',\n  notes: leadData.notes || leadData.additionalInfo || '',\n  rawResponse: aiResponse\n};\n\nreturn structuredLead;"
},
"typeVersion": 2
},
{
"id": "c21948dc-f3c6-45e0-965a-84088865a7af",
"name": "Lead Scoring Logic",
"type": "n8n-nodes-base.code",
"position": [
435,
395
],
"parameters": {
"mode": "runOnceForEachItem",
"jsCode": "// Calculate lead score using transparent rubric (0-100 points)\n// Scores leads 0-100 based on ICP criteria from Workflow Configuration: Industry Match (30pts), Company Size (25pts), Role Match (25pts), Problem Statement (10pts), Budget Signals (10pts). Categorizes as Hot (80+), Warm (60-79), Cold (40-59), or Unqualified (<40).\nconst item = $input.item.json;\n\n// Initialize scoring\nlet score = 0;\nlet breakdown = {};\nlet reasoning = [];\n\n// Target industries for scoring - read from Workflow Configuration\nconst targetIndustries = ($('Workflow Settings').first().json.targetIndustries || '').toLowerCase().split(',').map(i => i.trim());\n\n// Buyer roles that indicate decision-making authority - read from Workflow Configuration\nconst buyerRoles = ($('Workflow Settings').first().json.buyerRoles || '').toLowerCase().split(',').map(r => r.trim());\n\n// Budget signal keywords\nconst budgetSignals = ['budget', 'investment', 'funding', 'purchase', 'buy', 'pricing', 'cost', 'quote', 'proposal'];\n\n// 1. Industry Match (30 points)\nconst industry = (item.industry || '').toLowerCase();\nconst industryMatch = targetIndustries.some(target => industry.includes(target));\nif (industryMatch) {\n  score += 30;\n  breakdown.industry = 30;\n  reasoning.push(`Industry \\\"${item.industry}\\\" matches target industries (+30 points)`);\n} else {\n  breakdown.industry = 0;\n  reasoning.push(`Industry \\\"${item.industry}\\\" does not match target industries (0 points)`);\n}\n\n// 2. Company Size (25 points)\nconst companySize = parseInt(item.companySize || item.company_size || 0);\nif (companySize >= 100) {\n  score += 25;\n  breakdown.companySize = 25;\n  reasoning.push(`Company size ${companySize} meets minimum threshold (+25 points)`);\n} else if (companySize >= 50) {\n  score += 15;\n  breakdown.companySize = 15;\n  reasoning.push(`Company size ${companySize} is moderate (+15 points)`);\n} else if (companySize >= 10) {\n  score += 5;\n  breakdown.companySize = 5;\n  reasoning.push(`Company size ${companySize} is small (+5 points)`);\n} else {\n  breakdown.companySize = 0;\n  reasoning.push(`Company size ${companySize} is below threshold (0 points)`);\n}\n\n// 3. Role Match (25 points)\nconst role = (item.role || item.jobTitle || item.title || '').toLowerCase();\nconst roleMatch = buyerRoles.some(buyerRole => role.includes(buyerRole));\nif (roleMatch) {\n  score += 25;\n  breakdown.role = 25;\n  reasoning.push(`Role \\\"${item.role || item.jobTitle || item.title}\\\" indicates decision-making authority (+25 points)`);\n} else {\n  breakdown.role = 0;\n  reasoning.push(`Role \\\"${item.role || item.jobTitle || item.title}\\\" does not indicate decision-making authority (0 points)`);\n}\n\n// 4. Clear Problem Statement (10 points)\nconst message = (item.message || item.description || item.problem || '').toLowerCase();\nconst hasProblemStatement = message.length > 50 && (message.includes('need') || message.includes('problem') || message.includes('challenge') || message.includes('looking for') || message.includes('help'));\nif (hasProblemStatement) {\n  score += 10;\n  breakdown.problemStatement = 10;\n  reasoning.push('Clear problem statement provided (+10 points)');\n} else {\n  breakdown.problemStatement = 0;\n  reasoning.push('No clear problem statement (0 points)');\n}\n\n// 5. Budget Signals (10 points)\nconst hasBudgetSignals = budgetSignals.some(signal => message.includes(signal));\nif (hasBudgetSignals) {\n  score += 10;\n  breakdown.budgetSignals = 10;\n  reasoning.push('Budget signals detected in message (+10 points)');\n} else {\n  breakdown.budgetSignals = 0;\n  reasoning.push('No budget signals detected (0 points)');\n}\n\n// Determine lead quality tier\nlet tier = '';\nif (score >= 80) {\n  tier = 'Hot Lead';\n} else if (score >= 60) {\n  tier = 'Warm Lead';\n} else if (score >= 40) {\n  tier = 'Cold Lead';\n} else {\n  tier = 'Unqualified';\n}\n\n// Return enriched data with scoring\nreturn {\n  ...item,\n  leadScore: score,\n  leadTier: tier,\n  scoreBreakdown: breakdown,\n  scoreReasoning: reasoning,\n  scoredAt: new Date().toISOString()\n};"
},
"typeVersion": 2
},
{
"id": "44b4da8a-8531-4ade-9a2f-ab36b72ad723",
"name": "CRM Routing Switch",
"type": "n8n-nodes-base.switch",
"position": [
570,
390
],
"parameters": {
"rules": {
"values": [
{
"conditions": {
"options": {
"leftValue": "",
"caseSensitive": true,
"typeValidation": "strict"
},
"combinator": "and",
"conditions": [
{
"operator": {
"type": "string",
"operation": "equals"
},
"leftValue": "={{ $('Workflow Settings').first().json.crmSystem }}",
"rightValue": "hubspot"
}
]
}
},
{
"conditions": {
"options": {
"leftValue": "",
"caseSensitive": true,
"typeValidation": "strict"
},
"combinator": "and",
"conditions": [
{
"operator": {
"type": "string",
"operation": "equals"
},
"leftValue": "={{ $('Workflow Settings').first().json.crmSystem }}",
"rightValue": "salesforce"
}
]
}
}
]
},
"options": {
"fallbackOutput": "extra"
}
},
"typeVersion": 3.3
},
{
"id": "a21e9adb-f9cd-4777-b93b-90d83eebe5de",
"name": "Generate HubSpot Contact",
"type": "n8n-nodes-base.hubspot",
"position": [
840,
305
],
"parameters": {
"email": "={{ $json.email }}",
"options": [],
"additionalFields": {
"firstName": "={{ $json.firstName }}",
"companyName": "={{ $json.companyName }}",
"customPropertiesUi": {
"customPropertiesValues": [
{
"value": "={{ $json.leadScore }}",
"property": "lead_score"
},
{
"value": "={{ $json.region }}",
"property": "region"
}
]
}
}
},
"typeVersion": 2.2
},
{
"id": "5a66f775-7468-4d26-a15e-656ee0bef1b4",
"name": "Generate Salesforce Lead",
"type": "n8n-nodes-base.salesforce",
"position": [
820,
495
],
"parameters": {
"company": "={{ $json.companyName }}",
"lastname": "={{ $json.role }}",
"additionalFields": {
"email": "={{ $json.email }}",
"leadSource": "Web",
"description": "={{ $json.problemStatement }}"
}
},
"typeVersion": 1
},
{
"id": "32f7110b-6959-416c-9d81-97d6cca18c3e",
"name": "Slack Channel Notification",
"type": "n8n-nodes-base.slack",
"position": [
975,
385
],
"webhookId": "bac607da-654f-4b0b-a603-ad5ba3fc6ec7",
"parameters": {
"text": "New lead qualified",
"select": "channel",
"blocksUi": "=[\n  {\n    \"type\": \"section\",\n    \"text\": {\n      \"type\": \"mrkdwn\",\n      \"text\": \"*New Lead Qualified*\\n\\n*Company:* {{ $json.companyName }}\\n*Lead Score:* {{ $json.leadScore }}/100\\n\\n*Score Breakdown:*\\n{{ $json.scoreReasoning }}\\n\\n*Next Best Action:*\\n{{ $json.nextBestAction }}\"\n    }\n  },\n  {\n    \"type\": \"actions\",\n    \"elements\": [\n      {\n        \"type\": \"button\",\n        \"text\": {\n          \"type\": \"plain_text\",\n          \"text\": \"Create intro email\"\n        },\n        \"action_id\": \"create_intro_email\",\n        \"style\": \"primary\"\n      }\n    ]\n  }\n]",
"channelId": {
"__rl": true,
"mode": "id",
"value": "={{ $('Workflow Settings').first().json.slackChannel }}"
},
"messageType": "block",
"otherOptions": []
},
"typeVersion": 2.3
},
{
"id": "a0a91663-c96c-4241-a68d-f23321485bc8",
"name": "Append Lead to Sheets",
"type": "n8n-nodes-base.googleSheets",
"position": [
1230,
370
],
"parameters": {
"operation": "appendOrUpdate",
"sheetName": {
"__rl": true,
"mode": "list",
"value": ""
},
"documentId": {
"__rl": true,
"mode": "url",
"value": "={{ $('Workflow Settings').first().json.googleSheetUrl }}"
}
},
"credentials": [],
"typeVersion": 4.7
},
{
"id": "702156e9-9ea0-4c23-ba93-d0c1fbc7bd0d",
"name": "Prepare Validation Log",
"type": "n8n-nodes-base.set",
"position": [
45,
585
],
"parameters": {
"options": [],
"assignments": {
"assignments": [
{
"id": "id-1",
"name": "status",
"type": "string",
"value": "validation_failed"
},
{
"id": "id-2",
"name": "timestamp",
"type": "string",
"value": "={{ $now.toISO() }}"
},
{
"id": "id-3",
"name": "errorMessage",
"type": "string",
"value": "={{ $json.validation.errors }}"
},
{
"id": "id-4",
"name": "note",
"type": "string",
"value": "Formats validation failure data for logging"
}
]
}
},
"typeVersion": 3.4
},
{
"id": "209c94df-6322-4966-a1f8-a8ceaba25dd4",
"name": "Record Failed Leads",
"type": "n8n-nodes-base.googleSheets",
"position": [
190,
580
],
"parameters": {
"operation": "appendOrUpdate",
"sheetName": {
"__rl": true,
"mode": "list",
"value": ""
},
"documentId": {
"__rl": true,
"mode": "url",
"value": "={{ $('Workflow Settings').first().json.googleSheetUrl }}"
}
},
"credentials": [],
"typeVersion": 4.7
}
],
"active": false,
"pinData": [],
"settings": {
"executionOrder": "v1"
},
"versionId": null,
"connections": {
"Combine Intake Streams": {
"main": [
[
{
"node": "Workflow Settings",
"type": "main",
"index": 0
}
]
]
},
"Email Intake Trigger": {
"main": [
[
{
"node": "Combine Intake Streams",
"type": "main",
"index": 0
}
]
]
},
"Slack Channel Notification": {
"main": [
[
{
"node": "Append Lead to Sheets",
"type": "main",
"index": 0
}
]
]
},
"Validation Gate": {
"main": [
[
{
"node": "AI Lead Extraction",
"type": "main",
"index": 0
}
],
[
{
"node": "Prepare Validation Log",
"type": "main",
"index": 0
}
]
]
},
"Interpret AI Output": {
"main": [
[
{
"node": "Lead Scoring Logic",
"type": "main",
"index": 0
}
]
]
},
"CRM Routing Switch": {
"main": [
[
{
"node": "Generate HubSpot Contact",
"type": "main",
"index": 0
}
],
[
{
"node": "Generate Salesforce Lead",
"type": "main",
"index": 0
}
]
]
},
"Input Data Validation": {
"main": [
[
{
"node": "Validation Gate",
"type": "main",
"index": 0
}
]
]
},
"Lead Scoring Logic": {
"main": [
[
{
"node": "CRM Routing Switch",
"type": "main",
"index": 0
}
]
]
},
"Generate HubSpot Contact": {
"main": [
[
{
"node": "Slack Channel Notification",
"type": "main",
"index": 0
}
]
]
},
"Generate Salesforce Lead": {
"main": [
[
{
"node": "Slack Channel Notification",
"type": "main",
"index": 0
}
]
]
},
"Prepare Validation Log": {
"main": [
[
{
"node": "Record Failed Leads",
"type": "main",
"index": 0
}
]
]
},
"Workflow Settings": {
"main": [
[
{
"node": "Input Data Validation",
"type": "main",
"index": 0
}
]
]
},
"Form Intake Webhook": {
"main": [
[
{
"node": "Combine Intake Streams",
"type": "main",
"index": 1
}
]
]
},
"AI Lead Extraction": {
"main": [
[
{
"node": "Interpret AI Output",
"type": "main",
"index": 0
}
]
]
}
}
}