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


Chatwork
⚙

Pipedrive


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

Pipedrive
Trigger on Webhook
⚙

Chatwork
⚙
⚙
Iterator
⚙
Webhook response


Save and Activate the Scenario
After configuring Chatwork, Pipedrive, 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 Pipedrive integration works as expected. Depending on your setup, data should flow between Chatwork and Pipedrive (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 Pipedrive
Pipedrive + Google Sheets + Chatwork: When a new deal is created in Pipedrive, its details are added to a Google Sheet. Then, a notification is sent to a specified Chatwork room to inform the team.
Pipedrive + Slack + Chatwork: When a deal in Pipedrive is updated, specifically when it reaches a defined stage, a summary is sent to a designated Slack channel for review. Simultaneously, a similar notification is posted in a specified Chatwork room.
Chatwork and Pipedrive 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 Pipedrive
Sync Pipedrive with Latenode to automate sales workflows. Update deals, create activities, or trigger personalized emails based on deal stages. Use Latenode's visual editor and JavaScript node to build custom lead qualification and routing logic. Scale your sales automation without complex code or per-step pricing limits.
Similar apps
Related categories
See how Latenode works
FAQ Chatwork and Pipedrive
How can I connect my Chatwork account to Pipedrive using Latenode?
To connect your Chatwork account to Pipedrive 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 Pipedrive accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Pipedrive deals from new Chatwork messages?
Yes, you can! Latenode lets you parse Chatwork messages with AI to extract deal details and instantly create corresponding deals in Pipedrive. Improve your sales pipeline effortlessly.
What types of tasks can I perform by integrating Chatwork with Pipedrive?
Integrating Chatwork with Pipedrive allows you to perform various tasks, including:
- Create new Pipedrive deals from specific Chatwork messages automatically.
- Send Chatwork notifications when a Pipedrive deal reaches a certain stage.
- Update Pipedrive contact information based on Chatwork profile changes.
- Log Chatwork conversations as notes within Pipedrive deals or contacts.
- Trigger Chatwork messages when new Pipedrive leads are created.
How do I handle attachments sent via Chatwork in Latenode workflows?
Latenode can parse and process attachments from Chatwork via its file parsing and manipulation features. You can save them to storage or process them further.
Are there any limitations to the Chatwork and Pipedrive integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Real-time synchronization depends on Chatwork's and Pipedrive's API availability.
- Complex data transformations might require JavaScript or AI block configuration.
- Large file attachments may impact workflow execution time.