How to connect Productboard and Userback
Create a New Scenario to Connect Productboard and Userback
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Productboard, triggered by another scenario, or executed manually (for testing purposes). In most cases, Productboard or Userback will be your first step. To do this, click "Choose an app," find Productboard or Userback, and select the appropriate trigger to start the scenario.

Add the Productboard Node
Select the Productboard node from the app selection panel on the right.


Productboard

Configure the Productboard
Click on the Productboard node to configure it. You can modify the Productboard URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Userback Node
Next, click the plus (+) icon on the Productboard node, select Userback from the list of available apps, and choose the action you need from the list of nodes within Userback.


Productboard
⚙
Userback

Authenticate Userback
Now, click the Userback node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Userback settings. Authentication allows you to use Userback through Latenode.
Configure the Productboard and Userback Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Productboard and Userback Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
Userback
Trigger on Webhook
⚙

Productboard
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Productboard, Userback, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Productboard and Userback integration works as expected. Depending on your setup, data should flow between Productboard and Userback (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Productboard and Userback
Userback + Productboard + Slack: When new user feedback is created in Userback, a corresponding feature request is created in Productboard. The product team is then notified via a Slack channel message.
Userback + Productboard + Jira: When a user submits a bug report (new feedback) in Userback, a linked issue is created in Jira for the development team and a note is added to the corresponding feature in Productboard.
Productboard and Userback integration alternatives

About Productboard
Sync Productboard insights into Latenode to automate product development workflows. Track feature requests, prioritize tasks, and trigger actions in other apps (like Jira or Slack) based on user feedback. Build custom reports and alerts using Latenode's visual editor, making feedback actionable across teams without manual data wrangling.
Similar apps
Related categories
About Userback
Use Userback in Latenode to automate feedback loops. Collect user feedback, then trigger actions based on sentiment or keywords. Route bug reports, feature requests, and support queries directly into your workflows. Close the loop faster and with greater accuracy than standalone solutions.
Related categories
See how Latenode works
FAQ Productboard and Userback
How can I connect my Productboard account to Userback using Latenode?
To connect your Productboard account to Userback on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Productboard and click on "Connect".
- Authenticate your Productboard and Userback accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Productboard features from new Userback feedback?
Yes, you can! Latenode lets you automate feature creation based on Userback submissions, saving time and ensuring all feedback reaches Productboard. Use AI to summarize requests, too.
What types of tasks can I perform by integrating Productboard with Userback?
Integrating Productboard with Userback allows you to perform various tasks, including:
- Automatically create new Productboard features from Userback feedback.
- Update Productboard feature status based on Userback user satisfaction.
- Send announcements from Productboard to Userback users.
- Trigger Userback surveys when a Productboard feature is released.
- Centralize user feedback data from Userback into Productboard insights.
How can I automatically tag feedback in Userback based on Productboard data?
With Latenode, you can automatically tag Userback feedback using data from Productboard, making it easier to analyze and prioritize user needs effectively.
Are there any limitations to the Productboard and Userback integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Real-time, two-way synchronization of all data isn't supported.
- Complex data transformations may require custom JavaScript coding.
- Rate limits of Productboard and Userback APIs may impact high-volume workflows.