Product Hunt insights to Google Sheets + Slack

Launch day feedback is gold. But Product Hunt comments move fast, and the “I’ll summarize these later” plan usually turns into a messy doc, missed patterns, and zero follow-up.

This Product Hunt insights automation hits product marketers first, honestly. Founders feel it too. And if you’re a PM running competitive research between meetings, you already know how quickly “quick research” becomes a time sink.

This workflow scrapes launch comments, has an AI analyst turn them into structured takeaways, logs everything to Google Sheets, and posts a Slack confirmation so you know it’s done. You’ll learn what it fixes, what you need, and how to make it fit your monitoring routine.

How This Automation Works

See how this solves the problem:

n8n Workflow Template: Product Hunt insights to Google Sheets + Slack

Click to explore

flowchart LR

    subgraph sg0["When clicking ‘Execute workflow’ Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Execute workf..", pos: "b", h: 48 }
        n1@{ icon: "mdi:cog", form: "rounded", label: "Run a workflow task", pos: "b", h: 48 }
        n2@{ icon: "mdi:cog", form: "rounded", label: "Get details of a workflow task", pos: "b", h: 48 }
        n3@{ icon: "mdi:robot", form: "rounded", label: "AI Agent", pos: "b", h: 48 }
        n4@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser", pos: "b", h: 48 }
        n5@{ icon: "mdi:database", form: "rounded", label: "Append row in sheet", pos: "b", h: 48 }
        n6@{ icon: "mdi:brain", form: "rounded", label: "Gemini", pos: "b", h: 48 }
        n7["<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/slack.svg' width='40' height='40' /></div><br/>Send a message"]
        n8@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items", pos: "b", h: 48 }
        n9@{ icon: "mdi:database", form: "rounded", label: "Get row(s) in sheet", pos: "b", h: 48 }
        n6 -.-> n3
        n3 --> n5
        n8 --> n7
        n8 --> n1
        n5 --> n8
        n9 --> n8
        n1 --> n2
        n4 -.-> n3
        n2 --> n3
        n0 --> n9
    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 n0 trigger
    class n3,n4 ai
    class n6 aiModel
    class n5,n9 database
    classDef customIcon fill:none,stroke:none
    class n7 customIcon

The Challenge: Turning comment chaos into usable insights

Product Hunt is great at surfacing honest reactions, but it’s brutal as a “system.” Comments are scattered, context gets lost, and the real signal is buried under jokes, feature requests, and one-off opinions. If you try to capture it manually, you end up skimming, copy-pasting, and rewriting the same themes over and over. Then a teammate asks, “So what did people actually say?” and you’re back to scrolling, hoping you didn’t miss the most important critique. It’s exhausting, and it’s exactly the kind of work computers should do.

The friction compounds. Here’s where it breaks down.

Collecting comments by hand usually means 45 minutes per launch, and that’s before you’ve extracted any meaning.
Your notes end up unstructured, so you can’t compare launches side-by-side a week later.
Important negatives slip through because you’re reading quickly and relying on memory.
Teams don’t trust the output, since nobody knows if the summary is complete or current.

The Fix: Scrape Product Hunt feedback and summarize it into Sheets

This workflow turns Product Hunt launch monitoring into a repeatable pipeline. It starts with a list of products you want to track inside Google Sheets. For each product, it kicks off a BrowserAct scraping task to collect the public comments from the Product Hunt launch page, then fetches the completed scrape details once the task is ready. Next, an AI Agent (using a Gemini chat model in this template) reads the raw comments like a competitive intelligence analyst, pulling out a clean summary plus distinct positive feedback, negative feedback, and practical recommendations. That structured analysis gets appended back into Google Sheets so you can sort, filter, and review over time. Finally, Slack receives a confirmation message so the team knows the latest monitoring run actually landed.

The workflow begins by reading your monitoring list from Google Sheets. It loops through each product and scrapes the launch comments via BrowserAct. Then AI converts the messy text into consistent fields, saves a new row to Sheets, and posts a Slack alert when processing finishes.

What Changes: Before vs. After

What This Eliminates

Impact You’ll See

No more copying dozens of comments into docs or Notion.
You don’t have to re-read the whole thread to find recurring themes.
Manual “summary writing” stops being a recurring calendar task.
Slack check-ins like “is the research updated?” disappear.

Most teams get about 30–60 minutes back per launch.
Your insights become searchable and comparable inside Google Sheets.
Positives and negatives show up in consistent buckets, which makes pattern spotting easier.
Recommendations are ready for positioning, sales enablement, or roadmap notes.
Slack confirmation reduces doubt, so teammates actually use the sheet.

Real-World Impact

Say you monitor 5 competitor launches per week. Manually, if you spend about 45 minutes per launch collecting comments and writing a usable summary, that’s close to 4 hours weekly. With this workflow, you update your Google Sheet list once, then run it: a few minutes to trigger and review, plus waiting time while BrowserAct and AI do the heavy lifting. You typically end up with about 3 hours back each week, and the output is cleaner than “notes in a panic.”

Requirements

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Google Sheets for monitoring list and stored insights
Slack to send completion notifications
BrowserAct API key (get it from your BrowserAct dashboard)

Skill level: Intermediate. You’ll connect accounts, add API keys, and test one product end-to-end before scaling the list.

Need help implementing this? Talk to an automation expert (free 15-minute consultation).

The Workflow Flow

A manual run (or scheduled run) kicks things off. In the template it starts manually, but it’s designed to be swapped to a schedule so you can monitor launches continuously without remembering to press anything.

Your Product Hunt watchlist comes from Google Sheets. The workflow reads rows (product names or identifiers) and moves through them in batches, which keeps the process controlled when your list grows.

BrowserAct scrapes the comment thread, then the AI analyst summarizes it. One node launches the scraping task, another fetches the task details, then the AI Agent turns raw text into structured fields like summary, positives, negatives, and recommendations.

Results get appended to Google Sheets, and Slack confirms completion. You end up with a living spreadsheet of launches and insights, and a Slack message that tells you the update finished so nobody has to guess.

You can easily modify the input sheet columns to include Product Hunt URLs (instead of names) based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Manual Trigger

This workflow starts manually, which is useful for testing your Product Hunt feedback analysis before automating it further.

Add the Manual Execution Start node as your trigger.
Optionally keep Flowpast Branding as a sticky note for documentation and internal reference.
Connect Manual Execution Start to Retrieve Sheet Rows.

Step 2: Connect Google Sheets

These nodes load product names from a sheet and store analyzed feedback into a results sheet.

Open Retrieve Sheet Rows and select the spreadsheet by setting Document to [YOUR_ID] and Sheet to [YOUR_ID]. Credential Required: Connect your googleSheetsOAuth2Api credentials.
Open Append Sheet Row and set Operation to append. Credential Required: Connect your googleSheetsOAuth2Api credentials.
In Append Sheet Row, map columns to expressions: Product → {{ $json.output.Product }}, Summary → {{ $json.output.Summary }}, Negative → {{ $json.output.Negative }}, Positive → {{ $json.output.Positive }}, Recomendation → {{ $json.output.Recommendation }}.
Set Document to [YOUR_ID] and Sheet to [YOUR_ID] in Append Sheet Row so results go into the correct sheet.

If your column names differ in Google Sheets, update the Append Sheet Row schema so the mapping matches exactly.

Step 3: Configure BrowserAct Scraping

BrowserAct launches a browser task per product and fetches the completed results.

Open Launch Browser Task and set Workflow ID to [YOUR_ID]. Credential Required: Connect your browserActApi credentials.
Under Input Parameters in Launch Browser Task, set ProductName to {{ $json["Product name"] }} and Total_review to 30.
Enable Save Browser Data by setting it to true in Launch Browser Task.
Open Fetch Task Details and set Operation to getTask, Task ID to {{ $json.id }}, Max Wait Time to =600, and Wait For Finish to true. Credential Required: Connect your browserActApi credentials.

⚠️ Common Pitfall: If Launch Browser Task uses the wrong [YOUR_ID], Fetch Task Details will never return usable results.

Step 4: Set Up the AI Analysis Pipeline

This section analyzes scraped comments and formats them into structured JSON.

In Insight Analysis Agent, set Text to the full analysis prompt and ensure it includes {{ $json.output.string }} as the input payload.
In Insight Analysis Agent, set System Message to You are a competitive intelligence analyst specializing in startup product launches. Your sole task is to analyze raw, unfiltered community comments and extract actionable insights. Do not add any introductory or concluding commentary..
Open Structured JSON Parser and set JSON Schema Example to { "Positive":"<String>", "Negative":"<String>", "Summary":"<String>", "Product":"<String>", "Recommendation":"<String>" }.
Ensure Gemini Chat Model is connected as the language model for Insight Analysis Agent. Credential Required: Connect your googlePalmApi credentials in Gemini Chat Model (not in Structured JSON Parser).

Because Structured JSON Parser is an AI sub-node, it inherits the model settings from Insight Analysis Agent. Add credentials to Gemini Chat Model, not the parser.

Step 5: Configure Iteration and Slack Alerts

Each row is processed in batches, results are saved, and a Slack alert confirms updates.

Keep Iterate Records connected to both Post Slack Alert and Launch Browser Task so each record triggers scraping and notifications.
Iterate Records outputs to both Post Slack Alert and Launch Browser Task in parallel.
Open Post Slack Alert and set Text to The Product Hunt result for has been updated - Positive and negative node analyzed the recommendation added for the product.
Set Channel to [YOUR_ID] and keep Authentication as oAuth2 in Post Slack Alert. Credential Required: Connect your slackOAuth2Api credentials.

⚠️ Common Pitfall: If your Slack channel is not selected via the [YOUR_ID] list, the message will fail even if credentials are correct.

Step 6: Test and Activate Your Workflow

Run a full test to confirm scraping, AI analysis, and logging are all working together.

Click Execute Workflow and confirm Manual Execution Start triggers Retrieve Sheet Rows.
Verify a BrowserAct task is created in Launch Browser Task and completed in Fetch Task Details.
Confirm Insight Analysis Agent outputs a JSON object that matches Structured JSON Parser schema.
Check Google Sheets for a new row created by Append Sheet Row and Slack for a message from Post Slack Alert.
When satisfied, toggle the workflow to Active for production use.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Watch Out For

BrowserAct credentials can expire or need specific permissions. If things break, check your BrowserAct dashboard (API key + template/workflow ID) 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.

Common Questions

How quickly can I implement this Product Hunt insights automation?

About an hour if your accounts and API keys are ready.

Can non-technical teams implement this Product Hunt insights automation?

Yes, but expect a little setup work. You’ll paste in API keys, connect Google Sheets and Slack, then run one test product to confirm the scrape and summary look right.

Is n8n free to use for this Product Hunt insights workflow?

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 BrowserAct usage and your AI model costs (Gemini or OpenAI), which depend on how many launches you process.

Where can I host n8n to run this Product Hunt insights automation?

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.

How do I adapt this Product Hunt insights solution to my specific challenges?

You can adjust the Google Sheets “watchlist” columns to use direct Product Hunt URLs, then pass that into the BrowserAct launch node so it scrapes the exact page you care about. The other big lever is the AI Agent prompt: tweak it to output the fields your team actually uses (for example, “Objections,” “Top requested integrations,” or “Messaging angles”). If you prefer OpenAI instead of Gemini, swap the chat model powering the agent and keep the same structured JSON output. Small change, big difference.

Why is my Google Sheets connection failing in this workflow?

Usually it’s expired Google credentials or the wrong spreadsheet permissions. Reconnect the Google Sheets credential in n8n, then confirm the sheet is shared with the same Google account. Also double-check the document ID and worksheet/tab name, because a renamed tab can look like “missing data.”

What’s the capacity of this Product Hunt insights solution?

If you self-host, capacity mostly comes down to your server and external limits (BrowserAct and the AI model). On n8n Cloud Starter, you can run a few thousand executions per month, which is plenty for weekly monitoring lists. Practically, most teams process a few dozen launches per run without issues, as long as batching and wait time are set sensibly.

Is this Product Hunt insights automation better than using Zapier or Make?

Often, yes. This workflow leans on looping, structured AI output parsing, and a scraping task flow that’s easier to control in n8n than in a two-step automation tool. n8n also gives you a self-hosting path, which matters when you run monitoring jobs frequently and don’t want every extra step metered. Zapier or Make can still work if you keep the scope tiny, but scraping and multi-stage analysis tends to get clunky fast. If you’re unsure, Talk to an automation expert and we’ll sanity-check the best setup for your volume and team.

Once this is running, Product Hunt feedback stops being a one-time scramble and becomes a reliable input to your positioning and roadmap. The workflow does the collecting and summarizing. You make the calls.

Product Hunt insights to Google Sheets + Slack

How This Automation Works

n8n Workflow Template: Product Hunt insights to Google Sheets + Slack

The Challenge: Turning comment chaos into usable insights