--- title: "Productboard Integration" description: "Connect AI agents to Productboard. Agents capture customer feedback as notes, create and update features, browse the product hierarchy of products and components, link feedback to companies, and track release groups across product lines." url: https://flowrunner.ai/integrations/productboard date_modified: 2026-08-01T02:40:32-07:00 --- # Productboard [Project Management](https://flowrunner.ai/integrations/category/project-management-productivity) Connect AI agents to Productboard. Agents capture customer feedback as notes, create and update features, browse the product hierarchy of products and components, link feedback to companies, and track release groups across product lines. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 11 actions · API key · available [Productboard website](https://productboard.com/) · [Platform Documentation](https://developer.productboard.com/) · Capability data verified 2026-07-28 1. A support conversation closes with a feature request tagged by the support team 2. Create Note captures the customer's verbatim feedback, with their email attached so the note lands on the right company 3. List Features searches the workspace for an existing feature covering the same request 4. The product manager decides whether this becomes a new feature or evidence strengthening an existing one 5. Create Feature adds the approved feature under the right component, with the owner assigned by email 6. The product channel receives the note link and the feature link, so the evidence trail starts public ## What This Integration Enables Productboard's core promise is prioritization backed by evidence, and the evidence is the part most teams starve. When capturing an insight means a PM pasting quotes between tabs, the insight repository reflects whoever had time on Thursday, not what customers actually said. FlowRunner closes that gap: agents capture feedback as notes the moment it appears anywhere in the stack, associate it with the company that gave it, check new requests against the existing feature list, and keep the roadmap flowing outward to the people who plan around it. - Capture feedback from support tools, forms, and surveys as notes with verbatim content and source links - Attach customer emails so notes associate with companies for prioritization by segment - Create and update features from intake workflows, with owners assigned and parents set in the hierarchy - Sync products, components, features, and release groups into reports and spreadsheets - Keep roadmap-facing changes behind [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) review, because status is a promise ### Without FlowRunner **Feedback dies where it lands**: Requests live in support threads, sales calls, and survey exports that product never systematically reads **The roadmap argues from memory**: Prioritization debates run on whoever remembers the loudest customer, not on counted evidence **Roadmap reporting is an export chore**: Sharing feature status with stakeholders means a PM rebuilding a spreadsheet by hand ### With FlowRunner **Every request becomes a note**: Agents capture feedback verbatim from support, forms, and surveys, linked to the company that said it **Evidence accumulates on features**: New requests are checked against the existing roadmap so weight builds instead of duplicates **The roadmap reports itself**: Features, statuses, and release groups flow to spreadsheets and channels on a schedule ## Use Case Scenarios ### The insight repository that fills itself A conversation wraps in [Intercom](https://flowrunner.ai/integrations/intercom) with a product-feedback tag. The agent pulls the transcript, runs Create Note with the customer's words as HTML content, their email for company association, tags for theme, and a source URL back to the conversation. The same pattern handles survey responses from [Typeform](https://flowrunner.ai/integrations/typeform). When the product team opens Productboard for quarterly planning, the notes are already there, already linked to companies, and nobody spent an afternoon pasting. ### Request triage without duplicate features Each morning, the agent lists yesterday's unprocessed notes with List Notes, then runs List Features filtered by the relevant component to check whether each request matches something already on the roadmap. Matches get summarized to the PM with both links. Genuinely new themes arrive as a proposed feature: suggested name, description drafted from the note content, recommended parent component. The PM approves, Create Feature writes it with the owner set by email, and the backlog grows deliberately instead of accreting duplicates that split the evidence. ### Roadmap visibility on a schedule Every Friday, the agent walks List Products, List Components, and List Features with cursor pagination, assembles the current hierarchy with statuses and timeframes, and appends the snapshot to [Google Sheets](https://flowrunner.ai/integrations/google-sheets). Features whose status changed during the week get called out in a [Slack](https://flowrunner.ai/integrations/slack) digest, and List Release Groups frames the summary by release train. Stakeholders stop asking "what's the status of X" because the answer arrives before the question. ## Human-in-Loop Highlight Update Feature can archive a feature, and it can move a feature's status by name. Both operations rewrite the document the rest of the company treats as a commitment: sales references the roadmap in deals, support references it in tickets, customers hear about it in QBRs. An agent that silently flips a feature to a planned status has made a promise on the organization's behalf; one that archives a feature has quietly withdrawn one, pulling it out of the views the company plans by. So FlowRunner agents propose these changes rather than perform them. The PM sees the feature, its current status, the evidence count behind the change, and approves or declines. Note capture runs at machine speed all day. The roadmap only moves when a person moves 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 11 actions ### Features 4 - **List Features** Lists features with cursor-based pagination, optionally filtered by parent product, component, or feature, or by status. Returns each feature's id, name, description, type, status, timeframe, owner, and links. - **Get Feature** Retrieves a single feature by id, including its HTML description, current status, timeframe, owner, archived flag, parent reference, and links to the API resource and the Productboard UI. - **Create Feature** Creates a new feature with a required name and an HTML description. Optionally sets status by name, places the feature under a parent in the hierarchy, and assigns an owner by email. - **Update Feature** Updates an existing feature. Only supplied fields change: rename, replace the description, change status by name, reassign the owner, or archive and unarchive. The action this page's human gate watches. ### Components 1 - **List Components** Lists components with cursor-based pagination. Components group related features and can nest under products. Returns id, name, description, parent reference, and links. ### Products 1 - **List Products** Lists the top-level products in the hierarchy with cursor-based pagination. Products hold components and features. Returns id, name, description, and links. ### Companies 1 - **List Companies** Lists companies with cursor-based pagination, optionally filtered by exact name. Companies group the users and notes belonging to an organization, which is what makes segment-level prioritization possible. ### Releases 1 - **List Release Groups** Lists release groups with cursor-based pagination. Release groups organize related releases by product line or cadence, useful for framing roadmap reporting. ### Notes 3 - **List Notes** Lists customer feedback notes with cursor-based pagination, filterable by full-text search, linked company or feature, owner email, or date range. Returns each note's title, content, tags, source, owner, and creation date. - **Get Note** Retrieves a single note by id, including its HTML content, tags, processing state, source, owner, linked company and features, and display URL. - **Create Note** Creates a new note with a required title and HTML content. Optionally attaches the customer's email so the note associates with a company, adds tags, and sets a source URL linking back to the original feedback. ## Frequently Asked Questions ### What can FlowRunner do with Productboard? FlowRunner agents can run List Features, Get Feature, and Create Feature in Productboard, plus 8 more actions. ### Does connecting Productboard to FlowRunner require OAuth? No. Productboard connects to FlowRunner with an API key, no OAuth flow required. ### Can Productboard trigger a FlowRunner workflow automatically? Productboard doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Productboard?** This integration exposes Productboard to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/productboard. Site index: https://flowrunner.ai/llms.txt