Productboard connector for AI agents

Tools your product management agent reaches for on Productboard, scoped per user.

CALL ANY TOOL

28 tools for product management in Productboard: create, update, and search notes and entities such as features and initiatives, link feedback to features, and look up members and teams.

productboard_entities_list

List entities

List Productboard entities such as features, components, products, initiatives, objectives, key results, releases, companies and users, filtered by type, name, owner, status, team, parent, archived state or source record. Returns a page of entities with id, type, fields and links, plus links.next whose pageCursor fetches the next page. Use productboard_entities_list to browse with simple filters. Use productboard_entities_search for many ids, date ranges or custom-field filters. Use productboard_entity_get for one entity.

Parameters

Name

Type

Required

Description

archived

boolean

Optional

Filter by archived state. Example: false

name

string

Optional

Only return entities with this name. Example: Dark mode

owner_email

string

Optional

Only return entities owned by the member with this email. Needs the members_pii:read scope. Example: john@doe.com

owner_id

string

Optional

Only return entities owned by this member UUID. Example: 923e4567-e89b-12d3-a456-426614174008

page_cursor

string

Optional

Cursor for the next page of entities. Copy the pageCursor value from links.next of the previous response. Leave empty for the first page. Example: eyJvZmZzZXQiOjEwMH0

parent_id

string

Optional

Only return entities whose parent is this entity UUID, e.g. features of a component. Example: 223e4567-e89b-12d3-a456-426614174001

return_fields

array

Optional

Limit which entity fields are returned. Pass field ids such as name, owner, tags or a custom field UUID; pass ["all"] to also include empty fields. Leave empty to return all non-empty fields. Do not combine "all" with specific fields. Example: ["name", "owner"]

source_record_id

string

Optional

Only return entities whose metadata.source.recordId matches. Example: A-1

source_system

string

Optional

Only return entities whose metadata.source.system matches. Example: sfdc

status_id

string

Optional

Only return entities with this status UUID. Applies to types with a status, such as feature and initiative. Example: 447eb060-2a7e-4d1e-9d59-322a11e0fdb0

status_name

string

Optional

Only return entities with this status name, e.g. In Progress. Applies to types with a status. Example: In Progress

team_id

string

Optional

Only return entities assigned to this team UUID. Do not combine with team_name. Example: 95db5914-36b0-45e9-8f6d-7f11a950ac1d

team_name

string

Optional

Only return entities assigned to the team with this name. Do not combine with team_id. Example: Product Team

types

array

Optional

Only return entities of these types: product, component, feature, subfeature, initiative, objective, keyResult, release, releaseGroup, company or user (the set depends on the workspace; productboard_entity_configurations_list lists it). Example: ["feature"]

productboard_entities_search

Search entities

Search Productboard entities with a structured filter: type, ids, created or updated date range, name, archived state, status, owner, team, parent, source record and custom field values. Returns a page of matching entities with id, type, fields and links.next, whose pageCursor fetches the next page. Use productboard_entities_search for many ids, date ranges or custom-field filters. Use productboard_entities_list for simple filters. Use productboard_entity_get for one entity.

Parameters

Name

Type

Required

Description

archived

boolean

Optional

Filter by archived state. Example: false

created_from

string

Optional

Only match entities created on or after this ISO 8601 date-time. Example: 2026-01-01T00:00:00Z

created_to

string

Optional

Only match entities created on or before this ISO 8601 date-time. Example: 2026-03-31T23:59:59Z

custom_field_filters

object

Optional

Filters on other fields, keyed by field id (a predefined id such as domain or a custom field UUID). A text field takes contains, a number or date field takes eq, a single-select field takes id or name, a multi-select field takes any or all with a list of options, and any field takes isSet on its own. Requires types. At most 25 entries. Example: {"domain": {"contains": "acme.com"}}

entity_ids

array

Optional

Only match entities with these UUIDs. Example: ["123e4567-e89b-12d3-a456-426614174000"]

name

string

Optional

Only match entities with this name. Example: Dark mode

owner_emails

array

Optional

Only match entities owned by one of these member emails. Needs the members_pii:read scope. Example: ["john@doe.com"]

owner_ids

array

Optional

Only match entities owned by one of these member UUIDs. Example: ["923e4567-e89b-12d3-a456-426614174008"]

page_cursor

string

Optional

Cursor for the next page of results. Copy the pageCursor value from links.next of the previous response. Leave empty for the first page. Example: eyJvZmZzZXQiOjEwMH0

parent_ids

array

Optional

Only match entities whose parent is one of these entity UUIDs. Example: ["223e4567-e89b-12d3-a456-426614174001"]

return_fields

array

Optional

Limit which fields each result returns, e.g. name, status, owner; pass ["all"] to include empty fields too. Example: ["name", "status"]

source_record_id

string

Optional

Only match entities with this source record id. Example: PROJ-456

source_system

string

Optional

Only match entities whose source system matches. Example: Jira

status_names

array

Optional

Only match entities in one of these statuses, by name. Example: ["In Progress", "At Risk"]

team_names

array

Optional

Only match entities assigned to any of these teams, by name. Example: ["Product Team"]

types

array

Optional

Entity types to search: product, component, feature, subfeature, initiative, objective, keyResult, release, releaseGroup, company or user (the set depends on the workspace; productboard_entity_configurations_list lists it). Searching one type at a time is the documented norm, and custom field filters require a type. Example: ["feature"]

updated_from

string

Optional

Only match entities updated on or after this ISO 8601 date-time. Example: 2026-01-01T00:00:00Z

updated_to

string

Optional

Only match entities updated on or before this ISO 8601 date-time. Example: 2026-03-31T23:59:59Z

productboard_entity_configuration_get

Get entity configuration

productboard_entity_configurations_list

List entity configurations

productboard_entity_create

Create entity

Create a Productboard entity of a given type, such as a feature, component, initiative, objective, release, company or user, with its name, description, owner, status, timeframe, teams, tags and parent. Returns the new entity's id and links. Use productboard_entity_create to add a new item. Use productboard_entity_update to change an existing one. Run productboard_entity_configuration_get first to learn which fields the type requires (for example, features need a parent).

Parameters

Name

Type

Required

Description

name

string

Required

Name of the entity, up to 255 characters. Example: Dark mode

type

string

Required

Entity type to create: product, component, feature, subfeature, initiative, objective, keyResult, release, releaseGroup, company or user (the set depends on the workspace; productboard_entity_configurations_list lists it). Example: feature

additional_fields

object

Optional

Other fields to set, keyed by field id as listed by productboard_entity_configuration_get: predefined ids such as domain for companies or a custom field UUID. Example: {"faa1d59a-d55f-4ad2-b1d3-5b888123873b": 120}

archived

boolean

Optional

Set true to archive the entity or false to keep or make it active. Example: false

description

string

Optional

Rich-text description. Wrap text in supported HTML tags such as , <b>, <ul>/<li>, <h1>/<h2>; plain text without a tag is rejected. Example: <p>Let users switch the app to a dark theme.

owner_email

string

Optional

Email of the member who owns the entity. Used only when owner_id is empty. Example: john@doe.com

owner_id

string

Optional

UUID of the member who owns the entity. Use owner_id or owner_email, not both. Example: 923e4567-e89b-12d3-a456-426614174008

parent_id

string

Optional

UUID of the parent entity, e.g. the component or product a feature belongs to, or the feature a subfeature belongs to. Required for types that must have a parent. Example: 223e4567-e89b-12d3-a456-426614174001

source_record_id

string

Optional

Id of the record in the external system, stored as metadata.source.recordId. Example: PROJ-456

source_system

string

Optional

Name of the external system this entity is synced from, stored as metadata.source.system. Example: Jira

source_url

string

Optional

URL of the record in the external system, stored as metadata.source.url. Example: https://jira.example.com/browse/PROJ-456

status_id

string

Optional

Status to set, by UUID. Used instead of status_name. Example: 447eb060-2a7e-4d1e-9d59-322a11e0fdb0

status_name

string

Optional

Status to set, by name, e.g. In Progress. Must match a status configured for this entity type. Use status_name or status_id. Example: In Progress

tags

array

Optional

Tag names to set on the entity. Example: ["Q4", "Launch"]

team_names

array

Optional

Teams to assign, by exact team name. Example: ["Product Team"]

timeframe_end

string

Optional

Timeframe end date (yyyy-MM-dd). Example: 2026-12-31

timeframe_granularity

string

Optional

How the timeframe is shown: year, quarter, month or day. Example: month. One of: `year`, `quarter`, `month`, `day`.

timeframe_start

string

Optional

Timeframe start date (yyyy-MM-dd). Example: 2026-10-01

productboard_entity_field_values_list

List entity field values

productboard_entity_get

Get entity

productboard_entity_parent_set

Set entity parent

productboard_entity_relationship_create

Create entity relationship

productboard_entity_relationships_list

List entity relationships

productboard_entity_update

Update entity

Update fields of an existing Productboard entity, such as its name, description, owner, status, timeframe, teams, tags, archived state or custom fields. Returns the entity's id and links. Use productboard_entity_update to edit an entity. Use productboard_entity_parent_set to move it under another parent. Values replace the current ones; use patch_operations to add or remove single list items.

Parameters

Name

Type

Required

Description

entity_id

string

Required

UUID of the entity to update. Get it from productboard_entities_list or productboard_entities_search. Example: 123e4567-e89b-12d3-a456-426614174000

additional_fields

object

Optional

archived

boolean

Optional

Set true to archive the entity or false to keep or make it active. Example: false

description

string

Optional

Rich-text description. Wrap text in supported HTML tags such as , <b>, <ul>/<li>, <h1>/<h2>; plain text without a tag is rejected. Example: <p>Let users switch the app to a dark theme.

name

string

Optional

New name, up to 255 characters. Example: Dark mode (mobile)

owner_email

string

Optional

Email of the member who owns the entity. Used only when owner_id is empty. Example: john@doe.com

owner_id

string

Optional

UUID of the member who owns the entity. Use owner_id or owner_email, not both. Example: 923e4567-e89b-12d3-a456-426614174008

patch_operations

array

Optional

Granular changes sent instead of the field inputs: each operation has op (set, addItems, removeItems or clear), path (a field id such as tags, teams or a custom field UUID) and, except for clear, a value. Productboard rejects a request that mixes field values and patch operations, so when this is set the other field inputs are ignored. Example: [{"op": "addItems", "path": "tags", "value": [{"name": "Q1 2027"}]}]

source_record_id

string

Optional

Id of the record in the external system, stored as metadata.source.recordId. Example: PROJ-456

source_system

string

Optional

Name of the external system this entity is synced from, stored as metadata.source.system. Example: Jira

source_url

string

Optional

URL of the record in the external system, stored as metadata.source.url. Example: https://jira.example.com/browse/PROJ-456

status_id

string

Optional

Status to set, by UUID. Used instead of status_name. Example: 447eb060-2a7e-4d1e-9d59-322a11e0fdb0

status_name

string

Optional

Status to set, by name, e.g. In Progress. Must match a status configured for this entity type. Use status_name or status_id. Example: In Progress

tags

array

Optional

Tag names to set on the entity. Example: ["Q4", "Launch"]

team_names

array

Optional

Teams to assign, by exact team name. Example: ["Product Team"]

timeframe_end

string

Optional

Timeframe end date (yyyy-MM-dd). Example: 2026-12-31

timeframe_granularity

string

Optional

How the timeframe is shown: year, quarter, month or day. Example: month. One of: `year`, `quarter`, `month`, `day`.

timeframe_start

string

Optional

Timeframe start date (yyyy-MM-dd). Example: 2026-10-01

productboard_member_get

Get member

productboard_members_list

List members

productboard_members_search

Search members

productboard_note_configuration_get

Get note configuration

productboard_note_configurations_list

List note configurations

productboard_note_create

Create note

Create a note (a piece of customer feedback) in Productboard, optionally attributed to a customer, linked to features and tagged. Returns the new note's id and links. Use productboard_note_create to capture new feedback. Use productboard_note_update to change an existing note. Opportunity notes cannot be created through the API.

Parameters

Name

Type

Required

Description

name

string

Required

Title of the note, up to 255 characters. Example: Customer asks for dark mode

additional_fields

object

Optional

Other note fields to set, keyed by field id as listed by productboard_note_configuration_get, for example archived, processed or a custom field. Example: {"processed": false}

content

string

Optional

Body of a textNote. HTML is accepted; the Notes API keeps semantic tags and strips styling. Example: Customer reported slow loading on the mobile app.

conversation_parts

array

Optional

Messages of a conversationNote, oldest first. Each message needs an externalId (its id in your system), authorType (customer or agent), content and an ISO 8601 timestamp; authorName is optional. Example: [{"externalId": "msg-1", "authorType": "customer", "authorName": "John Doe", "content": "Hello", "timestamp": "2026-10-01T11:00:00Z"}]

creator_email

string

Optional

Email of the workspace member to record as the note's creator. Example: john.doe@example.com

customer_email

string

Optional

Email of the customer user the feedback came from, used instead of customer_id. Productboard looks up the user by email. Example: john@acme.com

customer_id

string

Optional

UUID of the user or company entity the feedback came from. Set customer_type to match. Leave empty if you use customer_email or want no customer. Example: 223e4567-e89b-12d3-a456-426614174001

customer_type

string

Optional

Entity type of customer_id: user or company. Defaults to user. Ignored when customer_email is used. Example: company. One of: `user`, `company`. Default: `user`.

linked_entity_ids

array

Optional

UUIDs of features or other entities to link the note to. Example: ["223e4567-e89b-12d3-a456-426614174001"]

owner_email

string

Optional

Email of the workspace member who owns the note. Used only when owner_id is empty. Example: jane.doe@example.com

owner_id

string

Optional

UUID of the workspace member who owns the note. Use owner_id or owner_email, not both. Example: 923e4567-e89b-12d3-a456-426614174008

source_record_id

string

Optional

Id of the feedback record in the external system, stored as metadata.source.recordId. Example: ticket-12345

source_system

string

Optional

Name of the external system the feedback came from, stored as metadata.source.system. Example: support

source_url

string

Optional

URL of the feedback record in the external system, stored as metadata.source.url. Example: https://support.example.com/ticket/12345

tags

array

Optional

Tag names to put on the note. Tags that do not exist yet are created. Example: ["mobile", "performance"]

type

string

Optional

Note type. textNote for plain feedback; conversationNote for a chat or email thread passed in conversation_parts. Defaults to textNote. Example: textNote. One of: `textNote`, `conversationNote`. Default: `textNote`.

productboard_note_customer_set

Set note customer

productboard_note_get

Get note

productboard_note_relationship_create

Create note relationship

productboard_note_relationships_list

List note relationships

productboard_note_update

Update note

Update fields of an existing Productboard note: name, content, owner, tags, archived or processed state. Returns the note's id and links. Use productboard_note_update to edit a note. Use productboard_note_relationship_create or productboard_note_customer_set to change what it is linked to. Notes whose content is highlighted into features cannot have content changed.

Parameters

Name

Type

Required

Description

note_id

string

Required

UUID of the note to update. Get it from productboard_notes_list or productboard_notes_search. Example: 123e4567-e89b-12d3-a456-426614174000

add_tags

array

Optional

Tag names to add, keeping existing tags. Example: ["urgent"]

archived

boolean

Optional

Set true to archive the note or false to unarchive it. Example: true

clear_owner

boolean

Optional

Set true to remove the owner. Do not combine with owner_id or owner_email. Example: true

content

string

Optional

New body of a textNote; replaces the existing content. HTML is accepted. Example: Updated feedback text.

name

string

Optional

New title, up to 255 characters. Example: Customer asks for dark mode (mobile)

owner_email

string

Optional

Email of the member to make the owner. Used only when owner_id is empty. Example: jane.doe@example.com

owner_id

string

Optional

UUID of the member to make the owner. Use owner_id or owner_email, not both. Example: 923e4567-e89b-12d3-a456-426614174008

patch_operations

array

Optional

Extra patch operations applied after the ones built from the other inputs, for fields they do not cover. Each operation has op (set, clear, addItems or removeItems), path (the field id) and, except for clear, a value. Example: [{"op": "addItems", "path": "content", "value": [{"externalId": "msg-2", "authorType": "agent", "content": "Thanks!", "timestamp": "2026-10-02T09:00:00Z"}]}]

processed

boolean

Optional

Set true to mark the note processed or false to mark it unprocessed. Example: true

remove_tags

array

Optional

Tag names to remove, keeping the others. Example: ["triage"]

tags

array

Optional

Replace all tags with exactly these tag names. Do not combine with add_tags or remove_tags. Example: ["mobile", "q3"]

productboard_notes_list

List notes

List notes (customer feedback) in the Productboard workspace, newest first, optionally filtered by type, owner, creator, archived or processed state, source record, or created/updated date range. Returns a page of notes with id, type, fields (name, content, owner, tags, archived, processed) and links.next, whose pageCursor fetches the next page. Use productboard_notes_list to browse or filter by simple fields. Use productboard_notes_search for a full-text query or to filter by linked customer or feature. Use productboard_note_get for one note by id.

Parameters

Name

Type

Required

Description

archived

boolean

Optional

Filter by archived state. true returns only archived notes; false returns processed and unprocessed notes that are not archived. Leave empty to include all. Example: false

created_from

string

Optional

Only return notes created on or after this ISO 8601 date-time (inclusive). Example: 2026-01-01T00:00:00Z

created_to

string

Optional

Only return notes created on or before this ISO 8601 date-time (inclusive). Must not be earlier than created_from. Example: 2026-03-31T23:59:59Z

creator_email

string

Optional

Only return notes created by the workspace member with this email. Needs the members_pii:read scope. Example: jane.doe@example.com

creator_id

string

Optional

Only return notes created by the workspace member with this UUID (from productboard_members_list). Example: e23e4567-e89b-12d3-a456-426614174013

owner_email

string

Optional

Only return notes owned by the workspace member with this email. Needs the members_pii:read scope. Example: john.doe@example.com

owner_id

string

Optional

Only return notes owned by the workspace member with this UUID (from productboard_members_list). Example: 923e4567-e89b-12d3-a456-426614174008

page_cursor

string

Optional

Cursor for the next page. Copy the pageCursor value from links.next of the previous response. Leave empty for the first page. Example: eyJvZmZzZXQiOjEwMH0

processed

boolean

Optional

Filter by processed state. true returns processed notes; false returns unprocessed and archived notes (archived notes always report processed=false). Leave empty to include all. Example: false

return_fields

array

Optional

Limit which note fields are returned. Pass field ids such as name, content, tags, owner; pass ["all"] to also include empty fields. Leave empty to return all non-empty fields. Do not combine "all" with specific fields. Example: ["name", "tags"]

source_record_id

string

Optional

Only return notes whose metadata.source.recordId matches this external record id. Combine with source_system. Example: ticket-12345

source_system

string

Optional

Only return notes whose metadata.source.system matches this external system name. Example: intercom

types

array

Optional

Only return notes of these types. Allowed values: textNote, conversationNote, opportunityNote. Example: ["textNote", "conversationNote"]

updated_from

string

Optional

Only return notes updated on or after this ISO 8601 date-time (inclusive). Example: 2026-01-01T00:00:00Z

updated_to

string

Optional

Only return notes updated on or before this ISO 8601 date-time (inclusive). Must not be earlier than updated_from. Example: 2026-03-31T23:59:59Z

productboard_notes_search

Search notes

Search Productboard notes with a full-text query and structured filters, including the linked customer (user or company) and linked features. Returns a page of matching notes with id, type, fields and links.next, whose pageCursor fetches the next page. Use productboard_notes_search for text queries or customer and feature filters. Use productboard_notes_list for simple field filters. Use productboard_note_get for one note by id.

Parameters

Name

Type

Required

Description

archived

boolean

Optional

Filter by archived state. Example: false

created_from

string

Optional

Only match notes created on or after this ISO 8601 date-time. Example: 2026-01-01T00:00:00Z

created_to

string

Optional

Only match notes created on or before this ISO 8601 date-time. Example: 2026-03-31T23:59:59Z

creator_emails

array

Optional

Only match notes created by one of these member emails. Needs the members_pii:read scope. Example: ["jane.doe@example.com"]

creator_ids

array

Optional

Only match notes created by one of these member UUIDs. Example: ["923e4567-e89b-12d3-a456-426614174008"]

customer_ids

array

Optional

Only match notes whose customer is one of these user or company entity UUIDs. Example: ["223e4567-e89b-12d3-a456-426614174001"]

linked_entity_ids

array

Optional

Only match notes linked to one of these feature or other entity UUIDs. Example: ["223e4567-e89b-12d3-a456-426614174001"]

note_ids

array

Optional

Only match notes with these UUIDs (up to 100). Example: ["123e4567-e89b-12d3-a456-426614174000"]

owner_emails

array

Optional

Only match notes owned by one of these member emails. Needs the members_pii:read scope. Example: ["john.doe@example.com"]

owner_ids

array

Optional

Only match notes owned by one of these member UUIDs. Example: ["923e4567-e89b-12d3-a456-426614174008"]

page_cursor

string

Optional

Cursor for the next page of results. Copy the pageCursor value from links.next of the previous response. Leave empty for the first page. Example: eyJvZmZzZXQiOjEwMH0

processed

boolean

Optional

Filter by processed state. Example: true

query

string

Optional

Full-text query matched against note content, up to 255 characters. Example: onboarding

return_fields

array

Optional

Limit which note fields each result returns, e.g. name, content, owner, tags. Leave empty for all non-empty fields. Example: ["name", "content"]

source_record_id

string

Optional

Only match notes with this source record id. Use together with source_system. Example: ticket-12345

source_system

string

Optional

Only match notes whose source system matches, e.g. intercom or zendesk. Example: intercom

tags

array

Optional

Only match notes with at least one of these tag names. Example: ["important"]

types

array

Optional

Only match notes of these types. Allowed values: textNote, conversationNote, opportunityNote. Example: ["textNote"]

updated_from

string

Optional

Only match notes updated on or after this ISO 8601 date-time. Example: 2026-01-01T00:00:00Z

updated_to

string

Optional

Only match notes updated on or before this ISO 8601 date-time. Example: 2026-03-31T23:59:59Z

productboard_team_get

Get team

productboard_team_members_list

List team members

productboard_teams_list

List teams

productboard_teams_search

Search teams

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Productboard tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["productboard"], toolNames: [
    "productboard_notes_search",
    "productboard_entities_search",
    "productboard_note_relationship_create"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Link every SSO note from this month to the Enterprise SSO feature" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["productboard"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Link every SSO note from this month to the Enterprise SSO feature" }],
  tools,
});

// Execute the tool call with the user's vaulted Productboard OAuth token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["productboard"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Link every SSO note from this month to the Enterprise SSO feature" }],
  tools,
});

// Tool call runs with the user's vaulted Productboard OAuth token
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["productboard"] }, pageSize: 100,
});

const agent = new Agent({
  name: "product_agent",
  model: "gemini-2.5-pro",
  instruction: "Productboard tools scoped to this user",
  tools,
});

await agent.run("Link every SSO note from this month to the Enterprise SSO feature");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Productboard tool. Click to copy, paste into your agent, done.

Feedback

Copy the prompt

Copied

Create a note from this customer call summary for Acme Corp.

Copy the prompt

Copied

Find notes from the last 30 days that mention SSO.

Copy the prompt

Copied

Link the Acme note to the Enterprise SSO feature.

Features

Copy the prompt

Copied

List features under the Billing component.

Copy the prompt

Copied

Create a feature called Usage alerts under the Billing component.

Copy the prompt

Copied

Set the status of the Dark mode feature to In progress.

Team

Copy the prompt

Copied

List the members of the Platform team.

Copy the prompt

Copied

Find the workspace member with the email dana@acme.com.

Copy the prompt

Copied

List the teams in our workspace.

SEE HOW AUTH WORKS

Each user signs in to Productboard once, and Scalekit stores and refreshes their tokens. Tokens stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Productboard

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Productboard

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Productboard

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Productboard

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other project management and product connectors.

GTM and RevOps Teams

Competitive intelligence briefing agent

Scans Gong calls for competitor mentions, matches each one to its Notion battlecard, and DMs every affected rep a single Slack digest per cycle. Every call runs as the PMM who owns the briefing, never a shared bot.

Support and Ops Teams

Support triage agent

Fetches new Zendesk tickets, classifies them by type and urgency, searches the Notion knowledge base for an answer, and routes what it cannot resolve to Slack. Every call runs on the support agent's own delegated OAuth.

Engineering Teams

Engineering standup agent

Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Productboard token looks fine in a demo. In production every note and feature update looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Productboard today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Productboard as the user or through a shared service account?

As the user. Each user signs in to Productboard once, and Scalekit stores and refreshes their tokens. Notes and feature changes the agent makes are attributed to that user in your audit trail, not a shared service account.

Where is the Productboard OAuth token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Productboard?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example the list and search tools without productboard_entity_update or productboard_note_create. No Productboard tool deletes data. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Productboard access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

What is a Productboard entity?

Entities are the items in your product hierarchy, such as features, components, products, initiatives, and objectives. productboard_entity_configurations_list shows which entity types your workspace has, and productboard_entity_create and productboard_entity_update take the type and its fields.