Resources · Make integration

ProdPad Make integrationAutomate ProdPad with Make.

Want feedback and ideas to reach ProdPad without copy and paste? The ProdPad Make integration gives you 14 modules, 5 of them triggers. This page is for product teams new to Make: link your account, build a first scenario and pick the right module.

Try the ProdPad integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the ProdPad Make integration do?

The ProdPad Make integration links your ProdPad account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick, such as a trigger that watches ProdPad or an action that writes to it, so feedback, ideas and user stories move between ProdPad and your other apps without manual work.

Feedback lands in ProdPad on its own. A support tool or a survey app sends Make a new comment, and Create a Feedback files it in ProdPad. Your product team reads every request in one place instead of hunting through inboxes.

Engineering hears about pushed work. Watch Pushed Ideas and Watch Pushed User Stories are instant triggers: ProdPad calls Make as soon as an item goes to development, and the next module can post the news wherever your developers already look.

Your backlog feeds reports. List Ideas and List Feedbacks are searches that return every matching item, one bundle each (a bundle is one item passed to the next module). Map them into a spreadsheet or a dashboard app to share the state of the roadmap.

Make will not cover every corner of ProdPad with ready modules: there are no delete modules and no user story actions in the list. For those, Make an API Call reaches the ProdPad API with the same connection. The same app often has an n8n node too; the n8n vs Make comparison sets out the criteria. To learn the editor itself, see the Make training, and check the Make pricing page before you count operations.

Connect

How do you connect ProdPad to Make?

  1. 01

    Copy your API key in ProdPad

    You need an active ProdPad account and its API key. In ProdPad, open your Profile settings, click API key in the menu, then copy the key shown on screen. Keep it at hand for the next step.

  2. 02

    Add a ProdPad module

    In your Make scenario, add any ProdPad module and click Create a connection. The Connection name field is optional: a clear label like the workspace name helps when several people share the account.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, then confirm. This connection, your ProdPad account linked to Make once, is reused by every ProdPad module you add later.

First scenario

Your first scenario: send survey answers to ProdPad

GoalWhen a customer answers your survey in another app, Make files the answer as feedback in ProdPad.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the trigger of the app that collects your survey answers: it is the first module and starts the flow.

  2. 02

    Add Create a Feedback

    Click the + on the right of that first module, search for ProdPad and choose Create a Feedback. Select the connection you made earlier, or click Create a connection if this is your first ProdPad module.

  3. 03

    Map the survey answer

    Fill the fields of Create a Feedback by mapping data from the survey module: click a field and pick the answer text from the list of values the first module returns. No typing of fixed text is needed.

  4. 04

    Test with Run once

    Click Run once, then submit one test answer in the survey app. Open the bubbles to read the bundles each module received, and check in ProdPad that the new feedback appeared with the right content.

  5. 05

    Schedule and switch on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on. On the Free plan, keep in mind that only 2 scenarios can be active at once.

Triggers

What can start a ProdPad scenario?

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

ProdPad1Watch Feedbacks

Watch Feedbacks

Scheduled trigger

In Make“Triggers when a new feedback is added to your ProdPad account.”

Watch Feedbacks starts your scenario with each feedback newly added to your ProdPad account, so a request typed by a colleague or sent by a customer can travel on to a ticketing tool, a chat channel or a spreadsheet without anyone forwarding it.

How it fires
scheduled. Make checks ProdPad on the scenario's schedule, every 15 minutes by default, and picks up the feedback added since the last check.
When to use it
your support lead wants every new piece of feedback copied to the tool the support team works in.
Watch out
each feedback found is one bundle, and every module after it spends one operation per bundle on your plan.
ProdPad2Watch Ideas

Watch Ideas

Scheduled trigger

In Make“Triggers when a new idea is added to your ProdPad account.”

Watch Ideas gives you a scenario that reacts to each new idea recorded in ProdPad, which is handy when ideas must also appear in a planning tool or reach the people who review them before the backlog grows out of sight.

How it fires
scheduled. Make asks ProdPad for new ideas on the scenario's schedule, so an idea shows up in your scenario at the next check, not the moment it is saved.
When to use it
a product manager wants a short message in the team chat each time someone adds an idea.
Watch out
this trigger sees new ideas only; a change to an existing idea does not start the scenario.
ProdPad3Watch Pushed Ideas

Watch Pushed Ideas

Instant trigger

In Make“Triggers when an idea in your ProdPad account is pushed to development.”

Watch Pushed Ideas lets engineering know the moment an idea leaves the product backlog: the scenario starts when an idea in your ProdPad account is pushed to development, so the next module can open a task or post an update right away.

How it fires
instant. ProdPad calls Make through a webhook as soon as the push happens, which you can spot by the lightning badge on the module.
When to use it
the delivery team wants a card created in its own board for every idea approved for build.
Watch out
click Create a webhook before the connection, otherwise nothing reaches Make.
ProdPad4Watch Pushed User Stories

Watch Pushed User Stories

Instant trigger

In Make“Triggers when a user story in your ProdPad account is pushed to development.”

Watch Pushed User Stories reacts at the user story level: your scenario runs whenever a user story in ProdPad is pushed to development, which suits teams that plan work story by story rather than idea by idea.

How it fires
instant. ProdPad notifies Make by webhook as soon as the story is pushed, with no waiting for a schedule.
When to use it
a QA lead wants a test checklist prepared in another app for each story sent to the developers.
Watch out
it listens to stories only. For whole ideas, Watch Pushed Ideas is the trigger to use, and it also needs Create a webhook first.
ProdPad5Watch User Stories

Watch User Stories

Scheduled trigger

In Make“Triggers when a new user story is added to your ProdPad account.”

Watch User Stories hands each newly written user story to the rest of your scenario, so stories drafted in ProdPad can be mirrored in a document, a tracker or a message to reviewers without a manual export.

How it fires
scheduled. Make checks ProdPad for new stories on the scenario's schedule and processes the ones added since the previous run.
When to use it
a design lead wants to hear about fresh stories early, well before they are pushed to development.
Watch out
it catches creation, not the push; for the handoff to engineering, the instant Watch Pushed User Stories is the right choice.
Modules

What can Make do in ProdPad?

ProdPad gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

ProdPad1

Create a Feedback

Action

In Make“Creates new feedback in ProdPad.”

Create a Feedback turns a message from another app into a feedback entry in ProdPad, so customer requests from support tools, forms or sales notes end up where the product team reviews them.

When to use it
after a trigger from your help desk or survey app, to file each comment as feedback.
Watch out
run the scenario once with a real sample to see exactly which content lands in ProdPad.
ProdPad2

Create an Idea

Action

In Make“Creates a new idea in ProdPad.”

Create an Idea adds a fresh idea to your ProdPad account from data your scenario already holds, which saves retyping when ideas are born in a workshop board, a chat thread or a form.

When to use it
when a request is concrete enough to become an idea rather than stay as feedback, for example once a teammate tags it in another tool.
Watch out
each run creates a new idea, so a test run with Run once also leaves one behind in ProdPad.
ProdPad3

Get a Feedback

Action

In Make“Fetches an individual feedback.”

Get a Feedback fetches one specific feedback so later modules can use its details, for instance to write a reply or enrich a record in your CRM with what the customer asked for.

When to use it
when an earlier module already points to a single feedback and you need its full content.
Watch out
it reads one item only; to go through many, List Feedbacks is the module to reach for.
ProdPad4

Get an Idea

Action

In Make“Fetches an individual idea.”

Get an Idea reads a single idea from ProdPad and passes its details down the scenario, useful when a notification should carry the full idea rather than a bare reference.

When to use it
right after Watch Pushed Ideas, to gather the idea's content before posting it to the engineering channel.
Watch out
it returns one idea per run of the module; each call counts as one operation.
ProdPad5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call is the way out when no listed module fits: it sends an authorized request to any endpoint of the ProdPad API, reusing the connection you already created.

When to use it
to act on user stories or to delete an item, since the ready modules only create, read and update feedback and ideas.
Watch out
you write the request yourself, so keep the ProdPad API documentation open and test with Run once.
ProdPad6

Update a Feedback

Action

In Make“Updates an existing feedback in ProdPad.”

Update a Feedback changes a feedback that already exists in ProdPad, keeping it in line with what happens elsewhere, such as a ticket closed in your support tool or a customer who added details.

When to use it
when an event in another app should be reflected on feedback that ProdPad already holds.
Watch out
map only the fields you mean to change and test on a sample entry before switching the scenario on.
ProdPad7

Update an Idea

Action

In Make“Updates an existing idea in ProdPad.”

Update an Idea edits an idea already stored in ProdPad, so its content stays current when decisions are taken in meeting notes, a spreadsheet or a planning tool.

When to use it
when a scoring sheet or review board elsewhere decides something the idea in ProdPad should show.
Watch out
the module changes the idea for everyone who works in ProdPad, so run a test on a throwaway idea first.
ProdPad8

List Feedbacks

Search

In Make“Fetches a list of feedbacks associated to the account.”

List Feedbacks pulls the feedback attached to your ProdPad account in one go, handy for a report, an export to a spreadsheet or a check before creating a duplicate.

When to use it
when a stakeholder asks for a table of all current feedback without logging into ProdPad.
Watch out
it is a search, so it can return zero, one or many bundles, and every module that follows runs once per bundle.
ProdPad9

List Ideas

Search

In Make“Fetches a list of ideas associated to an account.”

List Ideas returns the ideas held in your ProdPad account as separate bundles, so you can copy the backlog into a sheet, a slide deck tool or a dashboard for people outside the product team.

When to use it
to prepare a roadmap review with the full list of ideas at hand.
Watch out
a large backlog means many bundles; add a filter after it so later modules only spend operations on the ideas you need.
Need help

Need help automating ProdPad with Make?

A person reads every message.

FAQ

ProdPad and Make: common questions

01Is the ProdPad Make integration free?
Yes, on the Make side. ProdPad is a standard app, available from the Make Free plan, which allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes per execution, 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 per execution. Usage is counted in operations each month. You still need your own ProdPad subscription, which Make does not provide.
02What do you need to connect ProdPad to Make?
An active ProdPad account and its API key. In ProdPad, open Profile settings, click API key in the menu and copy the key displayed. In Make, add a ProdPad module, click Create a connection, give it a name if you like, and paste the key. For the two instant triggers, Make first asks you to click Create a webhook, then Create a connection. Once saved, the same connection serves every ProdPad module in all your scenarios, so there is nothing to set up twice.
03Do ProdPad triggers in Make fire in real time?
It depends on the trigger. Watch Pushed Ideas and Watch Pushed User Stories are instant: ProdPad calls Make through a webhook as soon as an item is pushed to development. Watch Feedbacks, Watch Ideas and Watch User Stories are scheduled: Make checks ProdPad on the scenario's schedule, every 15 minutes by default, and never more often than every 15 minutes on the Free plan or every minute on a paid plan. Pick an instant trigger when speed matters for the handoff to engineering.
04What if a ProdPad module is missing in Make?
Use Make an API Call. It sends an authorized request to any endpoint of the ProdPad API with the connection you already have, which covers what the 14 listed modules leave out, such as actions on user stories or deleting an item. You write the request yourself, so keep the ProdPad API documentation at hand and test with Run once. Note that the ProdPad page in the Make documentation is flagged as AI-generated content, so check important details with ProdPad directly.
05Should you use Make or n8n for ProdPad?
Both can work, and the choice rests on your needs rather than on ProdPad itself. In Make, ProdPad comes with 14 ready modules, including 2 instant triggers, and Make an API Call for the rest. The same app often has an n8n node as well, so compare the modules each tool offers for the jobs you plan, how you want to build and where your other automations already live. The comparison page linked above lists the criteria side by side, without ranking either tool.
Same platform

Other docs you might need on this stack.

Browse all integrations