How to connect Productboard and Vitally
Create a New Scenario to Connect Productboard and Vitally
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 Vitally will be your first step. To do this, click "Choose an app," find Productboard or Vitally, 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 Vitally Node
Next, click the plus (+) icon on the Productboard node, select Vitally from the list of available apps, and choose the action you need from the list of nodes within Vitally.


Productboard
⚙
Vitally

Authenticate Vitally
Now, click the Vitally node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Vitally settings. Authentication allows you to use Vitally through Latenode.
Configure the Productboard and Vitally 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 Vitally 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
⚙
Vitally
Trigger on Webhook
⚙

Productboard
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Productboard, Vitally, 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 Vitally integration works as expected. Depending on your setup, data should flow between Productboard and Vitally (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 Vitally
Productboard + Vitally + Slack: When a new feature is requested in Productboard, the automation checks if users in Vitally are associated with that feature. If a matching customer segment is found, a message is sent to a designated Slack channel to notify the product team.
Vitally + Productboard + Jira: If a customer's health score drops in Vitally, the automation searches Productboard for features related to that customer. Based on those features, a new bug fix issue is created in Jira, linking back to the relevant Productboard features.
Productboard and Vitally 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 Vitally
Use Vitally in Latenode to centralize customer success data and automate actions based on health scores. Sync data, trigger alerts for at-risk users, and personalize support workflows, all within Latenode's visual editor. Combine Vitally's insights with other tools for smarter, automated customer lifecycle management.
Similar apps
Related categories
See how Latenode works
FAQ Productboard and Vitally
How can I connect my Productboard account to Vitally using Latenode?
To connect your Productboard account to Vitally 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 Vitally accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically update Vitally customer health scores?
Yes, you can! Latenode's flexible workflows let you trigger updates based on Productboard feature requests, ensuring your team proactively addresses at-risk accounts.
What types of tasks can I perform by integrating Productboard with Vitally?
Integrating Productboard with Vitally allows you to perform various tasks, including:
- Sync new Productboard features as goals in Vitally.
- Create Vitally segments based on Productboard feature requests.
- Trigger customer outreach in Vitally after feature releases.
- Update customer health scores based on Productboard data.
- Send Productboard feedback to Vitally as customer notes.
What Productboard data can I access within Latenode workflows?
You can access features, components, and user feedback. Latenode supports dynamic extraction and parsing for richer data handling.
Are there any limitations to the Productboard and Vitally integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Historical data sync is limited to the available Productboard and Vitally APIs.
- Complex data transformations may require JavaScript blocks.
- Rate limits are subject to Productboard and Vitally API terms.