Resources · Make integration

Product Hunt Make integrationAutomate Product Hunt with Make.

Can Make pick up every new Product Hunt post for you? Yes. The Product Hunt Make integration offers 2 modules, one scheduled trigger and one action. This guide shows how to link your account and build a first scenario that runs on its own.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Product Hunt Make integration automate?

The Product Hunt Make integration links your Product Hunt account to Make, a no-code tool where you chain apps into automations called scenarios. It gives you 2 modules: Watch Posts, a trigger that picks up new posts, and Execute a GraphQL Query, an action that sends Product Hunt a query you write. GraphQL is the query language Product Hunt answers in: you spell out exactly which data you want back.

Share new launches with your team. Watch Posts catches each new post, and a module from your chat tool drops it where your team talks. A product team keeps launches in view without opening the site.

Keep a launch log. Send every post that Watch Posts finds into a table, for instance through the Airtable Make integration, so your marketing team can sort and comment on it later.

Ask Product Hunt for exactly what you need. Execute a GraphQL Query runs the query you write, authorized by your connection. A growth analyst can start it from another app and store the answer next to their own data.

What Make does not offer for this app: no instant trigger, no search module and no Make an API Call module, so the GraphQL action is your only way to reach beyond new posts. n8n often has a node for the same app, and the n8n vs Make comparison sets out how the two tools differ. For a wider look at Make itself, read the Make review.

Connect

How do you connect Product Hunt to Make?

  1. 01

    Add a Product Hunt module

    In your scenario, add Watch Posts or Execute a GraphQL Query, then click Create a connection. A connection is your Product Hunt account linked to Make one time.

  2. 02

    Name the connection

    This step is optional. A clear name, such as the account or the team it belongs to, helps when several people build scenarios in the same Make organization and pick from the same list.

  3. 03

    Authorize Make and save

    Depending on what the window asks, approve Make on the Product Hunt page that opens or paste the key Product Hunt gives you. Then click Save and the module is ready to fill.

First scenario

Your first scenario with Product Hunt

GoalWhen a new post appears on Product Hunt, Make runs the GraphQL query you wrote, using data taken from that post.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + on the canvas. A scenario is the automation you build, one module after another.

  2. 02

    Add Watch Posts

    Search for Product Hunt, pick Watch Posts and click Create a connection to link your account. This trigger hands each new post to the next module as a bundle, one item at a time.

  3. 03

    Add the GraphQL query

    Click the + to the right of Watch Posts, choose Execute a GraphQL Query and write your query. Map values from the post by picking them from the data of the previous module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time, and you can read the bundles each module received to check that the query returned what you expected.

  5. 05

    Schedule and switch it on

    On the first module, open the clock: the default schedule is every 15 minutes. Keep it or change it, then switch the scenario on so Make checks Product Hunt by itself.

Triggers

What starts a Product Hunt scenario

1 module starts a scenario when something happens in Product Hunt. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Product Hunt as soon as it happens.

Product Hunt1Watch Posts

Watch Posts

Scheduled trigger

In MakeTriggers when a new post is posted.

At each check, Watch Posts picks up the posts published on Product Hunt since the last one and passes each post to the next module as its own bundle. You get fresh launches flowing into your tools without refreshing the site.

How it fires
scheduled. Make checks Product Hunt on the scenario's schedule, every 15 minutes by default, and the clock badge on the module shows it.
When to use it
a team that wants every new launch copied into a shared table or chat.
Watch out
a new post waits for the next check, and the Free plan allows 15 minutes at least between two scheduled runs.
Modules

What the Product Hunt action does

Product Hunt gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Product Hunt1

Execute a GraphQL Query

Action

In MakePerforms an arbitrary authorized GraphQL query.

Execute a GraphQL Query sends Product Hunt a query you write yourself, signed with your connection, and returns the answer to the next module. It opens every request the ready-made trigger does not cover.

When to use it
when Watch Posts is not enough and you need to ask Product Hunt something specific.
Watch out
placed after Watch Posts, it runs once per post, and Make counts each run as one operation on your plan.
Need help

Need help automating Product Hunt with Make?

A person reads every message.

FAQ

Questions about Product Hunt and Make

01Is the Product Hunt Make integration free?
Yes. Product Hunt is a standard app in Make, so it works from the Free plan onward. The Free plan comes with limits worth knowing before you start: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module per bundle.
02What do you need to connect Product Hunt to Make?
A Product Hunt account and a Make account are enough to begin, and no other prerequisite is documented. Add a Product Hunt module, click Create a connection, give it a name if you like, then either approve Make on the Product Hunt page that opens or paste the key Product Hunt gives you. Click Save and you are done. The same connection then serves both modules, Watch Posts and Execute a GraphQL Query, in every scenario you build with this app.
03Does the Product Hunt trigger react in real time?
No. Watch Posts is a scheduled trigger: Make checks Product Hunt on the scenario's schedule rather than being called by Product Hunt the moment a post goes live. A new scenario checks every 15 minutes by default. On the Free plan the interval cannot go below 15 minutes, while paid plans can bring it down to 1 minute. For most launch tracking this delay is fine, but plan for it if your team expects a new post to show up the very second it is published.
04What if the module you need is missing for Product Hunt?
It depends on the request. Product Hunt has no Make an API Call module in Make, so that route is closed. Execute a GraphQL Query is the one to try first, since it sends any authorized query you write rather than a fixed request. If that still does not cover your case, another app in Make may hold the data you need, or the Hack'celeration team can look at the scenario with you and suggest a different path.
05Should you use Make or n8n for Product Hunt?
It depends on the tool your team already works in. On Make, Product Hunt brings 2 modules, a scheduled trigger for new posts and a GraphQL action for everything else, and it runs from the Free plan onward. n8n often has a node for the same app, so check what it offers for Product Hunt before choosing. Compare the modules each side gives you against your actual scenario rather than the brand, and pick the one where that scenario is simplest to build and maintain.