Skip to main content

Search Google, Bing, Yandex & extract structured results with Bright Data MCP & Google Gemini

Workflow preview

Workflow preview
100%
Search Google, Bing, Yandex & extract structured results with Bright Data MCP & Google Gemini preview
Open on n8n.io

Important notice

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

1. Workflow Overview

Notice Community nodes can only be installed on self hosted instances of n8n. Who this is for? The S...

Best for

  • Market Research automation workflows
  • AI RAG automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-mcp.mcpclient, n8n-nodes-base.function, n8n-nodes-mcp.mcpclienttool, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatgooglegemini, n8n-nodes-base.readwritefile

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Ranjan Dailata.

Original n8n.io source

1.1 Workflow description

Title
Search Google, Bing, Yandex & extract structured results with Bright Data MCP & Google Gemini
Workflow name
Search Google, Bing, Yandex & extract structured results with Bright Data MCP & Google Gemini

Notice

Community nodes can only be installed on self-hosted instances of n8n.

Who this is for?

The Search Engine Intelligence Extractor is a powerful n8n automation that leverages Bright Data’s MCP based AI Agents to simulate human-like searches across Google, Bing, and Yandex, and then distills clean, structured insights using Google Gemini.

This workflow is tailored for:

  • SEO analysts researching competitors or market trends

  • Market researchers needing real-time search visibility

  • Journalists & content writers gathering contextual insights

  • AI developers creating intelligent assistants

  • Digital marketers tracking brand mentions or news

What problem is this workflow solving?

Traditional scraping of search engines is often blocked, cluttered, or filled with irrelevant information. Manually analyzing and cleaning this data for insight is time-consuming.

This workflow solves the problem by:

  • Simulating real user search behavior via Bright Data MCP based AI Agent

  • Performing multi-platform search (Google, Bing, Yandex) in one unified flow

  • Extracting clean, human-readable results (stripping ads, navigation, etc.)

  • Structuring the content using Google Gemini LLM

  • Automating delivery via Webhook or saving to disk

What this workflow does

Input Fields Node:

  • Accepts the search query

  • Accepts action for example - Perform a google search. Replace the action with bing, yandex etc. for other search providers

  • Accepts Webhook notification URL

Bright Data MCP Agent Execution:

  • Triggers Bright Data’s intelligent search agent

  • Handles search navigation, result loading, pagination

Human Readable Data Extractor:

  • Cleanses HTML, removes ads, footers, irrelevant links

  • Produces a readable narrative of results

Final Output Handling:

  • Saves the processed response to disk

  • Sends the structured data to a Webhook for real-time use

Pre-conditions

  1. Knowledge of Model Context Protocol (MCP) is highly essential. Please read this blog post - model-context-protocol
  2. You need to have the Bright Data account and do the necessary setup as mentioned in the Setup section below.
  3. You need to have the Google Gemini API Key. Visit Google AI Studio
  4. You need to install the Bright Data MCP Server @brightdata/mcp
  5. You need to install the n8n-nodes-mcp

Setup

  1. Please make sure to setup n8n locally with MCP Servers by navigating to n8n-nodes-mcp
  2. Please make sure to install the Bright Data MCP Server @brightdata/mcp on your local machine.
  3. Sign up at Bright Data.
  4. Create a Web Unlocker proxy zone called mcp_unlocker on Bright Data control panel.
  5. Navigate to Proxies & Scraping and create a new Web Unlocker zone by selecting Web Unlocker API under Scraping Solutions.
  6. In n8n, configure the Google Gemini(PaLM) Api account with the Google Gemini API key (or access through Vertex AI or proxy).
  7. In n8n, configure the credentials to connect with MCP Client (STDIO) account with the Bright Data MCP Server as shown below.

Make sure to copy the Bright Data API_TOKEN within the Environments textbox above as API_TOKEN=<your-token>

How to customize this workflow to your needs

Add Scheduled Execution

  • Add a Cron trigger to run this workflow on a set schedule (e.g., daily/weekly keyword tracking).

Push Results to Custom Destinations

Connect output to:

  • Google Sheets (for analytics or dashboards)

  • PostgreSQL or MySQL DBs (for structured storage)

  • Notion or Airtable (for content pipelines)

  • Slack or Email (for alerting teams)

Customize Webhook Notifications

  • Update the Webhook URL in the notification node to push processed results to external APIs, CRMs, or real-time dashboards.

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 - Bright Data MCP Client List Tools

Type / Role
n8n-nodes-mcp.mcpClient - mcpClient
Config choices
Version 1

Block 3 - Create a binary data

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

Block 4 - MCP Client for Google Search

Type / Role
n8n-nodes-mcp.mcpClientTool - mcpClientTool
Config choices
Version 1

Block 5 - Set the Input Fields

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

Block 6 - MCP Client for Bing Search

Type / Role
n8n-nodes-mcp.mcpClientTool - mcpClientTool
Config choices
Version 1

Block 7 - MCP Client for Yandex Search

Type / Role
n8n-nodes-mcp.mcpClientTool - mcpClientTool
Config choices
Version 1

Block 8 - Bright Data Search AI Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 2

Block 9 - Google Gemini Chat Model for Search Agent

Type / Role
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - lmChatGoogleGemini
Config choices
Version 1

Block 10 - Write the search result to disk

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

Block 11 - Webhook for clean data extractor

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 12 - Sticky Note2

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

Block 13 - Sticky Note4

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

Block 14 - Sticky Note5

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

Block 15 - Sticky Note3

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

Block 16 - Human Readable Data Extractor

Type / Role
@n8n/n8n-nodes-langchain.informationExtractor - informationExtractor
Config choices
Version 1.1

Block 17 - Google Gemini Chat Model for Human Readable Data Extractor

Type / Role
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - lmChatGoogleGemini
Config choices
Version 1

3. Summary Table

Workflow Search Google, Bing, Yandex & extract structured results with Bright Data MCP & Google Gemini
Complexity advanced
Nodes 17
Categories Market Research, AI RAG
Author Ranjan Dailata
Published 09 Jun 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/4820/4820.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 Search Google, Bing, Yandex & extract structured results with Bright Data MCP & Google Gemini do?

Notice Community nodes can only be installed on self hosted instances of n8n. Who this is for? The S...

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 Market Research, AI RAG use case.