Product Hunt to Google Sheets, research logged clean
Copying Product Hunt details into a spreadsheet sounds simple. Then you do it 30 times, miss a field, paste the wrong link, and end up “fixing the sheet” instead of actually learning anything.
This Product Hunt Sheets automation hits marketers hardest during launch research, but agency owners building competitor trackers and operators keeping a running tools list feel the same drag. The outcome is straightforward: clean, consistent product fields in your sheet without the tab hopping.
You’ll see how the workflow grabs a Product Hunt page, pulls the data hiding in inline scripts, uses AI to structure it, and returns reliable JSON you can log to Google Sheets or Excel.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Product Hunt to Google Sheets, research logged clean
flowchart LR
subgraph sg0["LLM Script Processor Flow"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Incoming Product Webhook"]
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Retrieve Product Markup"]
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Parse Embedded Scripts"]
n3@{ icon: "mdi:robot", form: "rounded", label: "LLM Script Processor", pos: "b", h: 48 }
n4@{ icon: "mdi:brain", form: "rounded", label: "Gemini Script Review", pos: "b", h: 48 }
n5@{ icon: "mdi:robot", form: "rounded", label: "Structure Product JSON", pos: "b", h: 48 }
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Return JSON Reply"]
n1 --> n2
n2 --> n3
n3 --> n6
n0 --> n1
n5 -.-> n3
n4 -.-> n3
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n3,n5 ai
class n4 aiModel
class n0,n1,n6 api
class n2 code
classDef customIcon fill:none,stroke:none
class n0,n1,n2,n6 customIcon
The Problem: Product Hunt research turns into messy spreadsheets
Market research breaks down in the boring part: collecting consistent data. You open a Product Hunt post, grab the name, tagline, website, makers, topics, maybe the score and comments, then paste it into a sheet. Next product. Next tab. After a while, fields drift. One row has “Website” as the full URL, another has just a domain, another has the Product Hunt post URL in the wrong column. The worst part is you don’t notice until you’re already building a list, writing a summary, or prepping a launch plan.
It adds up fast. Here’s where it breaks down in real life.
- Manual copy-paste across 10+ fields per product creates small errors that ruin filtering later.
- You lose time bouncing between Product Hunt, your sheet, and notes just to capture basics.
- Different people log data differently, which makes “one clean list” basically impossible.
- When Product Hunt pages change, your old scraping bookmarks and quick hacks stop working.
The Solution: turn a Product Hunt slug into structured fields
This workflow gives you a simple input (a product name/slug sent to a webhook) and a dependable output (structured JSON you can write into Google Sheets). It starts when you send a request like ?product=epigram. n8n fetches the Product Hunt page HTML, then extracts the inline scripts that contain the data Product Hunt uses to render the post. Instead of relying on fragile page selectors, the workflow asks an AI model to interpret those scripts and pull out the fields you actually care about. A second AI pass (Gemini) refines the extraction, then everything is formatted to a strict JSON schema so the same columns are filled the same way every time.
The workflow begins with an incoming webhook and an HTTP fetch to Product Hunt. AI then turns “messy embedded data” into consistent fields. Finally, n8n returns a clean JSON response you can map directly into Google Sheets (or pass into another workflow that writes the row).
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you’re building a competitor list of 30 products for a quarterly positioning refresh. Manually, if you spend about 5 minutes per product to open the page, find the right fields, and paste them cleanly, that’s roughly 2.5 hours (and you’ll still have inconsistencies). With this workflow, you submit 30 slugs to the webhook and each one typically returns structured data in about 6 seconds. Even with some waiting and reviewing, most teams get the list done in under 30 minutes.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Product Hunt (public pages) as the research source to extract from.
- Google Sheets to store rows for research lists.
- OpenAI API key (get it from your OpenAI API dashboard)
Skill level: Intermediate. You’ll configure credentials and map JSON fields into your sheet, but you won’t be writing an app.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A webhook receives the product you want. You send a request to your n8n webhook with a simple parameter (for example, the Product Hunt slug). That single input is enough to kick off the entire lookup.
The workflow fetches the Product Hunt page content. n8n builds the right URL and pulls down the raw HTML. No browser automation needed, which keeps it fast and cheap.
Inline scripts are extracted and interpreted. A code step pulls script blocks from the page head, then the AI steps analyze the script data to find the real product fields (name, tagline, makers, scores, topics, URLs, and more). This approach is more resilient when the page layout changes.
Structured JSON is returned for logging. The workflow formats everything into a defined JSON schema and responds back to the caller, which means your Google Sheets mapping stays stable.
You can easily modify the schema fields to match your sheet columns based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Webhook Trigger
Set up the inbound trigger that starts the workflow when a product request is received.
- Add and open Incoming Product Webhook.
- Copy the webhook URL generated by Incoming Product Webhook for your inbound product requests.
- Confirm the execution flow starts with Incoming Product Webhook → Retrieve Product Markup.
Step 2: Connect Product Markup Retrieval
Configure the HTTP request that fetches the product page content for parsing.
- Open Retrieve Product Markup and set the URL and request options for the product page you need to parse.
- Verify Retrieve Product Markup outputs to Parse Embedded Scripts in the workflow canvas.
- Open Parse Embedded Scripts and add code that extracts any embedded script blocks or structured data needed for AI processing.
Step 3: Set Up LLM Processing and Structured Output
Connect the AI model and structured parser to transform extracted scripts into product JSON.
- Open LLM Script Processor and confirm it receives input from Parse Embedded Scripts.
- Open Gemini Script Review and connect it as the language model for LLM Script Processor.
- Open Structure Product JSON and connect it as the output parser for LLM Script Processor.
Credential Required: Connect your Google Gemini credentials in Gemini Script Review.
Credential Required: The parser Structure Product JSON is a sub-node of LLM Script Processor. Add credentials to the parent Gemini Script Review, not the parser itself.
⚠️ Common Pitfall: If Gemini Script Review has no credentials, LLM Script Processor will fail even if the rest of the workflow is configured correctly.
Step 4: Configure the JSON Response Output
Return the structured product data to the original webhook request.
- Open Return JSON Reply and ensure it’s connected directly from LLM Script Processor.
- Map the response body to the structured output generated by LLM Script Processor so the webhook caller receives parsed product JSON.
Step 5: Test and Activate Your Workflow
Validate the end-to-end flow and then enable it for production use.
- Click Test workflow and send a sample request to the Incoming Product Webhook URL.
- Confirm the execution path runs Incoming Product Webhook → Retrieve Product Markup → Parse Embedded Scripts → LLM Script Processor → Return JSON Reply.
- Verify the webhook response returns structured product JSON from Return JSON Reply.
- Toggle the workflow Active to enable it for live requests.
Common Gotchas
- OpenAI credentials can expire or be restricted by project permissions. If things break, check your API key status and usage limits in the OpenAI API dashboard first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 30 minutes if your AI keys and sheet are ready.
No. You’ll mostly connect accounts and paste in API keys. The only “technical” part is mapping JSON fields to columns, which is point-and-click in n8n.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs, which are usually a few cents per run for this kind of extraction.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s honestly the best part. You can extend the structured output by updating the schema in the “Structure Product JSON” step and adjusting the AI extraction prompt in the LLM processing step to include your extra fields. Common add-ons are additional maker profiles, more media links, and normalized categories/topics for cleaner filtering in Google Sheets.
Usually it’s not Product Hunt at all. The HTTP request may be blocked or rate-limited, or your AI step may be erroring because of an invalid API key. Check the “Retrieve Product Markup” node output first, then confirm your OpenAI/Gemini credentials in n8n and rerun a single test product.
A lot, as long as you pace requests. On n8n Cloud, your monthly execution limit depends on your plan; if you self-host, you’re mainly limited by your server and API rate limits. Since each product typically completes in about 6 seconds, many teams batch research runs in chunks (like 20–50 products) and review results as they go.
For this use case, usually yes. Zapier and Make are great for simple “new thing → add a row” workflows, but this one needs HTML fetching, script parsing, and multi-step AI structuring, which is where n8n tends to be more flexible (and more cost-effective at volume). Another practical win is self-hosting, because you can run larger research batches without watching task counters like a hawk. If you want total control over the JSON schema, n8n is the easier place to live. If you’re unsure, Talk to an automation expert and we’ll point you in the right direction.
Clean research rows change everything. Once Product Hunt logging is automatic, you stop maintaining spreadsheets and start using them.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
