# Product Hunt Launch Feed Monitor - New Products & Changes

Monitor Product Hunt public launch feeds for new products and saved metadata changes. Export launch titles, descriptions and links for product discovery. Feed data only.

Canonical product page: https://mayd-it.com/data-tools/actors/product-hunt-launch-feed-monitor/

## Example input

```json
{
  "feeds": [
    "latest"
  ],
  "maxResults": 1,
  "itemsPerQuery": 1
}
```

## Full guide

# Product Hunt Launch Feed Monitor - New Products & Changes

**A lightweight launch watchlist with exact source IDs, useful taglines and saved change-only delivery without a developer token.**

Monitor Product Hunt's public launch feed with product names, taglines, source dates and saved comparisons. Filter launches by keyword, export CSV/JSON and review readable reports. No developer token.

## Start in under a minute

1. Paste feed into the first input field, or use the included sample.
2. Keep the five-result limit for your first run and choose **Start**.
3. Open **Observations**, **Scope and diagnostics**, or the **Readable run report** in Output. Export CSV or JSON from the dataset.

```json
{
  "feeds": [
    "latest"
  ],
  "maxResults": 5,
  "itemsPerQuery": 3
}
```

No source account, API key, paid proxy or extra subscription is required for these public endpoints. Source availability and rate limits still apply.

## Who this helps

Startup researchers and SaaS teams watching new products and competitors.

## What you receive

One row per unique confirmed observation. Keyword filters inspect titles and taglines within the current feed window; they do not expand source coverage. Source timestamps that merely refresh do not create a change by themselves. Every row includes a stable `recordId`, title, source URL and observation time.

| Field | Meaning |
|---|---|
| `postId` | Source-reported post id; missing optional values remain null. |
| `tagline` | Source-reported tagline; missing optional values remain null. |
| `publishedAt` | Source-reported published at; missing optional values remain null. |
| `authorName` | Source-reported author name; missing optional values remain null. |
| `comparisonStatus` | not_requested, new, changed or unchanged |
| `changedFields` | Fields different from your last saved observation |
| `previous` | Previous saved source values when comparison is enabled |

## Saved comparisons

Enable **Compare with saved observations**, choose a snapshot name, and reuse the same input scope. The first run establishes history; it cannot report changes before that point. Enable **Save only new or changed observations** for later runs if you want a change-only export. An unchanged run can correctly save zero rows.

Only confirmed saved rows advance history. A bounded or failed run never establishes that a missing record was deleted. History is stored in a named key-value store in the running user's account. Use one writer per snapshot: do not overlap runs against the same snapshot. Change the snapshot name when starting a new independent workflow.

## Scope and limitations

Current public Product Hunt Atom feed only. Feed publication dates can precede today's listing. No historical leaderboard, vote counts, emails or complete launch coverage. Feed-wide updated timestamps are excluded from change detection to avoid false changes.

At most ten input values and five hundred saved rows per run. Each input performs one bounded public source request. Set Results requested per query to widen the feed window, up to 100 where available; the default is five. Responses are capped at 8 MiB and share the run deadline. No authentication bypass or code execution is performed. HTTP 429 stops further requests. Source failures appear in SUMMARY and the HTML report, never as paid data rows.

## Pricing

The configured base price is **$0.001 per saved observation**, plus **$0.00005 per start** at the default memory. Five observations cost $0.00505 at that base rate. Applicable plan discounts and the Store pricing panel govern actual charges. Set a maximum charge in Run options. Diagnostics, reports and unchanged skipped rows are not dataset result events.

## Make it recurring

Save an Actor task with your inputs, then attach an Apify Schedule. For change detection, keep the same snapshot and avoid overlapping runs. Add an integration to deliver results to your own spreadsheet or workflow. No external delivery is enabled automatically.

## Examples

1. **One launch** — Minimal first-run sample.
2. **Three launches** — Small research export.
3. **Five launches** — A broader current-feed sample.

## Source and support

[Official source documentation](https://www.producthunt.com/feed). This independent Mayd IT tool is not affiliated with the source platform. Open an Actor issue with the run ID and expected result, or contact bmay@mayd-it.com. Never include credentials.