FlowRunner
PricingContact
Theme
Start Free

Product Hunt

Social Media

Track Product Hunt launches from FlowRunner. Agents fetch daily featured posts ordered by votes or rank, read launch comments, browse curated collections and topics, and run custom GraphQL queries against the v2 API for anything else.

7 actions API key available
The morning market-intelligence sweep runs at 8 a.m.
Get Posts pulls yesterday's launches for the topics the company watches, ordered by ranking
The agent screens for launches that overlap the product's category or name known competitors
Get Post fetches full detail on the overlapping launches: makers, tagline, description, media
Get Post Comments reads the discussion for positioning signals and complaints worth noting
The founder reviews the competitive digest and decides what changes: messaging, roadmap notes, or nothing
The digest and decision log to the competitive-tracking sheet for the pattern to accumulate

What This Integration Enables

Product Hunt is where new software announces itself, which makes it two things at once: a discovery feed and the most current competitive dataset in tech. This connector reads both. FlowRunner agents fetch launches ordered by ranking, votes, featured date, or recency, filter them by topic slug, pull full post detail including makers and media, read the comment threads where the community says what it actually thinks, and browse the collections and topics that map the territory. A GraphQL escape hatch reaches anything the dedicated actions do not cover. The position: most teams treat Product Hunt as a launch-day event. The durable value is in watching it continuously, because category trends, competitor moves, and buyer language all surface there first, and an agent can watch every day without getting bored. - Run daily discovery sweeps on the topics that matter to your product - Mine launch comments for positioning signals and objection patterns - Track competitor launches with vote counts and reception attached - Build a longitudinal category dataset that compounds in value The topic and collection layer deserves its own mention. Get Topics exposes follower and post counts per category, which is a free proxy for where builder and buyer attention is concentrating, and Get Collections shows how curators are grouping the space. Watching those numbers move quarter over quarter tells you when a category is heating up before the launch volume makes it obvious.

Without FlowRunner

Launch tracking is somebody's browser habit Competitive awareness depends on who happened to scroll Product Hunt this week
Comment threads go unread The most honest product feedback on the internet sits in launch discussions nobody mines
Category history is unrecoverable What launched in your space last quarter, and how it was received, lives in scattered memories

With FlowRunner

Every launch in your space gets triaged Topic-filtered sweeps surface relevant launches daily, ranked and summarized
Community reaction becomes data Comments flow into analysis: what resonated, what got roasted, what buyers asked first
The tracking sheet becomes an asset Months of launches, votes, and reception build a category map no one else bothered to keep

Use Case Scenarios

The daily launch digest for the team

Each morning, Get Posts pulls the top-ranked launches for the artificial-intelligence and developer-tools topics. The agent formats name, tagline, votes, and URL into a digest and posts it to the team channel in [Slack](/integrations/slack). Fifteen seconds of scrolling replaces fifteen minutes of browsing, and the whole team shares one view of what launched instead of five partial ones. When something in the digest warrants a deeper look, the thread already carries the slug that Get Post and Get Post Comments need, so the follow-up is one message away.

Launch-day monitoring for your own product

On launch day, the agent polls Get Post by your product's slug through the day, logging vote and comment counts to [Google Sheets](/integrations/google-sheets) at each interval. Get Post Comments streams new questions into the war-room channel as they arrive, so makers answer in minutes rather than discovering a stalled thread at 4 p.m. The team runs the launch from one channel with live numbers instead of refreshing the page.

The competitor dossier that writes itself

When a competitor launches, the agent detects it in the topic sweep, pulls the full post with Get Post, and captures the entire comment thread with Get Post Comments once the discussion settles. Tagline, positioning claims, top comments, and vote trajectory land in the competitive tracker. Six months later, when sales asks how that competitor pitched themselves and what the market pushed back on, the answer is a document with dates and vote counts, not a teammate's fading memory of a launch day.

Human-in-Loop Highlight

Run GraphQL is the one door in this connector that opens outward. Every dedicated action here reads, but the escape hatch accepts mutations, and a mutation executes as the authenticated account from Get Viewer: a comment posted, a vote cast, an interaction made in public, under your name, in a community that reads authenticity like a credit score. A founder's account leaving an agent-written comment on a competitor's launch thread is not a bug you fix; it is a screenshot you live with. So FlowRunner treats the escape hatch asymmetrically: queries run freely as part of any sweep, but any payload containing a mutation stops and renders for human review, showing exactly what would be posted and as whom, before it executes. The reading never needs a person. Speaking in public always gets one.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

7 actions

Posts

3
  • Get Posts Lists launches with cursor-based pagination, ordered by featured date, votes, ranking, or newest, optionally filtered to a topic by slug. Returns name, tagline, slug, URL, vote and comment counts, and topics.
  • Get Post Retrieves a single post by numeric ID or slug, returning name, tagline, description, URL, counts, featured date, media, makers, and topics. The deep-dive step on any launch worth attention.
  • Get Post Comments Retrieves a post's comments with body, creation time, vote count, and author, cursor-paginated. The richest source of unfiltered market reaction this connector offers.

Collections

1
  • Get Collections Lists curated collections with name, tagline, follower count, and creator, cursor-paginated. Used to find themed product groupings worth monitoring.

Topics

1
  • Get Topics Lists topics with name, slug, description, and follower and post counts, cursor-paginated. Topic slugs feed the filter on Get Posts.

Account

1
  • Get Viewer Returns the authenticated user behind the developer token: ID, name, username, headline, profile URL, and avatar. The token check, and the identity every mutation would act as.

Advanced

1
  • Run GraphQL Sends any raw GraphQL query or mutation to the v2 API with optional variables, returning the raw data object. Queries flow freely; mutations pass this page's human gate.

Frequently Asked Questions

What can FlowRunner do with Product Hunt?

FlowRunner agents can run Get Posts, Get Post, and Get Post Comments in Product Hunt, plus 4 more actions.

Does connecting Product Hunt to FlowRunner require OAuth?

No. Product Hunt connects to FlowRunner with an API key, no OAuth flow required.

Can Product Hunt trigger a FlowRunner workflow automatically?

Product Hunt doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Product Hunt

$100 in credits. No card required. Connect in minutes.