Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Productboard

Productboard is a product management tool that helps you manage your product roadmap and features.

CategoryProductivity
Authenticationcustom
Version0.1.8
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Productboard with Flows360

Productboard is a product management tool that helps you manage your product roadmap and features.

Use the Productboard connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 4 actions and 3 triggers.

Available actions

  • Create Feature
  • Create Note
  • Update Feature
  • Get Feature

Available triggers

  • New Feature
  • New Note
  • Updated Feature

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Productboard
  • Package: @activepieces/piece-productboard@0.1.8
  • Exact artifact digest: sha256:f068e071bb4b0f72f29e38fecde6a4792240e000d075e0873f93678a082a76e0
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Feature (create_feature), Create a new feature in Productboard Classification: read.
  • Create Note (create_note), Creates a new note in Productboard Classification: read.
  • Update Feature (update_feature), Updates an existing feature in Productboard. Classification: read.
  • Get Feature (get_feature), Get an existing feature in Productboard Classification: read.

Trigger contracts

  • New Feature, webhook.
  • New Note, webhook.
  • Updated Feature, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects7
Supported actions4
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Feature Yes No Create a new feature in Productboard
Create Note Yes No Creates a new note in Productboard
Update Feature Yes No Updates an existing feature in Productboard.
Get Feature Yes No Get an existing feature in Productboard
New Feature Yes No webhook trigger declared by the pinned package.
New Note Yes No webhook trigger declared by the pinned package.
Updated Feature Yes No webhook trigger declared by the pinned package.

Supported actions

Create Feature · Read

Create a new feature in Productboard

create_feature · Risk: low · Retry: safe

Inputs

  • name · string · Required, Name of the feature
  • description · string · Required, Description of the feature
  • type · string · Required, Type of the feature
  • status · string · Required, Current status of the feature
  • parent_type · object · Required
  • parent_id · string · Required
  • archived · boolean · Optional, A flag denoting if the feature is archived. If null, it will default to `false`.
Create Note · Read

Creates a new note in Productboard

create_note · Risk: low · Retry: safe

Inputs

  • title · string · Required, Title of the feedback note
  • content · string · Required, HTML-encoded rich text content of the feedback note
  • user_email · string · Optional, Email address of a user to be attached to the note. This field can't be combined with `Company Domain`.
  • company_domain · string · Optional, Domain of a company the note should be linked to. This field can't be combined with `User Email`.
  • display_url · string · Optional, URL where the external entity can be accessed.
  • source_origin · string · Optional, A unique string identifying the external system from which the data came.
  • source_record_id · string · Optional, The unique id of the record in the origin system.
  • tags · array · Optional, A set of tags for categorizing the note.
Update Feature · Read

Updates an existing feature in Productboard.

update_feature · Risk: low · Retry: safe

Inputs

  • feature_id · string · Required, The feature to select.
  • name · string · Optional, New name for the feature.
  • description · string · Optional, New description for the feature.
  • status · string · Optional, Current status of the feature
  • archived · boolean · Optional, Whether the feature is archived.
Get Feature · Read

Get an existing feature in Productboard

get_feature · Risk: low · Retry: safe

Inputs

  • feature_id · string · Required, The feature to select.

Triggers

New Feature · Webhook

Triggers when a new feature is created in Productboard

New Note · Webhook

Triggers when a new note is created in Productboard

Updated Feature · Webhook

Triggers when an existing feature is updated in Productboard

Setup

Setup

  1. Add the Productboard connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-productboard@0.1.8; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 actions and 3 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Productboard connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-productboard@0.1.8 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com