ProdPad

Feed your ProdPad backlog from every channel. Agents capture ideas and customer feedback automatically, tag feedback to contacts, post comments recording decisions on ideas, and read products, personas, and roadmaps for reporting.

10 actions API key available

ProdPad website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A customer conversation in the support inbox surfaces a feature request

Create Feedback logs the request in ProdPad, tied to the contact's name and email

List Ideas scans the backlog for an existing idea covering the same theme

Add Comment attaches the new feedback and its source conversation to the matching idea, so the evidence accumulates in one place

Create Idea opens a new backlog item instead when nothing matches, tagged by product area

The product manager triages the new idea, reads the attached evidence, and decides whether it moves to Under Consideration

The weekly digest posts to the product channel: new ideas, feedback volume per idea, and the themes gathering weight

What This Integration Enables

A product backlog is a research corpus, not a wish list, and its value depends entirely on what actually reaches it. The requests that die in Slack threads and closed tickets are the evidence your roadmap decisions never saw. ProdPad's model, feedback tied to contacts, ideas moving through workflow states, products and personas organizing both, is built for evidence-based prioritization; FlowRunner agents are the capture layer that keeps the evidence flowing in from everywhere customers actually talk. - Capture ideas and feature requests from forms, chats, and support tools into the backlog automatically - Log customer feedback against the contact who gave it, so frequency and attribution are countable at triage - Attach cross-system context to ideas as comments: the deal at stake, the ticket that prompted it, the decision made - Keep external dashboards synchronized with idea statuses across the workflow, from New through Released - Read products, personas, and roadmaps to organize reporting and drive downstream automation

Without FlowRunner

Feedback dies where it lands Requests live in support tickets, sales notes, and chat threads, and none of them reach the backlog

The loudest voice wins Prioritization runs on whoever asked most recently, because nobody can count how often anything was asked

Roadmap reporting is an export The backlog spreadsheet was current the day someone built it, and has not been since

With FlowRunner

Every channel feeds the backlog Requests become feedback records tied to real contacts the moment they occur, from every source

Ideas carry their evidence Each idea accumulates the feedback, comments, and context that make its case, countable and attributable

The backlog reports itself Idea statuses stream to sheets and dashboards on a schedule, and triage runs on live data

Use Case Scenarios

The feedback pipeline from support to backlog

New conversations in [Intercom](/integrations/intercom) get scanned for feature requests. Each one becomes a Create Feedback record naming the customer, and the agent checks List Ideas for the theme. A match gets the feedback attached via Add Comment with a link back to the conversation; a miss becomes a Create Idea in the right product area. When triage happens, the PM sees that the export-permissions idea now carries eleven pieces of feedback from eight named accounts, and prioritization stops being an argument about anecdotes.

The backlog dashboard that is never stale

On a schedule, the agent pages through List Ideas by workflow status, joins each idea's product from List Products, and writes the snapshot to [Google Sheets](/integrations/google-sheets). A summary posts to [Slack](/integrations/slack): what entered New this week, what moved to Getting Built, what shipped to Released. Stakeholders who will never open ProdPad still read an accurate roadmap picture, and the product team stops fielding status questions it already answered.

The decision that gets written down where it belongs

A prioritization call ends with a verdict: the integrations expansion moves ahead, the offline mode waits two quarters. The agent records both with Add Comment on the respective ideas, including the reasoning and the meeting date, and updates tags with Update Idea so the deferred item carries its revisit marker. Six months later, when the request resurfaces, Get Idea returns the whole history: who asked, what was decided, and why. The team re-decides only when the evidence has actually changed.

Human-in-Loop Highlight

Update Idea replaces what it touches: any field provided, title, description, tags, overwrites the current value entirely. An idea's description in ProdPad is often the product manager's accumulated thinking, the problem statement refined across months of feedback, and an agent that rewrites it in a sync pass has destroyed judgment work no API can restore. So FlowRunner agents follow an append-first rule on this connector: new evidence and context arrive as Add Comment, which only ever adds. When a workflow genuinely calls for rewriting an idea's title or description, the agent drafts the replacement, shows the current text beside it, and the idea's owner approves the overwrite before it happens. Capture is the agent's job. The written case for building something belongs to the person who has to defend it.

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

10 actions

Ideas

List Ideas Retrieves the idea backlog with pagination, filterable by workflow status from New through Archived. The read behind theme matching, triage queues, and backlog reporting.
Get Idea Retrieves a single idea in full: title, description, workflow state, tags, associated products, personas, and external links. The context pull before any decision or edit.
Create Idea Creates a new idea with title, description, and optional tags, starting in the first workflow status. The write that turns a captured request into a backlog item.
Update Idea Updates an idea's title, description, or tags, replacing any field provided and leaving omitted fields untouched. The action this page's human gate governs, because replace semantics make it an overwrite, not an edit.
Add Comment Adds a comment to an idea. The append-only channel where agents log discussion, decisions, and cross-system context without disturbing what a person wrote.

Feedback

List Feedback Retrieves customer feedback items with their text and associated contact, paginated. The review read for triage and for linking feedback to ideas.
Create Feedback Creates a feedback item with the text and the contact who provided it, optionally with their email. The capture step that makes requests countable and attributable.

Products

List Products Retrieves the products defined in the account. The organizing read for filtering ideas and feedback by product line.
List Personas Retrieves the user personas defined in the account. Used to associate captured requests with the user types they came from.
List Roadmaps Retrieves the roadmaps defined in the account, with their time horizons and lanes. The navigation read for roadmap-level reporting.

Frequently Asked Questions

What can FlowRunner do with ProdPad?

FlowRunner agents can run List Ideas, Get Idea, and Create Idea in ProdPad, plus 7 more actions.

Does connecting ProdPad to FlowRunner require OAuth?

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

Can ProdPad trigger a FlowRunner workflow automatically?

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

Start building with ProdPad

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

Start Building Free Talk to us