Product Hunt Scraper — Daily Launch Data

What this Actor scrapes

Product Hunt publishes a live RSS feed at producthunt.com/feed covering each day's launches across all categories. This Actor wraps it, normalises every row with Pydantic, and pushes structured data straight to your Apify dataset. Run it on a schedule and you get a persistent, queryable record of every public PH launch — no OAuth application, no rate-limit negotiation, no manual checks.

What we handle for you

• 🛡️ Browser fingerprint rotation — curl-cffi impersonates real Chrome / Firefox / Safari TLS handshakes so the target sees a browser, not Python.
• 🌐 Residential proxy rotation via Apify Proxy — fresh session and fresh exit IP every time a connection is throttled.
• 🔁 Retries with exponential backoff on 408 / 429 / 5xx — up to 5 attempts per page, Retry-After headers honoured exactly.
• 🧱 Rate-limit-aware pacing — when the target pushes back we slow down rather than accumulating blocks.
• 🧊 Clean, typed dataset rows — Pydantic-validated, ISO-8601 timestamps, stable IDs, ready for JSON / CSV / Excel export straight from Apify Console.
• 💰 Pay-Per-Event pricing — you pay only for results that land in your dataset. No data, no charge (beyond the small warm-up fee).

Use cases

• Startup trend monitoring — diff yesterday's launches against last week to surface rising categories before they go mainstream.
• Investor scouting — pipe every new B2B SaaS launch directly into your CRM the day it ships.
• Product Hunt competitor monitoring — get an alert whenever a rival (or a new entrant in your category) launches on PH.
• Sales lead generation — founders who just launched are primed for outreach. Feed the daily stream into Clay or Apollo for enrichment.
• Automated Product Hunt monitoring via n8n / Make / Zapier — connect the Actor output to Slack, Notion, or a Beehiiv newsletter in minutes.
• Newsletter automation — publish a "Yesterday's top PH launches" digest without manually visiting the site.

Input

Paste this into the Apify Console, or send it as the run input over the API. Proxy settings are on by default; you rarely need to touch them.

{
  "feedUrl": "https://www.producthunt.com/feed",
  "maxResults": 3,
  "includeContent": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

Output

One row per result, schema-validated before it is written. Export JSON, CSV, Excel or XML from the run, or read it over the API.

feed_urltitlenametaglinelinkauthorcontent_htmlcategoriespublishedscraped_at

{
  "feed_url": "https://www.producthunt.com/feed",
  "title": "Devil Scrapes \u2014 Honest pay-per-event Apify Actors",
  "name": "Devil Scrapes",
  "tagline": "Honest pay-per-event Apify Actors",
  "link": "https://www.producthunt.com/posts/devil-scrapes",
  "author": "DevilScrapes",
  "categories": [
    "Developer Tools",
    "Data & Analytics"
  ],
  "published": "2026-05-15T08:00:00+00:00",
  "scraped_at": "2026-05-15T08:05:00+00:00"
}

Pricing

You pay only for results that land. Cap any run with maxTotalChargeUsd. See pricing & billing for worked examples.

Limitations

• RSS window is shallow — the feed typically covers 1–2 days of the most recent launches. For historical data going back weeks or months, you need the Product Hunt GraphQL API (separate paid integration).
• No vote counts or comment totals — those live on the rendered HTML page, not in the RSS feed. Use the official PH API for those fields.
• Maker / Hunter details are sparse — dc:creator gives one name; full maker profiles and hunter attribution require the PH API.
• Topic feeds may lag — category-specific feeds sometimes update more slowly than the global feed.