HumationHuman + Automation
Back to Catalog

Intelligent B2B lead generation workflow using Scrapeless and Claude

scrapeless officialscrapeless official
376 views
2/3/2026
File ManagementGoogle DriveAutomationAttachmentsEmail
Official Page

> ⚠️ Disclaimer: This workflow uses Scrapeless and Claude AI via community nodes, which require n8n self-hosted to work properly.

🔁 How It Works

This intelligent B2B lead generation workflow combines search automation, website crawling, AI analysis, and multi-channel output:

  1. It starts by using Scrapeless’s Deep Serp API to find company websites from targeted Google Search queries.
  2. Each result is then individually crawled using Scrapeless's Crawler module, retrieving key business information from pages like /about, /contact, /services.
  3. The raw web content is processed via a Code node to clean, extract, and prepare structured data.
  4. The cleaned data is passed to Claude Sonnet (Anthropic) which analyzes and qualifies the lead based on content richness, contact data, and relevance.
  5. A filter step ensures only high-quality leads (e.g. lead score ≥ 6) are kept.
  6. Sent via Discord webhook for real-time notification (can be replaced with Slack, email, or CRM tools).

> 📌 The result is a fully automated system that finds, qualifies, and organizes B2B leads with high efficiency and minimal manual input.

✅ Pre-Conditions

Before using this workflow, make sure you have:

  • An n8n self-hosted instance
  • A Scrapeless account and API key (get it here)
  • An Anthropic Claude API key
  • A configured Discord webhook URL (or alternative notification service)

⚙️ Workflow Overview

Manual Trigger → Scrapeless Google Search → Item Lists → Scrapeless Crawler → Code (Data Cleaning) → Claude Sonnet → Code (Response Parser) → Filter → Discord Notification

🔨 Step-by-Step Breakdown

  1. Manual Trigger – For testing purposes (can be replaced with Cron or Webhook)
  2. Scrapeless Google Search – Queries target B2B topics via Scrapeless’s Deep SERP API
  3. Item Lists – Splits search results into individual items
  4. Scrapeless Crawler – Visits each company domain and scrapes structured content
  5. Code Node (Data Cleaner) – Extracts and formats content for LLM input
  6. Claude Sonnet (via HTTP Request) – Evaluates lead quality, relevance, and contact info
  7. Code Node (Parser) – Parses Claude’s JSON response
  8. IF Filter – Filters leads based on score threshold
  9. Discord Webhook – Sends formatted message with company info

🧩 Customization Guidance

You can easily adjust the workflow to match your needs:

  • Lead Criteria: Modify the Claude prompt and scoring logic in the Code node
  • Output Channels: Replace the Discord webhook with Slack, Email, Airtable, or any CRM node
  • Search Topics: Change your query in the Scrapeless SERP node to find leads in different niches or countries
  • Scoring Threshold: Adjust the filter logic (lead_score >= 6) to match your quality tolerance

🧪 How to Use

  1. Insert your Scrapeless and Claude API credentials in the designated nodes
  2. Replace or configure the Discord webhook (or alternative outputs)
  3. Run the workflow manually (or schedule it)
  4. View qualified leads directly in your chosen notification channel

📦 Output Example

Each qualified lead includes:

  • 🏢 Company Name
  • 🌐 Website
  • ✉️ Email(s)
  • 📞 Phone(s)
  • 📍 Location
  • 📈 Lead Score
  • 📝 Summary of relevant content

👥 Ideal Users

This workflow is perfect for:

  • AI SaaS companies targeting mid-market & enterprise leads
  • Marketing agencies looking for B2B-qualified leads
  • Automation consultants building scraping solutions
  • No-code developers working with n8n, Make, Pipedream
  • Sales teams needing enriched prospecting data

Intelligent B2B Lead Generation Workflow using Scrapeless and Claude

This n8n workflow automates the process of generating B2B leads by scraping company websites for specific information and then using an AI agent (powered by Claude) to analyze the extracted data and identify potential leads.

What it does

This workflow performs the following steps:

  1. Manual Trigger: Initiates the workflow when manually executed.
  2. HTTP Request (Scrapeless): Makes an API call to a Scrapeless endpoint, likely to scrape a list of company websites or initial data.
  3. Split Out: Processes the results from the Scrapeless API, splitting them into individual items for further processing. This suggests that the Scrapeless API returns multiple data points (e.g., a list of companies).
  4. Code (Prepare Data): Executes custom JavaScript code to prepare the data for the AI agent. This might involve formatting the scraped data, extracting specific fields, or constructing a prompt for the AI.
  5. AI Agent (Lead Analysis): Utilizes an AI Agent (powered by Langchain) to analyze the prepared data. The agent is configured with an Anthropic Chat Model (Claude) to perform intelligent analysis, likely identifying key characteristics of a lead based on the scraped information.
  6. If (Lead Qualification): Evaluates the output from the AI Agent. This node likely contains logic to qualify whether the analyzed company is a viable lead based on criteria determined by the AI's response.
    • True Branch: If the AI Agent identifies the company as a qualified lead, the workflow would continue down this path (though no subsequent nodes are defined in the provided JSON, implying further actions would be added here, e.g., adding to a CRM, sending a notification).
    • False Branch: If the AI Agent does not qualify the company as a lead, the workflow would continue down this path (similarly, no subsequent nodes are defined, implying actions like logging or discarding the lead).

Prerequisites/Requirements

To use this workflow, you will need:

  • Scrapeless API Key: For the "HTTP Request" node to access web scraping capabilities.
  • Anthropic API Key: For the "Anthropic Chat Model" node to utilize Claude's AI capabilities.
  • n8n Instance: A running n8n instance to import and execute the workflow.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up a credential for your Scrapeless API key in the "HTTP Request" node.
    • Set up a credential for your Anthropic API key in the "Anthropic Chat Model" node.
  3. Review and Customize Nodes:
    • HTTP Request: Adjust the URL and body of the HTTP request to target your specific Scrapeless endpoint and provide the necessary input for scraping.
    • Code: Examine and modify the JavaScript code within the "Code" node to ensure it correctly processes and formats the data for your specific use case and the AI agent's prompt.
    • AI Agent: Review the configuration of the "AI Agent" and "Anthropic Chat Model" to ensure the prompt and model parameters align with your lead qualification criteria.
    • If: Define the conditions in the "If" node to accurately qualify leads based on the AI agent's output.
    • Extend Workflow: Add additional nodes after the "If" node's "True" branch to handle qualified leads (e.g., add to CRM, send email, post to Slack) and after the "False" branch for unqualified leads (e.g., log, discard).
  4. Execute the Workflow: Click the "Execute workflow" button on the "Manual Trigger" node to run the workflow.

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://<your-instance>.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