Resources · Make integration

Productboard Make integrationAutomate Productboard with Make.

Can Make react when a feature changes in Productboard? Yes. The Productboard Make integration gives you 10 modules: 4 triggers, 5 actions and 1 search. It suits product teams who gather feedback in several tools. This guide takes you from the connection to a first working scenario.

Try the Productboard integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Productboard Make integration let you automate?

The Productboard Make integration plugs your Productboard workspace into Make, a no-code tool where you build a scenario: an automation made of modules, and each module is one brick such as a trigger, an action or a search. With it, Make can watch your features, read them, change them and drop notes into Productboard from the other tools you use.

Customer feedback that files itself. A support message or a form answer arrives elsewhere, and Create a Note turns it into a Productboard note, ready for triage. Nobody pastes quotes by hand anymore.

Roadmap changes that reach sales. Watch Feature Updated starts a scenario as soon as someone edits a feature, and the next module passes the news to the channel your account managers actually read.

A record of what was dropped. Watch Feature Deleted fires when a feature disappears, so you can log it in a sheet and still answer the customer who asked for it.

The listed modules cover features and notes only. For any other part of Productboard, Make an API Call reaches the rest of the API with the same connection. The Make documentation gives no numeric limit for this app. The same app often exists as an n8n node too; the n8n vs Make comparison helps you pick, the Make training covers the editor from scratch, and Make troubleshooting helps when a run fails.

Connect

How do you connect Productboard to Make?

  1. 01

    Get your API key

    Before touching Make, open your Productboard account and generate an API key. You need an active Productboard account for this. Keep the key at hand: it goes into the API Key field of the connection.

  2. 02

    Add a Productboard module

    In your scenario, add any Productboard module and click Create a connection. A connection is your Productboard account linked to Make once, then reused by every Productboard module. Naming it is optional.

  3. 03

    Paste the key or authorize

    Make offers two ways in: paste your key into API Key, or pick OAuth and approve access on the Productboard page that opens. Click Save, and the module can now list your features.

First scenario

Your first scenario: feedback that becomes Productboard notes

GoalWhen a customer message lands in your support or form tool, Make creates a note in Productboard.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big +. This first slot holds whatever starts the flow.

  2. 02

    Pick the source of feedback

    Search for the app where customer messages arrive, such as your helpdesk or form builder, choose its trigger and link its account with Create a connection.

  3. 03

    Add Create a Note

    Click the + on the right of that first module, search Productboard and choose Create a Note. Select your Productboard connection, then map the message from the previous module into the note.

  4. 04

    Test with Run once

    Send yourself a sample message, then click Run once. Make runs the scenario one time and shows the bundles each module received. Check that the note appears in Productboard.

  5. 05

    Schedule and switch on

    Open the clock on the first module under Scheduling. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Then switch the scenario on.

Triggers

What can start a Productboard scenario?

4 modules start a scenario when something happens in Productboard. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Productboard as soon as it happens.

Productboard1Watch new features

Watch new features

triggerIn the docs only

Watch new features collects the features added to Productboard since its last check and passes each one on as a bundle, which is a single item moving from one module to the next.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and the module carries a clock badge.
When to use it
pick it when a short delay is fine, for instance to copy fresh features into a planning sheet in batches.
Watch out
the Make documentation lists this module by name only, without a description, and its scheduled type is inferred from that name. Check the badge in the editor before you build on it.
Productboard2Watch Feature Updated

Watch Feature Updated

Instant trigger

In Make“Triggers when a feature is updated.”

Watch Feature Updated starts your scenario the moment someone edits a feature, so a change in Productboard reaches your other tools without anyone relaying it.

How it fires
instant. Productboard calls Make through a webhook as soon as the update happens, shown by the lightning badge.
When to use it
a status moves and customer success needs to hear about it before the next call with a client.
Watch out
every edit counts, even a typo fix, and each module in the run uses operations. An operation is one execution of one module, the unit Make counts on your plan.
Productboard3Watch Feature Deleted

Watch Feature Deleted

Instant trigger

In Make“Triggers when a feature is deleted.”

Watch Feature Deleted gives you a signal when a feature disappears from Productboard, which is the moment people usually lose track of who asked for it.

How it fires
instant. Productboard warns Make through a webhook as soon as the deletion happens.
When to use it
keep an audit line in a spreadsheet, or tell the account owner that the request they were waiting on is off the board.
Watch out
once removed, the feature is probably no longer readable with Get a Feature, so build the rest of the scenario around what this trigger hands you instead of a later lookup.
Productboard4Watch Feature Created

Watch Feature Created

Instant trigger

In Make“Triggers when a new feature is created.”

Watch Feature Created wakes your scenario when a new feature is added, which lets the whole team see fresh ideas without opening Productboard.

How it fires
instant. Productboard calls Make through a webhook as soon as the feature exists.
When to use it
choose it over Watch new features when timing matters, for example to open a ticket for engineering right after a feature appears.
Watch out
do not run it alongside Watch new features in two active scenarios for the same job. Each new feature would be handled twice, and the Free plan allows only 2 active scenarios anyway.
Modules

What can Make do in Productboard?

Productboard gives you 6 modules in 4 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Features

3 modules
Productboard1

List Features

Search

In Make“Lists all features.”

List Features pulls your Productboard features in one go and returns them as separate bundles, zero, one or many depending on what exists.

When to use it
you want a full export of the board into a sheet or a report for a roadmap review.
Watch out
every module placed after it runs once per feature, so a large board quickly adds up in operations.
Productboard2

Get a Feature

Action

In Make“Returns information about the selected feature.”

Get a Feature fetches the current details of one feature, so the rest of your scenario works from fresh data rather than a stale copy.

When to use it
after a trigger or a search, when a later step needs to know more about that exact feature before acting.
Watch out
map the feature from the previous module instead of choosing it by hand, otherwise every run reads the same one.
Productboard3

Update a Feature

Action

In Make“Updates the selected feature.”

Update a Feature changes a feature you select, which keeps Productboard in step with work tracked somewhere else.

When to use it
the engineering tool marks a task as shipped and the matching feature in Productboard should say so too.
Watch out
if the scenario starts with Watch Feature Updated and edits that same feature, the update fires the trigger again and the scenario can loop.

Notes

1 module
Productboard4

Create a text note

ActionIn the docs only

Create a text note adds a note to Productboard; the Make documentation lists it without a description, and its name suggests a note made of plain text.

When to use it
short written feedback, like a sales call summary, that needs to land in Productboard as is.
Watch out
Create a Note does a similar job, so try both with Run once and keep the one whose result fits your triage.

Other

1 module
Productboard5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets your scenario reach any endpoint of the Productboard API, reusing the connection you already created, so you are not limited to features and notes.

When to use it
the object or action you need has no dedicated module in this list.
Watch out
you write the request yourself, so keep the Productboard API reference open while you fill in the module.

Other modules

1 module
Productboard6

Create a Note

Action

In Make“Creates a new note.”

Create a Note records a new note in Productboard, giving every customer insight a place in the same inbox your product team already triages.

When to use it
a support ticket, a survey answer or a chat transcript should end up in Productboard without copy and paste.
Watch out
each bundle that reaches this module becomes its own note, so a search before it that returns several items creates several notes.
Need help

Need help automating Productboard with Make?

A person reads every message.

FAQ

Productboard and Make: common questions

01Is the Productboard Make integration free?
Yes, on the Make side. Productboard is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution, with usage counted in credits each month. You still need an active Productboard account, whose subscription is set by Productboard.
02What does it take to connect Productboard to Make?
An active Productboard account and a way to authorize Make. The documentation describes two options. The first is an API key generated in your Productboard account and pasted into the API Key field of the connection. The second is OAuth, where you approve access on a Productboard page. In both cases, you start from any Productboard module, click Create a connection, give it a name if you want, then click Save. The connection is then shared by all Productboard modules in your scenarios.
03Do Productboard triggers in Make fire in real time?
Mostly yes. Three of the 4 triggers are instant: Watch Feature Created, Watch Feature Updated and Watch Feature Deleted. Productboard calls Make through a webhook as soon as the event happens, so there is no schedule to wait for. The fourth, Watch new features, is scheduled: Make checks Productboard on the scenario's schedule, every 15 minutes by default, and never more often than every 15 minutes on the Free plan. Paid plans can go down to 1 minute. When speed matters, prefer Watch Feature Created.
04What if a Productboard module is missing in Make?
Use Make an API Call. This module can call any endpoint of the Productboard API with the connection you already have, which covers whatever the 9 other modules leave out, such as objects beyond features and notes. You describe the request yourself, so the Productboard API reference is your guide. The Make documentation lists no numeric limit for this app, so the constraints you meet are those of your Make plan, like the number of active scenarios and the run duration.
05Should you use Make or n8n for Productboard?
It depends on the tool your team already runs. On Make, Productboard comes with 10 ready modules: instant triggers on created, updated and deleted features, a scheduled watch, feature actions, two note modules and Make an API Call for the rest. Apps found on Make often have an n8n node as well, so check that the modules you need exist on both sides. Then weigh which editor your team will maintain day to day. The n8n vs Make comparison on this site lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations