Skip to main content

Enrich seller data with email & domain lookup using Bright Data & Google Search

Workflow preview

Workflow preview
100%
Enrich seller data with email & domain lookup using Bright Data & Google Search preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Email Lookup with Google Search from Postgres Database This N8N workflow is designed to enrich seller data stored in a Postgres database by performing automated Google search lookups . It uses B...

Best for

  • Lead Generation automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.postgres, n8n-nodes-base.wait, n8n-nodes-base.scheduletrigger, n8n-nodes-base.switch, n8n-nodes-base.code, n8n-nodes-base.set, n8n-nodes-base.splitinbatches

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Cyril Nicko Gaspar.

Original n8n.io source

1.1 Workflow description

Title
Enrich seller data with email & domain lookup using Bright Data & Google Search
Workflow name
Enrich seller data with email & domain lookup using Bright Data & Google Search

🔍 Email Lookup with Google Search from Postgres Database

This N8N workflow is designed to enrich seller data stored in a Postgres database by performing automated Google search lookups. It uses Bright Data's Web Unlocker to bypass search result restrictions and the HTML Extract node to parse and extract relevant information from webpages.

The main purpose of this workflow is to discover missing contact details, company domains, and secondary emails for businesses or sellers based on existing database entries.


🎯 Problem This Workflow Solves

Manually searching for missing seller or business details—like secondary emails, websites, or domain names—can be time-consuming and inefficient, especially for large datasets. This workflow automates the search and data enrichment process, significantly reducing manual effort while improving the quality and completeness of your seller database.


✅ Prerequisites

Before using this template, make sure the following requirements are met:

  • ✔️ A Bright Data account with access to the Web Unlocker or Amazon Scraper API
  • ✔️ A valid Bright Data API key
  • ✔️ An active PostgreSQL database with seller data
  • ✔️ N8N self-hosted instance (recommended for using community nodes like n8n-nodes-brightdata)
  • ✔️ Installed n8n-nodes-brightdata package (custom node for Bright Data integration)

⚙️ Setup Instructions

Step 1: Prepare Your Postgres Table

Create a table in Postgres with the following structure (you can adjust field names if needed):

CREATE TABLE sellers (
  seller_id SERIAL PRIMARY KEY,
  seller_name TEXT,
  primary_email TEXT,
  company_info TEXT,
  trade_name TEXT,
  business_address TEXT,
  coc_number TEXT,
  vat_number TEXT,
  commercial_register TEXT,
  secondary_email TEXT,
  domain TEXT,
  seller_slug TEXT,
  source TEXT
);

Step 2: Setup Web Unlocker on Bright Data

  1. Go to your Bright Data dashboard.
  2. Navigate to Proxies & Scraping → Web Unlocker.
  3. Create a new zone, selecting Web Unlocker API under Scraping Solutions.
  4. Whitelist your server IP if required.

Step 3: Generate API Key

  1. In the Bright Data dashboard, go to the API section.
  2. Generate a new API key.
  3. In N8N, create HTTP Request Credentials using Bearer Authentication with the API key.

Step 4: Install the Bright Data Node in N8N

  1. In your N8N self-hosted instance, go to Settings → Community Nodes.
  2. Search and install n8n-nodes-brightdata.

🔄 Workflow Functionality

  • 🔁 Trigger: Can be set to run on a schedule (e.g., daily) or manually.
  • 📥 Read: Fetches seller records from the Postgres table.
  • 🌐 Search: Uses Bright Data to perform a Google search based on seller_name, company_info, or trade_name.
  • 🧾 Extract: Parses the HTML content using the HTML Extract node to identify potential websites and email addresses.
  • 📝 Update: Writes enriched data (like domain or secondary_email) back to the Postgres table.

💡 Use Cases

  • Lead enrichment for e-commerce sellers
  • Domain and contact info discovery for B2B databases
  • Email and web domain verification for CRM systems
  • Market research automation

🛠️ Customization Tips

  • You can enhance the parsing logic in the HTML Extract node to look for phone numbers, LinkedIn profiles, or social media links.
  • Modify the search query logic to include additional parameters like location or industry for more refined results.
  • Integrate additional APIs (e.g., Hunter.io, Clearbit) for email validation or social profile enrichment.
  • Add filtering to skip entries that already have domain or secondary_email.

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 1 - When clicking ‘Test workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 2 - Postgres1

Type / Role
n8n-nodes-base.postgres - postgres
Config choices
Version 2.5

Block 3 - Wait

Type / Role
n8n-nodes-base.wait - wait
Config choices
Version 1.1

Block 4 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 5 - Postgres2

Type / Role
n8n-nodes-base.postgres - postgres
Config choices
Version 2.5

Block 6 - Switch

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.2

Block 7 - Code

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 8 - Postgres3

Type / Role
n8n-nodes-base.postgres - postgres
Config choices
Version 2.5

Block 9 - Switch1

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.2

Block 10 - Postgres4

Type / Role
n8n-nodes-base.postgres - postgres
Config choices
Version 2.5

Block 11 - Wait1

Type / Role
n8n-nodes-base.wait - wait
Config choices
Version 1.1

Block 12 - Edit Fields3

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 13 - Process by Batch

Type / Role
n8n-nodes-base.splitInBatches - splitInBatches
Config choices
Version 3

Block 14 - BrightData

Type / Role
n8n-nodes-brightdata.brightData - brightData
Config choices
Version 1

Block 15 - BrightData1

Type / Role
n8n-nodes-brightdata.brightData - brightData
Config choices
Version 1

Block 16 - HTML

Type / Role
n8n-nodes-base.html - html
Config choices
Version 1.2

Block 17 - HTML1

Type / Role
n8n-nodes-base.html - html
Config choices
Version 1.2

Block 18 - Split Out

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 19 - Filter

Type / Role
n8n-nodes-base.filter - filter
Config choices
Version 2.2

Block 20 - Aggregate

Type / Role
n8n-nodes-base.aggregate - aggregate
Config choices
Version 1

Block 21 - Code2

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 22 - Split Out1

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 23 - Filter1

Type / Role
n8n-nodes-base.filter - filter
Config choices
Version 2.2

Block 24 - If2

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Showing the first 24 of 32 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Enrich seller data with email & domain lookup using Bright Data & Google Search
Complexity advanced
Nodes 32
Categories Lead Generation
Author Cyril Nicko Gaspar
Published 15 May 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/4072/4072.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 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. 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 seller data with email & domain lookup using Bright Data & Google Search do?

Email Lookup with Google Search from Postgres Database This N8N workflow is designed to enrich seller data stored in a Postgres database by performing automated Google search lookups . It uses B...

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 use case.