Block 1 - When clicking ‘Test workflow’
- Type / Role
- n8n-nodes-base.manualTrigger - manualTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
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...
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
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Cyril Nicko Gaspar.
Original n8n.io sourceThis 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.
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.
Before using this template, make sure the following requirements are met:
n8n-nodes-brightdata)n8n-nodes-brightdata package (custom node for Bright Data integration)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
);
n8n-nodes-brightdata.seller_name, company_info, or trade_name.domain or secondary_email) back to the Postgres table.location or industry for more refined results.domain or secondary_email.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.
Showing the first 24 of 32 workflow blocks. Download the JSON for the full node graph.
| 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 |
Use the JSON export at /data/workflows/4072/4072.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
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...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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.