At a glance
- Availability: Experimental (how to enable).
- Auth: OAuth 2.0.
- Connection: A user authorizes the connection in the provider’s consent screen.
- Scopes:
notes:read,notes:write,entities:read,entities:write. - Docs: https://developer.productboard.com/reference/oauth-authorization-code
Credentials
Set these per environment. See Connect an integration. With a managed OAuth app, Connect works without these variables; set them to use your own OAuth app instead.Setup
- Get a Productboard workspace: Sign up at https://www.productboard.com (a free trial workspace works for testing). Public API access requires a plan with API access enabled.
- Register an OAuth2 application: Follow the developer documentation at https://developer.productboard.com/reference/oauth-authorization-code to register your OAuth2 client and obtain a client ID and secret. Set the redirect URI to your app’s /api/auth/productboard/callback URL.
- Set environment variables: Add PRODUCTBOARD_CLIENT_ID and PRODUCTBOARD_CLIENT_SECRET to your .env.
- Verify access: Complete the OAuth flow, then run List Entities with type=feature.
- Tools target the Productboard REST API v2 (https://api.productboard.com/v2), which does not require the X-Version header used by the legacy v1 API
- Access tokens expire after 24 hours; refresh tokens expire 180 days after issue or 60 minutes after use
- Features, components, and initiatives are all ‘entities’ in v2 - filter with the type parameter
Tools
| Tool | Access | Description |
|---|---|---|
| List Notes | Read | List customer feedback notes in the Productboard workspace |
| Get Note | Read | Get a Productboard note by ID |
| Create Note | Write | Create a feedback note in Productboard |
| List Entities | Read | List product hierarchy entities (features, components, initiatives, releases, etc.) |
| Get Entity | Read | Get a hierarchy entity (e.g. a feature) by ID |
| Create Entity | Write | Create a hierarchy entity such as a feature or initiative |
| Update Entity | Write | Update fields of a hierarchy entity (e.g. rename a feature or change its status) |
Example prompts
- Create a Productboard note capturing this customer feedback with a clear title.
- List the features in my Productboard workspace and summarize their statuses.