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


Productboard
β

Chatwork


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

Chatwork
Trigger on Webhook
β

Productboard
β
β
Iterator
β
Webhook response


Save and Activate the Scenario
After configuring Productboard, Chatwork, 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 Chatwork integration works as expected. Depending on your setup, data should flow between Productboard and Chatwork (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 Chatwork
Productboard + Jira + Chatwork: When a new feature is created in Productboard, a corresponding issue is created in Jira. A message is then sent to a designated Chatwork room to notify the team.
Chatwork + Productboard + Google Sheets: When a new message is added to a specified Chatwork room, a note is created in Productboard. The content of the note, along with relevant details, is then added as a new row in Google Sheets for tracking and analysis.
Productboard and Chatwork 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 Chatwork
Use Chatwork with Latenode to automate team notifications and tasks. Send messages based on triggers from your CRM, database, or other apps. Latenode's visual builder simplifies creating complex workflows. Reduce manual updates, keep your team informed, and improve response times by integrating Chatwork into automated processes.
Similar apps
Related categories
See how Latenode works
FAQ Productboard and Chatwork
How can I connect my Productboard account to Chatwork using Latenode?
To connect your Productboard account to Chatwork 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 Chatwork accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I get notified in Chatwork about new Productboard features?
Yes, you can! Latenode allows you to automatically post new Productboard feature updates to a dedicated Chatwork room, keeping your team informed in real-time.
What types of tasks can I perform by integrating Productboard with Chatwork?
Integrating Productboard with Chatwork allows you to perform various tasks, including:
- Post new Productboard feature ideas to a Chatwork discussion room.
- Send Chatwork alerts when a Productboard feature status changes.
- Create Productboard features directly from Chatwork messages.
- Share Productboard customer feedback summaries in Chatwork.
- Automatically update feature statuses in Productboard based on Chatwork discussions.
Can I use JavaScript to transform data between Productboard and Chatwork?
Yes! Latenode lets you use JavaScript code blocks to customize and transform any data flowing between Productboard and Chatwork for advanced workflows.
Are there any limitations to the Productboard and Chatwork integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits imposed by Productboard and Chatwork may affect high-volume workflows.
- Custom field mappings may require JavaScript knowledge for complex transformations.
- Historical data synchronization is not supported by default.