Skip to content
← Back to documentation
Technical Reference

Produktly

Onboarding, in-app announcements, feedback collection and NPS for SaaS products.

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

Overview

Connect Produktly with Flows360

Onboarding, in-app announcements, feedback collection and NPS for SaaS products.

Use the Produktly 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 15 actions and 4 triggers.

Available actions

  • List Changelogs
  • List Changelog Posts
  • Create Changelog Post
  • Update Changelog Post
  • List Feedback Widgets
  • List Feedback Responses
  • List Roadmaps
  • Get Roadmap
  • Plus 7 additional declared actions.

Available triggers

  • New Changelog Post
  • New Feedback Response
  • New NPS Response
  • New Tag

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: Produktly
  • Package: @activepieces/piece-produktly@0.1.0
  • Exact artifact digest: sha256:08a3d5bb914404035815d4ff4cf34fc81a6376fbcc6959cdfc4919f69790028f
  • 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

  • List Changelogs (list_changelogs), List all changelogs in your Produktly account. Classification: read.
  • List Changelog Posts (list_changelog_posts), List all posts within a specific changelog. Classification: read.
  • Create Changelog Post (create_changelog_post), Publish a new post inside a changelog. Visible to your users once active. Classification: read.
  • Update Changelog Post (update_changelog_post), Edit an existing changelog post, change its title, body, tags or visibility. Classification: read.
  • List Feedback Widgets (list_feedback_widgets), List all feedback widgets configured in your Produktly account. Classification: read.
  • List Feedback Responses (list_feedback_responses), List the user responses submitted through a feedback widget. Classification: read.
  • List Roadmaps (list_roadmaps), List all public roadmaps in your Produktly account. Classification: read.
  • Get Roadmap (get_roadmap), Get a single roadmap with its sections, items, tags and vote counts. Classification: read.
  • List NPS Widgets (list_nps_widgets), List all NPS widgets configured in your Produktly account. Classification: read.
  • Get NPS Score (get_nps_score), Get the current Net Promoter Score (NPS) for a widget, broken down into promoters, passives and detractors. Classification: read.
  • List NPS Responses (list_nps_responses), List individual NPS responses (rating + comment + user info) for a widget. Classification: read.
  • List Tags (list_tags), List all tags that can be attached to changelog posts. Classification: read.
  • Get Company Stats (get_company_stats), Get a company-wide statistics summary across all your Produktly features. Classification: read.
  • Get Widget Stats (get_widget_stats), Get event and unique-user statistics for a specific entity type (e.g. all changelogs, all NPS widgets). Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Changelog Post, polling.
  • New Feedback Response, polling.
  • New NPS Response, polling.
  • New Tag, polling.

Verification

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

Capability summary

Authenticationcustom
Supported objects19
Supported actionsNot published
Triggers4

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
List Changelogs Yes No List all changelogs in your Produktly account.
List Changelog Posts Yes No List all posts within a specific changelog.
Create Changelog Post Yes No Publish a new post inside a changelog. Visible to your users once active.
Update Changelog Post Yes No Edit an existing changelog post u2014 change its title, body, tags or visibility.
List Feedback Widgets Yes No List all feedback widgets configured in your Produktly account.
List Feedback Responses Yes No List the user responses submitted through a feedback widget.
List Roadmaps Yes No List all public roadmaps in your Produktly account.
Get Roadmap Yes No Get a single roadmap with its sections, items, tags and vote counts.
List NPS Widgets Yes No List all NPS widgets configured in your Produktly account.
Get NPS Score Yes No Get the current Net Promoter Score (NPS) for a widget, broken down into promoters, passives and detractors.
List NPS Responses Yes No List individual NPS responses (rating + comment + user info) for a widget.
List Tags Yes No List all tags that can be attached to changelog posts.
Get Company Stats Yes No Get a company-wide statistics summary across all your Produktly features.
Get Widget Stats Yes No Get event and unique-user statistics for a specific entity type (e.g. all changelogs, all NPS widgets).
Custom API Call Yes No Make a custom API call to a specific endpoint
New Changelog Post Yes No polling trigger declared by the pinned package.
New Feedback Response Yes No polling trigger declared by the pinned package.
New NPS Response Yes No polling trigger declared by the pinned package.
New Tag Yes No polling trigger declared by the pinned package.

Triggers

New Changelog Post · Poll

Fires when a new post is published in the selected changelog.

Inputs

  • changelog · string
New Feedback Response · Poll

Fires when a user submits a new response to the selected feedback widget.

Inputs

  • widget · string
New NPS Response · Poll

Fires when a user submits a new NPS rating for the selected widget.

Inputs

  • widget · string
New Tag · Poll

Fires when a new tag is created in your Produktly account.

Setup

Setup

  1. Add the Produktly 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-produktly@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 15 actions and 4 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 Produktly 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-produktly@0.1.0 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.