Customer feedback, ideas, conversations, and insights collected across your product discovery process. Notes are the primary way feedback enters Productboard.
What is a Note?
A Note is a piece of customer feedback, an idea, a conversation, or an insight captured in Productboard. When you collect feedback from a stakeholder — whether through a support tool, sales call, or survey — that feedback is packaged into a note. Notes are the primary entry point for voice-of-the-customer data.
Notes can be linked to features to quantify demand and inform prioritization. When you link a note to a feature, that link is called an insight. Insights are how Productboard connects raw customer feedback to specific feature ideas, letting you see exactly how much demand exists for each feature. Notes can also be linked to companies and users to track which customers care about what.
Note types
Productboard supports three note types:
| Type | API value | Description |
|---|---|---|
| Text Note | textNote | Standard freeform note for capturing feedback, ideas, or internal observations. The most common type. |
| Conversation Note | conversationNote | Multi-part threaded content representing a dialogue — for example, a support ticket conversation between a user and an agent. Each part has its own timestamp and author. |
| Opportunity Note | opportunityNote | Structured feedback linked to sales or market opportunities, with key-value fields for amounts, dates, and descriptions. Typically imported from CRMs like Salesforce. Currently read-only via API. |
When to use it
- Feedback ingestion — Push customer feedback from support tools (Zendesk, Intercom), CRMs (Salesforce, HubSpot), or custom channels into Productboard.
- Feedback export — Pull notes for analysis in BI tools or data warehouses.
- Automated tagging — Read notes and update their tags or status programmatically based on content analysis.
- Customer intelligence — Query notes linked to a specific company or user to understand their needs before a meeting.
- Insight creation — Link notes to features to create insights that quantify demand.
Key fields
| Field | Description |
|---|---|
name | Title of the note |
content | The note body (rich text for text notes, structured parts for conversations) |
tags | Labels for categorizing notes |
owner | The member who owns this note |
creator | The member who created this note |
processed | Whether the note has been reviewed and processed |
archived | Whether the note has been archived |
source | Origin metadata — external ID, system name, and source URL |
Field availability depends on your workspace configuration. Use the Note Configuration endpoint to discover available fields.
Relationships
Notes support these relationship types:
| Relationship | Description |
|---|---|
customer | The company or user this feedback came from (by ID or email) |
hierarchyItem | Features, components, or other product hierarchy entities this note is linked to — each link creates an "insight" |
link | External URLs associated with this note |
Manage relationships via PATCH /notes/{id}/relationships/{relationshipType}.
Related objects
- Feature — features that this note provides evidence for
- Company — the company this feedback is associated with
- User — the individual user who provided the feedback
- Member — the workspace member who owns or created the note