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


Productboard
β
SOS Inventory

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

Productboard
β
β
Iterator
β
Webhook response

Save and Activate the Scenario
After configuring Productboard, SOS Inventory, 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 SOS Inventory integration works as expected. Depending on your setup, data should flow between Productboard and SOS Inventory (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 SOS Inventory
Productboard + SOS Inventory + Slack: When a new feature request is created in Productboard, automatically create a sales order in SOS Inventory. Subsequently, a notification is sent via Slack to the relevant team.
SOS Inventory + Productboard + Jira: When a new sales order is created in SOS Inventory, a feature request will be automatically created in Productboard, and an issue will be created in Jira.
Productboard and SOS Inventory 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 SOS Inventory
Sync SOS Inventory with Latenode to automate stock updates and order processing. Connect your inventory data to accounting, e-commerce, or shipping platforms. Build visual workflows to trigger actions based on inventory levels or sales data. Use no-code tools or custom scripts to tailor the flow, avoiding manual data entry and ensuring real-time accuracy.
Related categories
See how Latenode works
FAQ Productboard and SOS Inventory
How can I connect my Productboard account to SOS Inventory using Latenode?
To connect your Productboard account to SOS Inventory 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 SOS Inventory accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I update SOS Inventory when a Productboard feature ships?
Yes, you can! Latenode's visual editor simplifies this. Automatically update inventory levels in SOS Inventory as new features are released in Productboard, streamlining your product lifecycle updates.
What types of tasks can I perform by integrating Productboard with SOS Inventory?
Integrating Productboard with SOS Inventory allows you to perform various tasks, including:
- Automatically create SOS Inventory items from new Productboard features.
- Sync feature requests from Productboard to SOS Inventory as work orders.
- Update inventory in SOS Inventory when a Productboard feature is released.
- Track the cost of goods for features planned in Productboard.
- Trigger alerts for low stock when feature development nears completion.
How does Latenode handle Productboard's API rate limits?
Latenode uses intelligent queueing and error handling to manage Productboard API rate limits, ensuring reliable data synchronization and preventing workflow disruptions.
Are there any limitations to the Productboard and SOS Inventory integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Custom field synchronization requires custom JavaScript blocks.
- Complex data transformations may require advanced node configuration.
- Real-time, bi-directional sync depends on the polling frequency.