Automate product Hunt lead generation with Apify and Google Sheets
Product Hunt Scraper - Automated Lead Generation Workflow
Turn Product Hunt Launches Into Qualified Leads and Reach out Automatically
Stop manually searching Product Hunt for potential customers. This n8n workflow automatically scrapes the latest products from Product Hunt every day, enriches them with contact details, and delivers organized lead lists straight to your Google Sheets.
What You Get
This powerful automation workflow delivers:
- Daily Lead Generation: Automatically scrapes top 50 Product Hunt products every day at 9 AM
- Weekly Top Performers: Every Monday, captures the top 100 products from the previous week (configurable)
- Rich Contact Data: Extracts emails, Twitter handles, LinkedIn profiles, Discord usernames, phone numbers, and more
- Organized Google Sheets: All leads exported to a structured spreadsheet with product details, maker info, and contact data
- Automated Outreach: Optional email system to reach out to makers with personalized messages
- Fresh Leads Daily: Never miss a new product launch or potential customer
Why This Workflow Is a Game Changer
For Sales & Business Development Teams
- Build a targeted prospect list of innovative companies launching new products
- Reach decision makers directly with founder emails and social profiles
- Beat your competition to newly launched products looking for partnerships or tools
- Scale your outreach without hiring additional SDRs
For SaaS Founders & Indie Hackers
- Find integration partners by identifying products that complement yours
- Discover competitors and track their launches in real time
- Connect with fellow makers for collaboration opportunities
- Source beta testers from engaged Product Hunt communities
For Marketing & PR Agencies
- Identify potential clients who just launched and need marketing support
- Build media lists of active founders for outreach campaigns
- Track industry trends and emerging products in your niche
- Automate lead qualification by capturing product categories and descriptions
For Investors & VCs
- Monitor emerging startups launching on Product Hunt
- Track portfolio company launches and engagement
- Discover investment opportunities in specific categories
- Build deal flow with minimal manual research
Key Features
Intelligent Data Extraction
The workflow captures comprehensive product data:
- Product name, description, and tagline
- Product categories and launch date
- Upvotes and engagement metrics
- Maker information with social profiles
- Website URLs and demo links
- Banner images and screenshots
Multi Channel Contact Discovery
Advanced contact enrichment pulls:
- Primary email addresses (founder emails, sales, feedback, hello)
- Secondary email addresses for CC'ing multiple contacts
- Social media profiles: Twitter, LinkedIn, Discord, Facebook, Instagram
- Communication channels: YouTube, TikTok, Telegram, WhatsApp, Reddit
- Phone numbers (when publicly available)
- Company domains for additional research
Automated Daily Operations
- Set and forget scheduling: Runs automatically every morning at 9 AM
- Smart deduplication: Removes duplicate entries to keep your data clean
- Error handling: Continues processing even if individual products fail
- Webhook driven architecture: Efficiently processes results as they're ready
- Batch processing: Handles large datasets without overwhelming your system
- Gmail integration: Professional email sending via Gmail API for better deliverability
Automated Outreach System
The workflow includes a sophisticated Gmail powered email system that:
- Sends personalized outreach emails to product makers with their product details
- CCs secondary email addresses for better reach
- Professional HTML email templates that are customizable to your brand
- Better deliverability through Gmail API (not SMTP)
- Tracks delivery and engagement through Gmail
- Free to use - 500 emails/day (personal Gmail) or 2,000/day (Workspace)
Email Template Features:
- Dynamic product name and details
- Reference to Product Hunt launch
- Personalized value proposition
- Clear call to action
- Unsubscribe link for compliance
- Your branding and contact info
What's Included
When you purchase this workflow, you get:
- Complete n8n workflow JSON file ready to import
- Detailed technical setup guide with step by step instructions
- Pre configured Apify actors for Product Hunt scraping and contact enrichment
- Email templates for outreach campaigns
Real Results
Cost Effective Lead Generation
Run this workflow for approximately $65 to $95/month and generate:
- 1,900+ leads per month (50 products/day × 30 days + weekly top 100)
- Cost per lead: ~$0.03 to 0.05 which is far cheaper than any lead database
- Fresh, verified contacts that aren't available in purchased lists
- Zero manual work after initial setup
Sign up for Apify: Use our affiliate link or referral code 99h7ds
Technical Highlights
- Built on n8n - the powerful open source automation platform
- Uses Apify actors for reliable scraping at scale
- Google Sheets integration for easy data access and sharing
- Gmail API integration for professional email outreach
- Webhook based architecture for real time processing
- Smart batching to stay within API rate limits
- Modular design making it easily customize which data points to collect
- Error recovery built into every step
- Active testing data pinned for easier debugging
Requirements
To run this workflow, you'll need:
- n8n instance (cloud or self hosted on Railway or Hostinger)
- Apify account (use referral code: 99h7ds - free tier available, paid recommended)
- Google account (for Sheets, Drive and Email integration)
Detailed setup instructions are provided in the Technical Setup guide.
Comparison: DIY vs This Workflow
| Task | Manual Process | With This Workflow | |------|---------------|-------------------| | Find daily products | 30 mins/day checking Product Hunt | Automatic | | Extract contact info | 5 mins per product × 50 = 4+ hours | Automatic | | Organize in spreadsheet | 30 mins/day | Automatic | | Send outreach emails | 3 mins per email × 50 = 2.5 hours | Automatic | | Total time saved | 7+ hours/day | 0 hours | | Monthly cost | Your time + assistant salary | ~$50/month |
Customization Options
This workflow is fully customizable:
- Adjust scraping schedule: Change from daily to twice daily or weekly
- Filter by category: Only scrape products in specific categories (AI, Developer Tools, etc.)
- Modify top N products: Increase/decrease the number of products scraped
- Custom email templates: Edit the outreach message to match your brand
- Add email verification: Integrate ZeroBounce or similar services
- Connect to your CRM: Pipe leads directly to Salesforce, HubSpot, or Pipedrive
- Slack/Discord notifications: Get alerted when new leads are found
Support & Updates
- Lifetime updates: Get all future improvements and bug fixes
- Email support: Questions? We're here to help with setup, Email Us
- Community access: Join our Skool community with other users sharing tips and customizations
- Documentation: Comprehensive guides covering every feature
Get Started Today
Stop losing leads to competitors. Start automatically capturing fresh Product Hunt leads every single day.
→ Purchase Workflow - One time payment, lifetime access
→ View Technical Setup Guide - See what's involved
→ Join Community - Connect with other users
Frequently Asked Questions
Q: Do I need coding skills? A: No! The workflow is pre built and ready to import. Basic n8n familiarity is helpful but not required.
Q: What are the ongoing costs? A: Approximately $65 to $95/month total ($40-60 for Apify scraping services + $20 for n8n cloud, or $0 if you self host on Railway or Hostinger).
Q: Is this legal? A: Yesm all data is publicly available on Product Hunt and product websites. Follow ethical outreach practices.
Q: Can I scrape more/fewer products? A: Absolutely! The workflow is fully customizable. Adjust the "topNProducts" parameter in the config.
Q: What if emails bounce or accounts get banned? A: The guide includes best practices for email deliverability and warnings about sending volume limits.
Q: Can I use this for specific product categories? A: Yes! You can filter by category in the Apify scraper configuration.
Q: Does this work with Gmail? A: Yes! The workflow now uses Gmail API by default for better deliverability and tracking. You can customize it for other providers by using the SMTP node
Ready to automate your lead generation? Get the Product Hunt Scraper workflow today and start building your pipeline on autopilot.
n8n Workflow: Product Hunt Lead Generation and Google Sheets Integration
This n8n workflow demonstrates a basic structure for processing data, applying conditional logic, and interacting with Google Sheets and a generic HTTP API. While the workflow's JSON definition is incomplete for a fully functional lead generation system, it lays the groundwork for such an automation.
What it does
This workflow showcases the following capabilities:
- Receives a Webhook: It starts by listening for incoming data via a webhook, which would typically contain information to be processed.
- Transforms Data: It uses a "Code" node to execute custom JavaScript, allowing for flexible data manipulation and transformation.
- Applies Conditional Logic: An "If" node evaluates conditions on the incoming data, branching the workflow based on whether the condition is true or false.
- Makes HTTP Requests: It includes an "HTTP Request" node, which can be used to interact with external APIs (e.g., to enrich data, trigger other services, or fetch additional information).
- Loops Over Items: A "Loop Over Items (Split in Batches)" node is present, indicating the intention to process multiple items iteratively or in batches.
- Aggregates Data: An "Aggregate" node is included, suggesting that data from multiple sources or iterations might be combined.
- Manages Data in Google Sheets: It interacts with Google Sheets, likely for storing, retrieving, or updating lead information.
- Sends Emails (Gmail): A "Gmail" node is part of the flow, indicating the ability to send email notifications or personalized outreach.
- Includes a Data Table: A "Data table" node is present, which could be used for storing or referencing structured data within the workflow.
- Utilizes a Switch Node: A "Switch" node provides another layer of conditional routing, allowing for multiple output paths based on different criteria.
- Schedules Operations: A "Schedule Trigger" is available, suggesting that parts of the workflow could be set to run at specific intervals.
- Adds Notes: A "Sticky Note" is included for documentation within the workflow itself.
Prerequisites/Requirements
To fully utilize this workflow, you would typically need:
- n8n Instance: A running instance of n8n.
- Google Account: For connecting to Google Sheets and Gmail. You will need to set up Google OAuth credentials in n8n.
- API Keys/Authentication: For any external services you intend to call via the "HTTP Request" node (e.g., Apify for scraping, Product Hunt API, CRM APIs).
- Webhook Source: An external system or application configured to send data to the n8n webhook URL.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Set up your Google Sheets and Gmail credentials within n8n. This typically involves OAuth authentication.
- If the "HTTP Request" node is intended to call a specific API, configure its authentication (e.g., API key, OAuth) as needed.
- Configure Webhook:
- Activate the "Webhook" trigger node. n8n will provide a unique URL.
- Configure your external system to send data to this webhook URL.
- Customize Nodes:
- Code Node: Modify the JavaScript code in the "Code" node (
Node38) to perform the desired data transformations. - If Node: Adjust the conditions in the "If" node (
Node20) to match your specific logic for branching. - HTTP Request Node: Update the URL, method, headers, and body of the "HTTP Request" node (
Node19) to interact with your target API. - Google Sheets Node: Configure the "Google Sheets" node (
Node18) with the correct spreadsheet ID, sheet name, and operation (e.g., "Append Row"). - Gmail Node: Configure the "Gmail" node (
Node356) with recipient, subject, and body for email notifications. - Switch Node: Define the expressions and cases for the "Switch" node (
Node112) to route data based on different values. - Schedule Trigger: If you want the workflow to run on a schedule, configure the "Schedule Trigger" (
Node839) with your desired interval.
- Code Node: Modify the JavaScript code in the "Code" node (
- Activate the Workflow: Once configured, activate the workflow in n8n.
This workflow provides a flexible foundation for building automated processes involving data manipulation, conditional logic, API interactions, and integration with Google services.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
By Ranjan DailataGenerate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
By Daniel NkenchoAutomate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.
By Le Nguyen