> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atako.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Productboard

> Connect Productboard to your Atako agents — 11 read and 3 write actions.

Let your agents read your product hierarchy (products, components, features, objectives, releases), capture customer feedback as notes, and create or update features in Productboard.

## Connection

* **Authentication**: API key (Public API access token).

<Note>
  Productboard → Settings → Integrations → Public APIs → Access Token → click the + icon to generate a token, then copy it (it is shown only once). The token acts with the rights of the workspace; there are no scopes to choose. Public API access is not available on every plan (not on Essentials): see productboard.com/pricing.

  See [Productboard's documentation](https://developer.productboard.com/reference/api-token).
</Note>

## Read actions (11)

| Action | Description |
| - | - |
| `get_entity` | Read one entity by id (a feature, component, product, objective, release, company or end user): all its fields and relationships. id: UUID from any list\_\* action. |
| `get_note` | Read one note by id: title, content, tags, owner, customer and linked features. id: UUID from list\_notes. |
| `list_companies` | List customer companies (paginated). Optional filter: name (string). page\_cursor: string, the pageCursor value found in links.next of the previous page (omit for the first page). |
| `list_components` | List components (paginated). Optional filters: name (string), parent\_id (UUID of the parent product or component). Read one with get\_entity. page\_cursor: string, the pageCursor value found in links.next of the previous page (omit for the first page). |
| `list_feature_statuses` | List the statuses a feature can take (id and name). Use their id as status\_id or their exact name as status\_name in create\_feature / update\_feature. page\_cursor: string, the pageCursor value found in links.next of the previous page (omit for the first page). |
| `list_features` | List features (paginated). Optional filters: name (string), status\_name (string, exact status name) or status\_id (UUID, see list\_feature\_statuses), parent\_id (UUID of the parent component/product/feature), owner\_email (string), archived (boolean). page\_cursor: string, the pageCursor value found in links.next of the previous page (omit for the first page). |
| `list_notes` | List feedback notes, newest first (paginated). Optional filters: archived (boolean), processed (boolean), owner\_email (string), created\_from / created\_to / updated\_from / updated\_to (ISO-8601 date-time, e.g. "2026-09-01T00:00:00Z", inclusive). page\_cursor: string, the pageCursor value found in links.next of the previous page (omit for the first page). |
| `list_objectives` | List objectives (paginated). Optional filter: name (string). page\_cursor: string, the pageCursor value found in links.next of the previous page (omit for the first page). |
| `list_products` | List products (top of the hierarchy, paginated). Optional filter: name (string). page\_cursor: string, the pageCursor value found in links.next of the previous page (omit for the first page). |
| `list_releases` | List releases (paginated). Optional filter: name (string). page\_cursor: string, the pageCursor value found in links.next of the previous page (omit for the first page). |
| `list_users` | List end users — your customers who give feedback, not Productboard members (paginated). Optional filter: name (string). page\_cursor: string, the pageCursor value found in links.next of the previous page (omit for the first page). |

## Write actions (3)

| Action | Description |
| - | - |
| `create_feature` | Create a feature. Arguments: name (string, 1-255 chars, required); parent\_id (UUID of the parent component or product, required — see list\_components / list\_products); description (string, HTML such as "\<p>text\</p>", optional); status\_name (string, exact name of an existing status, optional) OR status\_id (UUID from list\_feature\_statuses, optional) — not both; owner\_email (string, email of a Productboard member, optional). Returns the new feature id. |
| `create_note` | Create a text note (a piece of customer feedback). Arguments: title (string, 1-255 chars, required); content (string, HTML such as "\<p>The export is too slow\</p>", required); customer\_email (string, email of the customer end user the feedback comes from — Productboard looks that user up by email, optional); tags (array of tag-name strings, e.g. \["onboarding", "export"], optional); feature\_ids (array of feature UUIDs from list\_features to link the note to, optional, max 20). Returns the new note id. |
| `update_feature` | Update a feature. Arguments: id (UUID of the feature, required — see list\_features); then at least one of: name (string, 1-255 chars); description (string, HTML such as "\<p>text\</p>", replaces the whole description); status\_name (string, exact name of an existing status) OR status\_id (UUID from list\_feature\_statuses) — not both; owner\_email (string, email of a Productboard member); archived (boolean). Omitted fields are left unchanged. |

## Permissions

Every action above must be explicitly granted to an agent before it can be used. See [Permissions](/integrations/permissions) for the grant model and [Security](/integrations/security) for how credentials are protected.

***

*Last reviewed against the provider API: September 2026.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.