🔐 How to Get Your Product Hunt Token
Configured with Function, Google Sheets, HTTP Request, Schedule Trigger. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Transform
- Web / API
- Code
- Data store
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Daily Trigger1 | Trigger | Schedule Trigger | See node parameters |
| Set Date1 | Transform | Edit Fields | See node parameters |
| Fetches today’s Product Hunt posts via API. | Web / API | HTTP Request | POST |
| Extracts Product Info | Code | Code | See node parameters |
| Resolve Website Redirection | Web / API | HTTP Request | See node parameters |
| Data 2 (website url) | Transform | Edit Fields | See node parameters |
| Data 1 (product info) | Transform | Edit Fields | See node parameters |
| Merge Data | Code | Function | See node parameters |
| Appends all details | Data store | Google Sheets | appendOrUpdate |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
🔐 How to Get Your Product Hunt Token
🔐 How to Get Your Product Hunt Token
To get your Product Hunt token, follow the official guide here:
👉 Product Hunt OAuth Token Guide
📄 How to Connect Google Sheets in n8n
📄 How to Connect Google Sheets in n8n
To connect your Google Sheets to n8n:
- Go to your n8n Credentials page.
- Select Google Sheets and add new credentials.
- Authenticate your Google account and give the required permissions.
Follow the full guide here:
👉 https://www.youtube.com/watch?v=pWGXlZBGu4k
About Me
About Me
Hey there! I’m Ajetomobi Ifeoluwa – the brains (and vibe) behind this template. When I’m not crafting cool workflows, I’m busy making the web more beautiful and functional as a UI/UX Designer and Vibe Coder. Want your project to stand out? Let’s chat! Check out my portfolio and my work on Behance. Let’s create something awesome together! 🎨✨
🔐 How to Get Your Product Hunt Token
🔐 How to Get Your Product Hunt Token
Purpose and structure
This folder contains the 🔐 How to Get Your Product Hunt Token workflow. Its executable nodes use code, function, googleSheets, httpRequest, scheduleTrigger, set. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Daily Trigger1
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/0863_Code_Schedule_Import_Webhook.json MIT; preserve source notices.