HomeBack to recipes
RecipesMarketingProduct Hunt Scraper Alert

TL;DR

Product Hunt Scraper Alert is a marketing workflow that chains Firecrawl + Slack to automate a common task. Scrape Product Hunt daily with Firecrawl and send trending posts in your category to Slack so your team never misses a launch. Once configured, it saves ~3 hours/week per founder/PM, plus preservation of reaction-time advantage on competitor moves and runs through Claude Code, Cursor, Windsurf or any MCP-compatible AI agent.

🔥💬
MarketingBeginner

Product Hunt Scraper Alert

Scrape Product Hunt daily with Firecrawl and send trending posts in your category to Slack so your team never misses a launch.

5 min setup, daily market intelligence2 MCPs requiredSaves ~3 hours/week per founder/PM, plus preservation of reaction-time advantage on competitor moves

How it works

🔥Firecrawl
💬Slack
Automated
1Daily 9 AM: scrape Product Hunt /tech2Filter posts by relevant category tags3Extract title, tagline, upvote count+2 more steps
Hostable — runs in your browser2/2 MCPs hosted

Run with MCPizy

New

Execute this recipe in your browser — no local install, no Claude Code. Streams results live.

Whitelisted MCPs: perplexity, notion, anthropic, openai, tavily, firecrawl, coingecko, stripe, slack, github, gitlab, linear, resend, sendgrid, elevenlabs, shopify, sentry, posthog, supabase-mcp, context7, deepwiki~4k tokens  ·  ~$0.012 est.

Why this combo?

Firecrawl extracts structured data from Product Hunt including upvotes, categories, and taglines despite JS rendering; Slack delivers that intelligence to your whole team every morning. Together they ensure you never miss a competitor launch or a product in your category gaining traction.

Without this workflow

Check Product Hunt manually a few times a week. Miss a direct competitor that launched yesterday and is trending. Find out from a customer who asks why you don't have that feature.

With MCPizy

Every morning at 9 AM your team gets a Slack digest of trending products in your category. You see launches the day they happen.

Business value

Concrete ROI — not marketing fluff.

Time saved

~3 hours/week per founder/PM, plus preservation of reaction-time advantage on competitor moves

  • Spot competitor launches the day they happen — respond with counter-messaging within 24h instead of 2 weeks
  • Identifies integration partners early — first-mover advantage on joint launches and co-marketing
  • Kills the 'customer told us about a competitor we didn't know existed' embarrassment
  • Feeds product roadmap with live market signal — build what's actually gaining traction, not yesterday's ideas

Workflow steps

  1. 1
    Daily 9 AM: scrape Product Hunt /tech
  2. 2
    Filter posts by relevant category tags
  3. 3
    Extract title, tagline, upvote count
  4. 4
    Format digest message
  5. 5
    Post to #market-intel Slack channel

Use cases

  • Daily trending products digest filtered to your specific category
  • Immediate alert when a direct competitor launches on Product Hunt
  • Track upvote velocity for launches in your space over time
  • Never miss a new tool that your customers might ask you to integrate with

MCPs required

🔥

Firecrawl

Firecrawl MCP Server

View
💬

Slack

Slack MCP Server

View

Agent prompt (copy into Claude Code)

This prompt is the workflow. Paste into Claude Code, Cursor, or Windsurf.

You are a Product Hunt monitor agent. Runs daily at 09:00.

1. Call firecrawl.scrape(url="https://www.producthunt.com/", formats=["json"], json_schema={posts: [{name, tagline, upvotes, category, url, maker}]}, render_js=true)
2. Filter posts by category against categories.yaml (e.g. ["developer-tools", "saas", "ai"])
3. For each relevant post, also call firecrawl.scrape(post.url) to extract description + tech stack mentions
4. Build a Slack digest block:
   - header: :rocket: Today on Product Hunt — ${filtered.length} in your space
   - per post: :arrow_up: ${upvotes} | ${name} — ${tagline} | <link>
5. Call slack.send_message(channel="#market-intel", blocks=[...])
6. For direct competitors (names in competitors.yaml), also post individual alerts with @here mention

Keep upvote threshold configurable (default: >= 50 upvotes to reduce noise).

Trigger & credentials

How this workflow fires and what env vars you need.

.env.example
ScheduledTrigger
0 9 * * *  # daily at 09:00 UTC
🔥Firecrawl· 1 var
FIRECRAWL_API_KEYGet key

Firecrawl API key

e.g. fc-...

💬Slack· 2 vars
SLACK_BOT_TOKENGet key

Slack bot OAuth token with chat:write

e.g. xoxb-...

SLACK_MARKET_INTEL_CHANNEL

Channel for Product Hunt digests

e.g. #market-intel

One-command deploy

Install everything — MCPs, prompt, env template — in a single call.

$ mcpizy recipe install firecrawl-slack-product-hunt

✓ Installs all 2 MCP servers
✓ Writes prompt to ~/.mcpizy/prompts/firecrawl-slack-product-hunt.md
✓ Generates .env.example in current directory
✓ Ready to paste into Claude Code

Requires mcpizy CLI v1.1+ — install via npm i -g mcpizy.

Quick install (MCPs only)

5 min setup, daily market intelligence
$ mcpizy install firecrawl && mcpizy install slack

More Marketing recipes

🔮📝

Competitor Watch Automation

Run daily Perplexity searches on competitors and log product updates, pricing changes, and news to a Notion tracker.

🔍

[Benchmark] Tavily News Search

Internal benchmark-only recipe: one Tavily search call, returns a short summary. Not intended for production use.

🔍

[Benchmark] Tavily 2-step Research

Internal benchmark-only recipe: Tavily search + answer for a topic, 2 tool calls.

🔍

[Benchmark] Tavily 3-query Multi-angle

Internal benchmark-only recipe: 3 Tavily searches on different angles of a topic, then synthesise.

Frequently asked questions

What is this workflow?

Product Hunt Scraper Alert is a marketing automation that uses Firecrawl + Slack together via the Model Context Protocol. Scrape Product Hunt daily with Firecrawl and send trending posts in your category to Slack so your team never misses a launch.

How long does setup take?

Setup takes around 5 min setup, daily market intelligence. You install the required MCP servers with `mcpizy install firecrawl && mcpizy install slack`, connect your accounts, and the workflow is ready to run.

How much time does this workflow save?

Once running, this workflow saves ~3 hours/week per founder/PM, plus preservation of reaction-time advantage on competitor moves. The concrete business value: Spot competitor launches the day they happen — respond with counter-messaging within 24h instead of 2 weeks; Identifies integration partners early — first-mover advantage on joint launches and co-marketing.

Which MCP servers do I need for this?

You need 2 MCP servers: Firecrawl (mcpizy install firecrawl), Slack (mcpizy install slack). All are installable in one command via the MCPizy CLI and configured in your `.claude.json` or `.cursor/mcp.json`.

Does this work with Claude Code, Cursor, and Windsurf?

Yes. The workflow runs with any MCP-compatible AI agent — Claude Code, Claude Desktop, Cursor, Windsurf, VS Code with Copilot, and custom agents built on the MCP SDK. The MCP servers are identical across clients; only the config file path (`.claude.json` vs `.cursor/mcp.json`) changes.

Start building this workflow

Install the required MCPs from the marketplace and automate this in 5 min setup.

$ mcpizy install firecrawl && mcpizy install slack

🔥Install Firecrawl💬Install Slack

Free to install. Connect your accounts and this workflow runs itself.