Back to Catalog

Qualify & enrich leads with GPT-4 and LinkedIn data for intelligent routing

AK PasnoorAK Pasnoor
119 views
2/3/2026
Official Page

AI-Powered Lead Qualification & Enrichment Pipeline

🎯 Who is this for?

This template is perfect for:

  • Marketing Teams looking to automatically qualify inbound leads from campaigns
  • Sales Teams wanting to prioritize high-value prospects instantly
  • Agencies offering lead qualification as a service to clients
  • SaaS Companies routing trial signups to appropriate nurture sequences
  • B2B Service Providers scoring and enriching leads from multiple sources

πŸ’‘ What problem does it solve?

Manual lead qualification is slow, inconsistent, and expensive. Sales teams waste hours on unqualified leads while hot prospects go cold. This workflow:

  • Eliminates manual research - Automatically enriches company data via LinkedIn
  • Scores leads instantly - AI analyzes 15+ data points to score 0-100
  • Routes intelligently - Hot leads get instant alerts, warm leads enter nurture
  • Personalizes outreach - AI generates custom emails based on company context

⚑ What this workflow does

1. Lead Capture & Validation

  • Captures leads via built-in n8n Form (embeddable on any website)
  • Validates email format and detects business vs personal emails
  • Normalizes data from various field naming conventions

2. Company Enrichment via Apify

  • Uses Google Search to find company's LinkedIn profile
  • Scrapes LinkedIn for industry, size, description, specialties, and more
  • Gracefully skips enrichment for personal emails (Gmail, Yahoo, etc.)

3. AI Lead Qualification (GPT-4.1)

  • Scores leads 0-100 based on buying signals
  • Assigns tier: Hot (80+), Warm (60-79), Cold (40-59), Disqualified (<40)
  • Identifies buyer persona (Decision Maker, Influencer, Champion, etc.)
  • Generates personalized talking points and risk factors

4. Intelligent Routing & Actions

  • Hot Leads: Instant Slack alert + AI-generated personalized email + HubSpot contact
  • Warm Leads: Slack notification for nurture sequence
  • Cold Leads: Logged for future reference
  • All Leads: Recorded to Google Sheets with full qualification data

πŸ”§ Setup

Required Credentials

| Service | Purpose | |---------|---------| | OpenAI | AI qualification & email generation | | Apify | Google Search + LinkedIn scraping |

Optional Credentials

| Service | Purpose | |---------|---------| | Slack | Lead alerts and notifications | | HubSpot | CRM contact creation | | Gmail | Sending personalized emails | | Google Sheets | Lead database logging |

Apify Setup

  1. Create account at apify.com
  2. Get API token from Settings β†’ Integrations
  3. Open the Apify HTTP nodes and replace YOUR_API_KEY with the API token obtained in the above step

Apify Actors Used

  • Google Search Scraper PPR (Actor ID: G9PR1B1upfS0mRvp0) - ~$0.004/search
  • LinkedIn Company Scraper PPR (Actor ID: G9y3V8J1hXYJTf1Ho) - ~$0.02/company

Total cost: ~$0.02-0.03 per enriched lead

πŸ“Š Lead Scoring Criteria

| Score | Tier | What it means | |-------|------|---------------| | 80-100 | πŸ”₯ Hot | Strong buying signals, budget confirmed, urgent timeline | | 60-79 | 🌑️ Warm | Good fit, some buying signals, needs nurturing | | 40-59 | ❄️ Cold | Potential fit but unclear intent | | 0-39 | β›” Disqualified | Poor fit, spam, or invalid |

🎨 Customization

Modify Form Fields

Edit the "Lead Capture Form" node to add/remove fields for your use case.

Adjust AI Scoring

Edit the system prompt in "AI Lead Qualification" to customize:

  • Score thresholds for your industry
  • Buyer persona definitions
  • Custom qualification criteria

Add Integrations

Easily extend with:

  • Pipedrive, Salesforce, or other CRMs
  • Email sequences (Mailchimp, ActiveCampaign)
  • SMS notifications (Twilio)
  • Calendar booking (Calendly)

πŸ“ˆ Example Output

{
  "qualification": {
    "score": 85,
    "tier": "Hot",
    "buyerPersona": "Decision Maker",
    "urgencyLevel": "High"
  },
  "insights": {
    "keyInsights": [
      "VP-level with direct budget authority",
      "Company in growth phase (51-200 employees)",
      "Industry aligned with our ICP"
    ],
    "talkingPoints": [
      "Reference their sustainability focus",
      "Highlight ROI for mid-market companies"
    ]
  }
}

πŸ™‹ Need Help?

  • Check the sticky notes in the workflow for section-by-section guidance
  • Ensure Apify credentials are properly configured
  • Test with a business email (not Gmail/Yahoo) to see full enrichment

Created by Agentical AI - AI Automation Agency specializing in workflow automation and AI solutions.

# Qualify & Enrich Leads with GPT-4 and LinkedIn Data for Intelligent Routing

This n8n workflow automates the process of qualifying and enriching leads submitted via a form, leveraging OpenAI's GPT-4 for lead qualification and a custom HTTP request for LinkedIn data. Based on the qualification, it intelligently routes leads to either HubSpot, Slack, or Gmail, ensuring efficient lead management and follow-up.

## What it does

1.  **Triggers on Form Submission**: The workflow starts when a new lead is submitted through an n8n form.
2.  **Qualifies Lead with OpenAI (GPT-4)**: It sends the submitted lead data to OpenAI's GPT-4 model to determine if the lead is "qualified" or "unqualified" based on predefined criteria.
3.  **Enriches Lead with LinkedIn Data**: It makes an HTTP request to an external API (likely a LinkedIn data provider) to enrich the lead with additional information.
4.  **Conditional Routing**:
    *   **Qualified Leads**: If the lead is qualified by GPT-4, it proceeds to add the lead to HubSpot.
    *   **Unqualified Leads**: If the lead is unqualified, it sends a notification to a designated Slack channel and also sends an email via Gmail, potentially for manual review or alternative follow-up.
5.  **Handles Errors**: If any step in the qualification or enrichment process fails, the workflow stops and reports an error.
6.  **Responds to Webhook**: After processing, it sends a response back to the initial form submission.

## Prerequisites/Requirements

*   **n8n Instance**: A running n8n instance.
*   **OpenAI API Key**: For the OpenAI node to qualify leads using GPT-4.
*   **LinkedIn Data Provider API Key/Endpoint**: For the HTTP Request node to enrich leads with LinkedIn data.
*   **HubSpot Account**: Configured credentials for the HubSpot node to add qualified leads.
*   **Slack Account**: Configured credentials for the Slack node to send notifications for unqualified leads.
*   **Gmail Account**: Configured credentials for the Gmail node to send emails for unqualified leads.

## Setup/Usage

1.  **Import the Workflow**: Download the JSON provided and import it into your n8n instance.
2.  **Configure Credentials**:
    *   Set up your **OpenAI API Key** credential for the "OpenAI" node.
    *   Configure the **HTTP Request** node with the appropriate URL, headers (including your API key), and body for your LinkedIn data provider.
    *   Set up your **HubSpot** credential for the "HubSpot" node.
    *   Configure your **Slack** credential for the "Slack" node.
    *   Set up your **Gmail** credential for the "Gmail" node.
3.  **Configure the n8n Form Trigger**:
    *   Activate the "On form submission" node and copy the webhook URL.
    *   Integrate this webhook URL into your lead capture form or system.
4.  **Customize Lead Qualification Logic**:
    *   Review and adjust the prompt in the "OpenAI" node to refine the lead qualification criteria for GPT-4 to match your business needs.
5.  **Customize LinkedIn Data Extraction**:
    *   Adjust the HTTP Request node's parameters (URL, body, headers) to correctly fetch the desired LinkedIn data based on your chosen provider's API documentation.
6.  **Customize Routing Logic**:
    *   Review the "If" node's conditions to ensure leads are routed correctly based on the `isQualified` output from the OpenAI node.
7.  **Customize Notifications and Actions**:
    *   Modify the "HubSpot" node to map the lead data to the correct HubSpot properties.
    *   Adjust the message in the "Slack" node to provide relevant information for unqualified leads.
    *   Customize the email content and recipient in the "Gmail" node for unqualified leads.
8.  **Activate the Workflow**: Once all configurations are complete, activate the workflow.

This workflow provides a robust and intelligent way to automate your lead qualification and routing, saving time and ensuring that leads are handled appropriately based on their quality.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger β€” Manually start the workflow or schedule it to run periodically. Input Setup β€” Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) β€” Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring β€” Clean and convert GPT output into JSON format. Data Storage (Google Sheets) β€” Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the β€œSet Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors β†’ Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection β†’ Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report β†’ Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization β†’ Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs β†’ Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chatβ€”turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. πŸ“‹ What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing πŸ”§ Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation πŸ”‘ Required Credentials OpenAI API Setup Go to platform.openai.com β†’ API keys (sidebar) Click "Create new secret key" β†’ Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai β†’ Dashboard β†’ API Keys Generate a new API key β†’ Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) βš™οΈ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflowβ€”chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content β†’ the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://&lt;your-instance&gt;.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger β†’ Download File From Google Download File From Google β†’ Extract from File β†’ Update File to One Drive Extract from File β†’ Message a model Message a model β†’ Create or update an account Create or update an account β†’ Create an opportunity Create an opportunity β†’ Build SOQL Build SOQL β†’ Query PricebookEntries Query PricebookEntries β†’ Code in JavaScript Code in JavaScript β†’ Create Opportunity Line Items --- Quick setup checklist πŸ” Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. πŸ“‚ IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name β†’ Account upsert fields Invoice code/date/amount β†’ Opportunity fields Product name must equal your Product2.ProductCode in SF. βœ… Test: Drop a sample PDF β†’ verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep β€œReturn only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942