Back to Catalog

AI-powered lead enrichment with Bright Data MCP and Google Sheets

Cyril Nicko GasparCyril Nicko Gaspar
5042 views
2/3/2026
Official Page

📌 HubSpot Lead Enrichment with Bright Data MCP

Screenshot 20250603 at 1.24.49 PM.png

This template enables natural-language-driven automation using Bright Data's MCP tools, triggered directly by new leads in HubSpot. It dynamically extracts and executes the right tool based on lead context—powered by AI and configurable in N8N.


❓ What Problem Does This Solve?

Manual lead enrichment is slow, inconsistent, and drains valuable time. This solution automates the process using a no-code workflow that connects HubSpot, Bright Data MCP, and an AI agent—without requiring scripts or technical skills. Perfect for marketing, sales, and RevOps teams.


🧰 Prerequisites

To use this template, you’ll need:

  • A self-hosted or cloud instance of N8N
  • A Bright Data MCP API token
  • A valid OpenAI API key (or compatible AI model)
  • A HubSpot account
  • Either a Private App token or OAuth credentials for HubSpot
  • Basic familiarity with N8N workflows

⚙️ Setup Instructions

1. Set Up Authentication in HubSpot

🔐 Option 1: Use a Private App Token (Simple Setup)

  1. Log in to your HubSpot account.
  2. Navigate to Settings → Integrations → Private Apps.
  3. Create a new Private App with the following scopes:
    • crm.objects.contacts.read
    • crm.objects.contacts.write
    • crm.schemas.contacts.read
    • crm.objects.companies.read (optional)
  4. Copy the Access Token.
  5. In N8N, create a credential for HubSpot App Token and paste the app token in the field.
  6. Go back to Hubspot Private App settings to setup a webhook.
    • Copy the url in your workflow's Webhook node and paste it here.

🔁 Option 2: Use OAuth (Advanced + Secure)

  1. In HubSpot, go to Settings → Integrations → Apps → Create App.
  2. Set your Redirect URL to match your N8N OAuth2 redirect path.
  3. Choose scopes like:
    • crm.objects.companies.read
    • crm.objects.contacts.read
    • crm.objects.deals.read
    • crm.schemas.companies.read
    • crm.schemas.contacts.read
    • crm.schemas.deals.read
    • crm.objects.contacts.write (conditionally required)
  4. Note the Client ID and Client Secret.
  5. Copy the App ID and the developer API key
  6. In N8N, create a credential for HubSpot Developer API and paste those info from previous step.
  7. Attach these credentials to the HubSpot node in N8N.

2. Setup and obtain API token and other necessary information from Bright Data

In your Bright Data account, obtain the following information:

  • API token
  • Web Unlocker zone name (optional)
  • Browser API username and password string separated by colon (optional)

3. Host SSE server from STDIO command

The methods below will allow you to receive SSE (Server-Sent Events) from Bright Data MCP via a local Supergateway or Smithery


Method 1: Run Supergateway in a separate web service (Recommended)

This method will work for both cloud version and self-hosted N8N.

Signup to any cloud services of your choice (DigitalOcean, Heroku, Hetzner, Render, etc.).

For NPM based installation:
  • Create a new web service.
  • Choose Node.js as runtime environment and setup a custom server without repository.
  • In your server’s settings to define environment variables or .env file, add: API_TOKEN=your_brightdata_api_token WEB_UNLOCKER_ZONE=optional_zone_name BROWSER_AUTH=optional_browser_auth
  • Paste the following text as a start command: npx -y supergateway --stdio "npx -y @brightdata/mcp" --port 8000 --baseUrl http://localhost:8000 --ssePath /sse --messagePath /message
  • Deploy it and copy the web server URL, then append /sse into it.
  • Your SSE server should now be accessible at: https://your_server_url/sse
For Docker based installation:
  • Create a new web service.
  • Choose Docker as the runtime environment.
  • Set up your Docker environment by pulling the necessary images or creating a custom Dockerfile.
  • In your server’s settings to define environment variables or .env file, add: API_TOKEN=your_brightdata_api_token WEB_UNLOCKER_ZONE=optional_zone_name BROWSER_ZONE=optional_browser_zone_name - Use the following Docker command to run Supergateway: docker run -it --rm -p 8000:8000 supercorp/supergateway \ --stdio "npx -y @brightdata/mcp /" \ --port 8000
  • Deploy it and copy the web server URL, then append /sse into it.
  • Your SSE server should now be accessible at: https://your_server_url/sse

For more installation guides, please refer to https://github.com/supercorp-ai/supergateway.git.


Method 2: Run Supergateway in the same web service as the N8N instance

This method will only work for self-hosted N8N.

a. Set Required Environment Variables

In your server's settings to define environment variables or .env file, add:

API_TOKEN=your_brightdata_api_token
WEB_UNLOCKER_ZONE=optional_zone_name
BROWSER_ZONE=optional_browser_zone_name
b. Run Supergateway in Background
npx -y supergateway --stdio "npx -y @brightdata/mcp" --port 8000 --baseUrl http://localhost:8000 --ssePath /sse --messagePath /message

Use the command above to execute it through the cloud shell or set it as a pre-deploy command.

Your SSE server should now be accessible at:
http://localhost:8000/sse

For more installation guides, please refer to https://github.com/supercorp-ai/supergateway.git.


Method 3: Configure via Smithery.ai (Easiest) If you don't want additional setup and want to test it right away, follow these instructions:

Visit https://smithery.ai/server/@luminati-io/brightdata-mcp/tools to:

  • Signup (if you are new to Smithery)
  • Create an API key
  • Define environment variables via a profile
  • Retrieve your SSE server HTTP URL

4. Connect Google Sheets to N8N

  • Ensure your Google Sheet:

    • Contains columns like row_id, first_name, last_name, email, and status.
    • Is shared with your N8N service account (or connected via OAuth)
  • In N8N:

    • Add a Google Sheets Trigger node
    • Set it to watch for new rows in your lead sheet

5. Import and Configure the N8N Workflow

  • Import the provided JSON workflow into N8N
  • Update nodes with your credentials:
    • Hubspot: Add your API key or connect it via OAuth.
    • Google Sheets Trigger: Link to your actual sheet
    • OpenAI Node: Add your API key
    • Bright Data Tool Execution: Add Bright Data token and SSE URL

🔄 How It Works

  • New contact in Hubspot or a new row is added to the Google Sheet
  • N8N triggers the workflow
  • AI agent classifies the task (e.g., “Find LinkedIn”, “Get company info”)
  • The relevant MCP tool is called
  • Results are appended back to the sheet or routed to another destination
  • Rerun the specific record by specifying status "needs more enrichment", or leaving it blank.

🧩 Use Cases

  • B2B Lead Enrichment – Add missing fields (title, domain, social profiles)
  • Email Intelligence – Validate and enrich based on email
  • Market Research – Pull company or contact data on demand
  • CRM Auto-fill – Push enriched leads to tools like HubSpot or Salesforce

🛠️ Customization

  • Prompt Tuning – Adjust how the AI interprets input data
  • Column Mapping – Customize which fields to pull from the sheet
  • Tool Logic – Add retries, fallback tools, or confidence-based routing
  • Destination Output – Integrate with CRMs, Slack, or webhook endpoints

✅ Summary

This template turns a Google Sheet into an AI-powered lead enrichment engine. By combining Bright Data’s tools with a natural language AI agent, your team can automate repetitive tasks and scale lead ops—without writing code.

Just add a row, and let the workflow do the rest.

AI-Powered Lead Enrichment with Bright Data, MCP, and Google Sheets

This n8n workflow automates the process of enriching leads by leveraging AI and data extraction services, then storing the enriched data in Google Sheets and HubSpot. It's designed to streamline lead generation and qualification, providing valuable insights for sales and marketing teams.

What it does

This workflow performs the following steps:

  1. Triggers on new Google Sheet rows: It starts when a new row is added to a specified Google Sheet, acting as the initial source of lead data.
  2. Initial Lead Data Processing: It processes the incoming lead data from Google Sheets.
  3. AI Agent for Lead Enrichment: An AI Agent (likely powered by OpenAI) is invoked to perform lead enrichment tasks. This agent uses a structured output parser to ensure the output is in a defined format.
  4. Bright Data Integration (MCP Client Tool): The AI Agent utilizes the "MCP Client Tool" (Model Context Protocol) which is likely configured to interact with Bright Data for web scraping or data extraction, providing real-time information about the leads.
  5. Output Parsing: The output from the AI agent is parsed, potentially correcting any formatting issues with an "Auto-fixing Output Parser" and then structuring it with a "Structured Output Parser."
  6. Data Transformation: The enriched data is then transformed and set into a desired format using the "Edit Fields (Set)" node.
  7. Conditional Logic (Future Expansion): A "Switch" node is present, suggesting potential for branching logic based on the enriched data (e.g., qualifying leads, assigning to different sales funnels). Currently, it defaults to a "No Operation" node.
  8. HubSpot Integration: The enriched lead data is then sent to HubSpot, likely creating or updating contact records.
  9. Google Sheets Update: Finally, the enriched data is written back to Google Sheets, updating the original spreadsheet with the new information.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: With a spreadsheet containing your initial lead data.
  • Google Sheets Credential: Configured in n8n to access your spreadsheet.
  • OpenAI API Key: For the AI Agent and OpenAI Chat Model.
  • Bright Data Account: And corresponding API access or configuration for the MCP Client Tool.
  • HubSpot Account: To store and manage your enriched leads.
  • HubSpot Credential: Configured in n8n.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Google Sheets credential.
    • Set up your OpenAI API key credential.
    • Set up your HubSpot credential.
    • Ensure the MCP Client Tool is configured to connect to Bright Data with the necessary authentication.
  3. Google Sheets Trigger:
    • In the "Google Sheets Trigger" node, select your Google Sheets credential.
    • Specify the Spreadsheet ID and Sheet Name where your initial lead data resides.
  4. HubSpot Node:
    • In the "HubSpot" node, select your HubSpot credential.
    • Configure the operation (e.g., "Create or Update Contact") and map the fields from the enriched data to your HubSpot contact properties.
  5. AI Agent and OpenAI Chat Model:
    • Ensure your OpenAI API key is correctly configured for the "OpenAI Chat Model" node.
    • Review the prompts and configurations within the "AI Agent" node to ensure it performs the desired enrichment tasks.
  6. Activate the Workflow: Once all credentials and node settings are configured, activate the workflow. It will now automatically trigger when new rows are added to your specified Google Sheet.

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 Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247