[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Triage Productboard feedback and link it to features

> Link new Productboard feedback to the right feature with an importance score and mark it processed, daily, with the unsure ones left for you.

Source: https://cotlet.dev/integrations/productboard-api-mcp-server/triage-customer-feedback

Feedback from calls, emails and the portal piles up on the insights board. Every item still needs someone to read it, pick the quote that matters, link it to a feature and mark it processed.

Cotlet does it in your own Productboard account with list\_feedback, get\_feedback, search\_features, link\_feedback\_to\_feature and mark\_feedback\_processed, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=productboard) [All Productboard tools](https://cotlet.dev/integrations/productboard-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Productboard do this on its own?

Productboard has AI auto-linking, which needs the Enterprise plan with the AI add-on, and its help center says Productboard AI is not available for purchase at this time (checked 22 Oct 2026). API v2 has relationship endpoints that link a note to a feature, and its tokens need a workspace admin on the Pro plan or higher. Nothing applies your own rule about which quote counts and how important it is.

## How you do it in Productboard today

1. A maker opens any insights board in the workspace and clicks a feedback item to open its sidebar.
2. In the feedback body, the maker selects the most relevant text or images and clicks Link to.
3. The maker searches for the idea and picks a feature from the hierarchy, or adds a new feature at the right spot in the hierarchy menu.
4. The maker sets the importance, which adds +1 for unknown importance, +1 for nice-to-have, +2 for important or +3 for critical to the feature.
5. Mark processed in the bottom-right corner of the item takes it out of the queue. For many items, the maker ticks checkboxes and chooses (Un)process in the sidebar.
6. The queue refills every day, and an item left unprocessed looks the same as one nobody has read.

## How to triage Productboard feedback and link it to features

Prompt

```
Go through unprocessed feedback in Productboard. For each item, find the feature it is about, link the most relevant quote with an importance, and mark it processed. Leave the ones you are unsure about for me.
```

1. 01  
### Read the queue  
The agent calls list\_feedback with processed set to false and follows the cursor to the end, so a long weekend is judged as one batch. Each row already shows how many insights the item has, so items linked by a colleague are skipped.
2. 02  
### Read each item in full  
get\_feedback brings the whole text and the company or user. A feedback item without a company or user goes on your list instead of being linked blind, because the customer decides how much a link should weigh.
3. 03  
### Find the feature  
search\_features runs with the product word from the quote. One clear match is linked. Two or more near matches, or none, leave the item for you with the candidates named, because the agent never creates a feature.
4. 04  
### Link the quote with an importance  
link\_feedback\_to\_feature sends the exact sentence as the highlight and one of unknown, nice\_to\_have, important or critical, chosen by the rule in your prompt, for example "critical when the customer names a cancellation". The link can be undone with unlink\_insight, so it does not wait for your OK.
5. 05  
### Mark processed last  
mark\_feedback\_processed runs only after the link went through, so an item that failed to link stays in the queue for the next run.

### What you get back

Example data

```
Unprocessed feedback: 15
Linked and processed 11, e.g. "Export to CSV is too slow" to CSV export, important
Left for you 4:
- "Would love dark mode" (two features match)
- "Call notes, Acme" (no company or user)
```

### Other ways to ask

- Every Friday, link feedback from enterprise customers as critical when it names a deadline.
- Show me unprocessed feedback grouped by the feature it would link to, but link nothing.
- Link only feedback tagged "interview" and leave everything else in the queue.

## What Productboard allows, and what to know first

- Productboard scores each link: +1 for unknown importance, +1 for nice-to-have, +2 for important and +3 for critical.
- Productboard AI auto-linking runs every three hours and skips feedback under 100 characters, and a feature needs both a title and a description before it can be a target.
- Productboard suggests the owner of a feedback item is the person who processes it, and a comment that @-mentions a colleague tells them you did.
- Mark processed is a toggle in Productboard: clicking it again takes the item back to unprocessed.

link\_feedback\_to\_feature and mark\_feedback\_processed change only your own Productboard data and reach no one else, so they run without asking first.

Sources: [Productboard Help: Link feedback to feature ideas via insights](https://support.productboard.com/hc/en-us/articles/360056354514-Link-user-feedback-to-related-feature-ideas-using-insights) · [Productboard Help: Link insights automatically with Productboard AI](https://support.productboard.com/hc/en-us/articles/26949590820627-Link-insights-automatically-with-Productboard-AI) · [Productboard developers: API v2 overview](https://developer.productboard.com/reference/introduction)

## Call link\_feedback\_to\_feature from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/productboard/features/ft_4d7e10/feedbacks/fb_81c2a9/to-feature/link \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"quote":"Exporting 50,000 rows to CSV takes over ten minutes and then times out.","importance":"important"}'
```

Example response

```
{
"feedback_id": "fb_81c2a9",
"feature": {
"id": "ft_4d7e10",
"name": "CSV export"
},
"quote": "Exporting 50,000 rows to CSV takes over ten minutes and then times out.",
"importance": "important",
"linked": true
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is productboard\_write → link\_feedback\_to\_feature. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/productboard-api-mcp-server.md#automations)

## Productboard tools this automation uses

__Cotlet Productboard tools used to triage Productboard feedback and link it to features__
| Tool | Parameters |
| --------------------------- | -------------------------------------------- |
| list\_feedback | processed, query, cursor |
| get\_feedback | feedback\_id |
| search\_features | query, status, cursor |
| link\_feedback\_to\_feature | feedback\_id, feature\_id, quote, importance |
| mark\_feedback\_processed | feedback\_id, processed |

[All 12 Productboard tools with descriptions](https://cotlet.dev/integrations/productboard-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Productboard to Cotlet?

Yes. You sign in to Productboard yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Productboard once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Productboard automations

- [Log customer calls as Productboard feedback](https://cotlet.dev/integrations/productboard-api-mcp-server/log-customer-calls-as-feedback.md)
- [Update Productboard feature statuses after a release](https://cotlet.dev/integrations/productboard-api-mcp-server/update-feature-statuses-after-release.md)
- [Productboard API and MCP server: every tool](https://cotlet.dev/integrations/productboard-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Productboard.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Productboard.

[Sign up free](https://cotlet.dev/app/signup?app=productboard)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.