Product Hunt Launch & Maker Lead Scraper

Extract Product Hunt launches, makers, hunters, websites, social links, upvotes, comments, reviews, and lead scoring fields for startup research and outreach.

Best for

• Sales teams looking for newly launched SaaS and AI startup leads
• Investors and scouts monitoring launch traction by day or category
• Market researchers comparing products, makers, comments, and launch history
• Newsletter or content teams building Product Hunt launch roundups

Quick start

For a fast, low-risk daily leaderboard run:

{
    "startUrls": "https://www.producthunt.com/leaderboard/daily/2025/1/15/all",
    "getDetails": false,
    "maxResults": 25,
    "timeoutSecs": 600,
    "useApifyProxy": true
}

For enriched lead generation, keep the volume smaller because detail pages add maker, hunter, comment, review, website, and social extraction:

{
    "startDate": "2025-01-15",
    "endDate": "2025-01-15",
    "getDetails": true,
    "maxResults": 5,
    "maxCommentPages": 1,
    "maxConcurrency": 2,
    "timeoutSecs": 900,
    "useApifyProxy": true
}

If startUrls, startDate, and endDate are empty, the Actor defaults to the previous daily leaderboard.

Common workflows

• Daily startup lead list: scrape yesterday's leaderboard, sort by leadScore, then export companyWebsite, websiteDomain, makers, and hunter.
• Competitor launch tracking: run date ranges and compare upvotes, position, comments, reviews, and categories.
• Maker outreach: enable getDetails to collect makers, hunter, social links, launch history, and discussion fields.
• Traction scoring: use tractionScore, contactScore, qualityScore, and leadSignals to prioritize records before CRM import.

Useful input fields

Field	Use
startUrls	Product Hunt leaderboards or product pages.
startDate, endDate	Daily leaderboard range in YYYY-MM-DD format.
getDetails	Opens product pages for maker, hunter, website, comments, and reviews.
maxResults	Limit saved products; keep low for detailed runs.
maxCommentPages	Add comment pages per product when details are enabled.
maxConcurrency	Lower values are slower but more stable.
useApifyProxy	Recommended for cloud runs.

Output fields

The dataset can include:

• name
• tagline
• productHuntUrl
• companyWebsite
• websiteDomain
• upvotes
• position
• rank
• categories
• makerUsernames
• hunterUsername
• comments
• reviews
• leadScore
• contactScore
• tractionScore
• leadSignals
• outreachReady
• qualityWarnings

Dataset views

Use the built-in views for faster review:

• Overview: launch rank, product, upvotes, scores, and URLs.
• Lead generation: website, domain, maker, hunter, social, and outreach fields.
• Traction: upvotes, comments, reviews, launch count, and performance score.
• Details: enriched product page fields and quality warnings.

Settings that convert best

• Use getDetails: false for broad monitoring.
• Use getDetails: true only for a small shortlist.
• Keep maxCommentPages: 0 unless comments are part of the workflow.
• Start with one date, confirm the output, then expand the range.

Notes

• Product Hunt pages are dynamic and can be slow.
• Detail extraction is best effort; Product Hunt may hide or delay maker, comment, review, website, or social fields.
• Use source URLs, dates, and quality warnings when sending records to CRM or AI workflows.

Support

If a run returns unexpected data, open an issue from the Actor page with the input used, the run ID, and the result you expected.