Block 1 - When clicking ‘Execute 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.
Notice Community nodes can only be installed on self hosted instances of n8n. Who this is for? Thi...
n8n-nodes-base.manualtrigger, n8n-nodes-mcp.mcpclient, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatgooglegemini, n8n-nodes-mcp.mcpclienttool, n8n-nodes-base.function, n8n-nodes-base.readwritefile
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Ranjan Dailata.
Original n8n.io sourceCommunity nodes can only be installed on self-hosted instances of n8n.
This workflow template enables intelligent data extraction from ProductHunt using Bright Data’s Model Context Protocol (MCP) and processes search results with Google Gemini.
This workflow is designed for individuals and teams who need automated, intelligent discovery and analysis of new tech products. It's especially valuable for:
Traditional product discovery on ProductHunt is constrained by limited descriptions and requires repeated manual validation through web searches. Manually extracting and enriching this data is slow, repetitive, and error-prone.
This workflow solves the problem by:
Extracting real-time ProductHunt data using Bright Data’s MCP infrastructure to mimic real-user behavior and avoid blocks.
Performing contextual searches on Google for a specific product on ProductHunt to gather use cases, reviews, and related information.
Structuring results using Google Gemini LLM to provide human-readable insights and reduce noise.
Delivering results seamlessly by saving output to disk, updating Google Sheets, and sending Webhook alerts.
Input Field Node
Define the ProductHunt category with the search term(s) you want to target. This is used to drive extraction and search operations.
Agent Operation Node
The agent performs two major tasks:
Extract from ProductHunt Retrieves trending products from ProductHunt using Bright Data MCP
Contextual Google Search for the product the agent searches Google for deeper context, including:
Reviews
Competitor mentions
Real-world usage examples
LLM Node (Google Gemini)
Analyzes and summarizes extracted web content
Removes noise (ads, menus, etc.)
Structures content into bullet points, insights, or JSON objects
Make sure to copy the Bright Data API_TOKEN within the Environments textbox above as API_TOKEN=<your-token>
This workflow is flexible and modular, allowing you to adapt it for various research, product discovery, or trend analysis use cases. Below are the key customization points and how to modify them.
Define Your Target Products or Topics:
Change the input parameter to a specific ProductHunt category, tag, or keyword (e.g., "AI tools", "SaaS", "DevOps")
Change Output Destinations :
Save to Disk: Change the file format (.json, .csv, .md) or directory path
Google Sheet: Modify sheet name, structure (columns like Product, Summary, Link)
Webhook Notification: Point to a Slack/Discord/CRM/Webhook URL with payload mapping
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.
| Workflow | Extract & search ProductHunt data with Bright Data MCP and Google Gemini AI |
|---|---|
| Complexity | advanced |
| Nodes | 21 |
| Categories | Market Research, AI RAG |
| Author | Ranjan Dailata |
| Published | 09 Jun 2025 |
Use the JSON export at /data/workflows/4823/4823.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.
Notice Community nodes can only be installed on self hosted instances of n8n. Who this is for? Thi...
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 Market Research, AI RAG use case.