Block 1 - Azure OpenAI Chat Model
- Type / Role
- @n8n/n8n-nodes-langchain.lmChatAzureOpenAi - lmChatAzureOpenAi
- Config choices
- Version 1
Enrich & qualify leads with Azure OpenAI, Bright Data MCP & HubSpot CRM
Workflow preview
100%
$20/month : Unlimited workflows
2500 executions/month
THE #1 IN WEB SCRAPING
Scrape any website without limits
HOSTINGER 
Early Deal
DISCOUNT 20% Try free
Early DealDISCOUNT 20%
Self-hosted n8n
Unlimited workflows - from $4.99/mo
#1 hub for scraping, AI & automation
6000+ actors - $5 credits/mo
Important notice
This workflow is provided as-is. Please review and test before using in production.
1. Workflow Overview
AI Lead Enricher & Qualifier using Bright Data MCP and Hubspot This workflow automatically enriches inbound leads, evaluates their business fit, updates HubSpot, and alerts the team only when a ...
Best for
- Lead Generation automation workflows
- AI Summarization automation workflows
- advanced n8n builders looking for reusable templates
Tools used
@n8n/n8n-nodes-langchain.lmchatazureopenai, @n8n/n8n-nodes-langchain.mcpclienttool, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.hubspot, n8n-nodes-base.formtrigger, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.if, n8n-nodes-base.slack
Source and attribution
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Sparsh From Automation Jinn.
Original n8n.io source1.1 Workflow description
- Title
- Enrich & qualify leads with Azure OpenAI, Bright Data MCP & HubSpot CRM
- Workflow name
- Enrich & qualify leads with Azure OpenAI, Bright Data MCP & HubSpot CRM
🧠AI Lead Enricher & Qualifier using Bright Data MCP and Hubspot
This workflow automatically enriches inbound leads, evaluates their business fit, updates HubSpot, and alerts the team only when a lead meets qualification criteria. It eliminates manual research and scoring while keeping CRM data clean and complete.
🏗️ What this automation does
| Step | Component | Purpose |
|---|---|---|
| 1 | Form Trigger | Captures a new lead’s Name + Email |
| 2 | AI Lead Enricher Agent | Uses Azure OpenAI + Bright Data MCP to search the public web and fill missing contact + company details |
| 3 | Structured Output Parser | Ensures AI returns clean JSON in a strict schema |
| 4 | Lead Scoring Agent | Calculates a numeric Fit Score (0–100) based on ICP match |
| 5 | IF Logic | Routes the lead based on Fit Score threshold (> 70 = qualified) |
| 6 | HubSpot Actions | Updates/creates Contact & Company with enriched properties |
| 7 | Slack Notification | Sends high-quality leads to the team instantly |
🧩 Data Enriched by AI
The enrichment agent populates the following fields only if validated with high confidence:
Contact
- Job title
- LinkedIn profile
- Country
Company
- Company name
- LinkedIn company page
- Industry
- Number of employees
- Annual revenue
- Description
- Headquarters (country & city)
- Funding raised
If reliable data is not found → field stays "" (no hallucination, no guessing).
🎯 Lead Qualification Strategy
The Fit Score (0–100) evaluates how aligned the lead is with a: > B2B automation / AI / RevOps agency targeting SaaS and tech companies
Score increases for:
- SaaS / tech / B2B service industries
- Mid-size or high-growth teams
- High-responsibility job titles (Founder, COO, Head of Ops, RevOps, CTO)
- Funding raised or traction signals
đź”” Resulting CRM + Team Workflow
| Fit Score | CRM Update | Slack Notification |
|---|---|---|
> (qualified) |
Contact + Company updated | YES — sales alert sent |
≤ 70 (not qualified) |
Contact + Company updated | No notification |
This ensures:
- CRM always stays enriched and structured
- Sales only sees high-potential leads
- No lead is ever dropped or ignored
🌟 Why this automation is powerful
âś” 0 manual research
âś” 0 manual lead scoring
âś” Real-time alerts for high-value leads
âś” Eliminates poor data quality in HubSpot
âś” Works instantly on every form submission
🔧 Ideal use cases
- Agencies generating inbound leads
- SaaS companies with SDR teams
- RevOps teams improving CRM hygiene
- Lead qualification before booking calls
đź“Ś Key Integrations
- Azure OpenAI
- Bright Data MCP
- HubSpot (Contacts & Companies)
- Slack
- n8n Form Trigger
This workflow can run fully autonomously or be extended with:
- Calendly auto-booking for qualified leads
- Sales sequence automation
- CRM lifecycle stage updates
- Forecasting dashboards
1.2 Logical Blocks
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
2. Block-by-Block Analysis
Block 2 - MCP Client
- Type / Role
- @n8n/n8n-nodes-langchain.mcpClientTool - mcpClientTool
- Config choices
- Version 1.2
Block 3 - Structured Output Parser
- Type / Role
- @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
- Config choices
- Version 1.3
Block 4 - Create or update a contact
- Type / Role
- n8n-nodes-base.hubspot - hubspot
- Config choices
- Version 2.2
Block 5 - On form submission
- Type / Role
- n8n-nodes-base.formTrigger - formTrigger
- Config choices
- Version 2.3
Block 6 - Azure OpenAI Chat Model1
- Type / Role
- @n8n/n8n-nodes-langchain.lmChatAzureOpenAi - lmChatAzureOpenAi
- Config choices
- Version 1
Block 7 - Lead Enricher Agent
- Type / Role
- @n8n/n8n-nodes-langchain.agent - agent
- Config choices
- Version 3
Block 8 - Lead Scoring Agent
- Type / Role
- @n8n/n8n-nodes-langchain.agent - agent
- Config choices
- Version 3
Block 9 - If
- Type / Role
- n8n-nodes-base.if - if
- Config choices
- Version 2.2
Block 10 - Send a message
- Type / Role
- n8n-nodes-base.slack - slack
- Config choices
- Version 2.3
Block 11 - Structured Output Parser1
- Type / Role
- @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
- Config choices
- Version 1.3
Block 12 - Create or update a contact1
- Type / Role
- n8n-nodes-base.hubspot - hubspot
- Config choices
- Version 2.2
Block 13 - Update a company2
- Type / Role
- n8n-nodes-base.hubspot - hubspot
- Config choices
- Version 2.2
Block 14 - Search for a company by Domain
- Type / Role
- n8n-nodes-base.hubspot - hubspot
- Config choices
- Version 2.2
Block 15 - Search for a company by Domain1
- Type / Role
- n8n-nodes-base.hubspot - hubspot
- Config choices
- Version 2.2
Block 16 - Update a company
- Type / Role
- n8n-nodes-base.hubspot - hubspot
- Config choices
- Version 2.2
Block 17 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Block 18 - Sticky Note1
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Block 19 - Sticky Note2
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Block 20 - Sticky Note3
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Block 21 - Sticky Note4
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Block 22 - Sticky Note5
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
3. Summary Table
| Workflow | Enrich & qualify leads with Azure OpenAI, Bright Data MCP & HubSpot CRM |
|---|---|
| Complexity | advanced |
| Nodes | 22 |
| Categories | Lead Generation, AI Summarization |
| Author | Sparsh From Automation Jinn |
| Published | 26 Nov 2025 |
4. Reproducing the Workflow from Scratch
-
1. Download the workflow JSON
Use the JSON export at /data/workflows/11258/11258.json as the source template for this automation.
-
2. Import the template into n8n
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
-
3. Configure credentials and variables
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
-
4. Test with sample data
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
-
5. Activate and monitor
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
5. General Notes & Resources
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Frequently asked questions
What does Enrich & qualify leads with Azure OpenAI, Bright Data MCP & HubSpot CRM do?
AI Lead Enricher & Qualifier using Bright Data MCP and Hubspot This workflow automatically enriches inbound leads, evaluates their business fit, updates HubSpot, and alerts the team only when a ...
What do I need before importing this workflow?
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Can I customize this workflow?
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Lead Generation, AI Summarization use case.