Track daily Product Hunt launches with website verification in Google Sheets
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Function (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 9 nodes and runs on a schedule (every day). Along the way it connects Google Sheets. It also calls api.producthunt.com over HTTP.
How it runs
Trigger: On a schedule (every day).
- Set Date (Edit Fields (Set)): sets or maps fields
- Fetches today’s Product Hunt posts via API. (HTTP Request): calls api.producthunt.com (POST)
- Extracts Product Info (Code): runs custom JavaScript code
- Resolve Website Redirection (HTTP Request): calls an HTTP API
- Data 1 (product info) (Edit Fields (Set)): sets or maps fields
- Data 2 (website url) (Edit Fields (Set)): sets or maps fields
- Merge Data (Function): runs custom JavaScript (legacy Function node)
- Appends all details (Google Sheets): append or update
Services it uses
HTTP calls to: api.producthunt.com
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Function (legacy) in Merge Data: replace with Code node, mode 'Run Once for All Items'.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) Merge Data | Code node, mode 'Run Once for All Items' |
Nodes used (6)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - Function
n8n-nodes-base.function - Google Sheets
n8n-nodes-base.googleSheets
From the author
This workflow helps you stay updated with daily launches on Product Hunt. It automatically fetches product details (name, tagline, description, and website), checks if the website redirects to another URL, and logs the final information into a Google Sheet.…