How to connect Chatwork and Productboard
Create a New Scenario to Connect Chatwork and Productboard
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 Chatwork, triggered by another scenario, or executed manually (for testing purposes). In most cases, Chatwork or Productboard will be your first step. To do this, click "Choose an app," find Chatwork or Productboard, and select the appropriate trigger to start the scenario.

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


Chatwork

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


Chatwork
⚙

Productboard


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

Productboard
Trigger on Webhook
⚙

Chatwork
⚙
⚙
Iterator
⚙
Webhook response


Save and Activate the Scenario
After configuring Chatwork, Productboard, 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 Chatwork and Productboard integration works as expected. Depending on your setup, data should flow between Chatwork and Productboard (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Chatwork and Productboard
Chatwork + Productboard + Jira: When a new feature request is posted in Chatwork, it automatically creates a feature in Productboard for prioritization. Once the feature is accepted, a Jira ticket is created to track its development.
Productboard + Chatwork + Slack: When the status of a feature changes in Productboard, a message is sent to a designated Chatwork room and a Slack channel to keep stakeholders informed.
Chatwork and Productboard integration alternatives

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

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.
Related categories
See how Latenode works
FAQ Chatwork and Productboard
How can I connect my Chatwork account to Productboard using Latenode?
To connect your Chatwork account to Productboard on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Chatwork and click on "Connect".
- Authenticate your Chatwork and Productboard accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Productboard features from Chatwork messages?
Yes, you can! Latenode's flexible workflows let you parse Chatwork messages with AI and create new Productboard features automatically, saving hours of manual data entry.
What types of tasks can I perform by integrating Chatwork with Productboard?
Integrating Chatwork with Productboard allows you to perform various tasks, including:
- Create new Productboard features from specific Chatwork messages.
- Send Chatwork notifications for new Productboard insights.
- Update Productboard features when Chatwork discussions change.
- Automatically archive Chatwork messages related to completed features.
- Trigger workflows based on sentiment analysis of Chatwork feedback for Productboard.
How do I handle errors when updating Productboard from Chatwork?
Latenode provides robust error handling. You can automatically retry failed updates or send alerts to Chatwork for manual intervention.
Are there any limitations to the Chatwork and Productboard integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits imposed by Chatwork and Productboard APIs may affect high-volume workflows.
- Complex data transformations might require JavaScript knowledge.
- Historical data migration requires a separate initial setup workflow.