Email a Weekly Product Hunt Leaderboard Digest

How It Works

This n8n workflow fires every Friday at 17:00 and uses Apify to fetch Product Hunt’s weekly leaderboard for the topics you choose. It drops launches below a minimum vote count, sorts the rest by votes, and compiles the top results into a single ranked HTML email. Gmail then delivers the digest to the address you configure, so a week of launches in your space arrives as one message.

Setup Steps

1. Connect Apify: Add an Apify credential (API token) that can run the dami_studio/producthunt-scraper actor.
2. Connect Gmail: Add a Gmail credential and make sure the account is allowed to send email from n8n.
3. Set Your Configuration: Update the topics, minVotes, keep (top N), and digestEmail values to match the categories you track and where the digest should go.
4. Add Slack (Optional): Add a Slack credential, pick a target channel, and connect the digest output to the Slack step to post the digest in a channel too.
5. Archive in Google Sheets (Optional): Add Google Sheets credentials, choose a spreadsheet and sheet, and connect the sorted launches to the Google Sheets append step.
6. Activate the Schedule: Turn the workflow on so it runs every Friday at 5 PM.

Automation Workflow

Schedule Trigger (every Friday, 17:00)
    ↓
Set Configuration (topics, minVotes, keep, digestEmail)
    ↓
Apify: dami_studio/producthunt-scraper (weekly leaderboard per topic)
    ↓
Filter launches below minVotes → Sort by votes (descending)
    ↓
Build HTML digest of top N launches (or a "no launches" message)
    ↓
Gmail: send digest to digestEmail
    ↓ (optional)
Slack post  /  Google Sheets append

Benefits

• No Manual Browsing: The weekly leaderboard for your topics lands in your inbox instead of requiring a Friday visit to Product Hunt.
• Signal Over Noise: The vote threshold and top N limit keep the digest short and focused on launches that gained traction.
• Topic Control: One configuration node defines which Product Hunt topics, how many launches, and which recipient, so changes take seconds.
• Clear Empty Weeks: When nothing passes the threshold, the workflow still sends a “no launches” message, so a missing email never hides a failed run.
• Optional History: The Google Sheets branch builds a running archive of ranked launches for later trend analysis.

Use Cases

• Product managers tracking new launches in their category each week
• Founders and investors scouting emerging tools and competitors on Product Hunt
• Marketing teams collecting launch ideas and positioning examples for their own release
• Newsletter writers sourcing a weekly “top launches” section for a niche topic
• Agencies sharing a weekly tool roundup with clients or an internal Slack channel