Product Hunt Launch Lead Finder

Find fresh Product Hunt launches and turn them into scored B2B outreach leads.

This Actor monitors the public Product Hunt Atom feeds and outputs launch leads with product name, tagline, maker name, Product Hunt URL, product slug, discussion and outbound launch links, launch age, matched campaign keywords, lead score, lead tier, buyer persona, outreach angle, and optional Google plus separate LinkedIn founder/company search URLs for quick contact enrichment.

It can merge several Product Hunt category feeds in one run (AI, developer tools, SaaS, marketing, ecommerce, fintech, productivity, design tools, no-code, tech). Each category feed returns up to 50 launches and is deduplicated by launch ID, so a single run covers far more launches than the default all-launches feed alone.

Who should use this

• outbound agencies looking for companies that just launched and are likely to buy growth help
• SaaS sales teams selling analytics, CRM, onboarding, support, automation, devtools, or AI infrastructure
• recruiters targeting freshly launched startups with visible makers
• founder-service providers offering design, SEO, launch amplification, pitch decks, ads, or integrations
• newsletters, communities, and sponsors looking for new products in a niche

Why this can get customers

Fresh launch timing matters. Product Hunt makers are actively promoting, answering comments, fixing onboarding, and chasing early users. That creates a short window where they are more receptive to relevant offers: launch distribution, analytics, onboarding, integrations, SEO, customer support, recruiting, and founder-led sales help.

Instead of returning a raw feed, this Actor gives a sales-ready table:

• lead score and hot/warm/review tier
• matched keywords for your GTM campaign
• recommended buyer persona
• concrete outreach angle
• founder/maker name when available
• Product Hunt page URL
• Google plus targeted LinkedIn people and company search URLs for quick contact discovery

Input options

Field	Description
maxItems	Maximum leads to return.
daysBack	Include launches published or updated within this many days.
categoryPreset	Campaign preset: b2b-saas, ai-tools, developer-tools, marketing-sales, ecommerce, or all.
categories	Product Hunt category feeds to merge, for example ["artificial-intelligence", "saas"]. Empty means the default all-launches feed. Each feed returns up to 50 launches, so more categories means wider coverage at the same per-lead price.
keywords	Extra keywords that boost/filter lead scoring, such as CRM, Shopify, analytics, API, or hiring.
minLeadScore	Minimum score required to output a lead.
includeSearchUrls	Adds Google and LinkedIn search URLs for manual contact enrichment.

Example input

{
  "maxItems": 25,
  "daysBack": 7,
  "categoryPreset": "marketing-sales",
  "categories": ["artificial-intelligence", "saas", "marketing"],
  "keywords": ["CRM", "lead", "email", "SEO", "analytics"],
  "minLeadScore": 55,
  "includeSearchUrls": true
}

Output fields

Field	Description
leadScore	0-100 lead quality score.
leadTier	hot, warm, or review.
productName	Product Hunt product name.
tagline	Product tagline/description from the feed.
founderName	Maker name from the feed author.
productSlug	Product Hunt product slug, useful as a stable join key.
launchId	Product Hunt post ID.
discussionUrl	Clean Product Hunt discussion URL with tracking parameters removed.
launchLinkUrl	Product Hunt outbound launch link for the product website.
daysSinceLaunch	Whole days between the launch timestamp and the run.
feedCategory	Category feed the launch came from, omitted for the default all-launches feed.
publishedAt / updatedAt	Feed timestamps.
matchedKeywords	Preset or custom keywords found in the product text.
buyerPersona	Suggested customer persona for the campaign.
outreachAngle	Plain-language reason to contact the maker now.
productHuntUrl	Product Hunt page URL.
googleSearchUrl	Google query combining the product and maker name for broader enrichment.
linkedinSearchUrl	LinkedIn people search targeted to the maker/product.
companyLinkedinSearchUrl	LinkedIn company search targeted to the launched product.

Example output

{
  "productName": "AI CRM Copilot",
  "tagline": "Automate sales workflows for B2B teams",
  "founderName": "Ada Maker",
  "productHuntUrl": "https://www.producthunt.com/products/ai-crm-copilot",
  "publishedAt": "2026-08-20T00:00:00.000Z",
  "categoryPreset": "marketing-sales",
  "matchedKeywords": ["sales", "crm", "workflow"],
  "leadScore": 86,
  "leadTier": "hot",
  "buyerPersona": "Outbound agencies, CRM vendors, SEO/content tools, lifecycle marketing consultants",
  "outreachAngle": "New Product Hunt launch by Ada Maker: AI CRM Copilot. It matches sales, crm, workflow. Pitch launch amplification, lead capture, SEO/content, email sequences, CRM enrichment, or founder-led sales help."
}

Feed reliability and run summary

Each Product Hunt feed request is retried once before a category is dropped. Retries apply to throttling and server-side failures (HTTP 408, 425, 429, and 5xx), use exponential backoff with jitter starting at 400 ms, and honor a Retry-After header when Product Hunt sends one. Client errors such as 404 or 400 fail immediately and are never retried, so a bad custom feedUrl surfaces as a clear error instead of a slow run.

Feeds are fetched in parallel and a failed category never aborts the run. The Actor only fails when every requested feed fails. At the end of each run, the OUTPUT key-value record reports coverage and retry behavior:

Field	Meaning
feedsAttempted	Feeds requested in this run.
feedsSucceeded	Feeds that returned Atom XML.
feedsFailed	Feeds skipped after exhausting their retry budget.
feedsRetried	Feeds that needed more than one attempt but recovered.
feedRequests	Total HTTP requests made across all feeds.
failedCategories	Category names skipped in this run.
uniqueEntries	Deduplicated launches after merging feeds.
leadsPushed	Leads written to the dataset and charged.

If feedsFailed is above zero on a schedule, the run is still usable, but check failedCategories to see whether a category feed changed or was rate limited.

Automate a daily lead workflow

For recurring prospecting, create an Apify schedule that runs once per day with daysBack set to 2. Send the completed dataset to Slack, Google Sheets, Airtable, HubSpot, Salesforce, n8n, Zapier, or a webhook-driven enrichment step. Use a stable categoryPreset and focused keywords so lead scores remain comparable from run to run, and pick the two or three categories your buyers actually launch in so coverage grows without lowering score quality.

The Product Hunt feed can repeat launches across daily runs. Deduplicate downstream on launchId when available, or on productHuntUrl as a fallback.

Usage and pricing behavior

The Actor is designed for pay-per-event pricing. It emits one qualified-launch-lead charge event only after a lead passes the recency and minimum-score filters and is written to the dataset. Filtered feed entries are not charged as qualified leads. maxItems therefore caps both the number of output records and the number of qualified-lead events in a run. The exact event price is displayed by Apify before a paid run.

Platform compute and storage usage may still apply according to your Apify plan. Start with maxItems: 3 to validate your preset and score threshold before scaling a scheduled workflow.

Data source, privacy, and limitations

The Actor uses the public Product Hunt Atom feed. It does not require login, cookies, proxies, or the official Product Hunt API. Product Hunt pages and outbound redirects may be protected, so this Actor intentionally avoids brittle browser scraping and focuses on stable launch-feed data plus search-enrichment URLs.

• Maker names are included only when exposed by the public feed.
• Search URLs are convenience links, not verified identities, emails, or contact records.
• Scores and outreach angles are prioritization aids; verify a lead before contacting it.
• Feed availability, fields, and timing are controlled by Product Hunt and can change.
• Use exported data and outreach workflows in accordance with applicable laws and platform terms.

For best results, run it daily with a focused preset and route hot leads into a CRM, Slack, or n8n workflow.