How to connect Chatwork and Zoho Inventory
Create a New Scenario to Connect Chatwork and Zoho 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 Chatwork, triggered by another scenario, or executed manually (for testing purposes). In most cases, Chatwork or Zoho Inventory will be your first step. To do this, click "Choose an app," find Chatwork or Zoho Inventory, 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 Zoho Inventory Node
Next, click the plus (+) icon on the Chatwork node, select Zoho Inventory from the list of available apps, and choose the action you need from the list of nodes within Zoho Inventory.


Chatwork
⚙

Zoho Inventory


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

Zoho Inventory
Trigger on Webhook
⚙

Chatwork
⚙
⚙
Iterator
⚙
Webhook response


Save and Activate the Scenario
After configuring Chatwork, Zoho 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 Chatwork and Zoho Inventory integration works as expected. Depending on your setup, data should flow between Chatwork and Zoho Inventory (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 Zoho Inventory
Zoho Inventory + Chatwork + Slack: When a new item is created in Zoho Inventory, a notification is sent to a designated Chatwork room to inform the team, and a Slack alert is sent to the purchasing team.
Zoho Inventory + Chatwork + Zoho CRM: When a new sales order is created in Zoho Inventory, a message is sent to a specified Chatwork room to notify the sales team. The customer record is also updated in Zoho CRM to reflect the new order.
Chatwork and Zoho Inventory 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 Zoho Inventory
Connect Zoho Inventory to Latenode and automate stock updates across platforms. Track orders, manage product levels, and trigger alerts when items run low, all within visual workflows. Enhance inventory visibility by integrating sales data from multiple sources using Latenode's AI-powered data transformation tools.
Similar apps
Related categories
See how Latenode works
FAQ Chatwork and Zoho Inventory
How can I connect my Chatwork account to Zoho Inventory using Latenode?
To connect your Chatwork account to Zoho Inventory 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 Zoho Inventory accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I get Chatwork notifications for new Zoho Inventory orders?
Yes, you can! Latenode's visual editor makes it easy to trigger Chatwork messages whenever a new order is created in Zoho Inventory, keeping your team instantly informed.
What types of tasks can I perform by integrating Chatwork with Zoho Inventory?
Integrating Chatwork with Zoho Inventory allows you to perform various tasks, including:
- Send Chatwork alerts for low stock levels in Zoho Inventory.
- Create Zoho Inventory invoices directly from Chatwork messages.
- Post daily sales summaries from Zoho Inventory to a Chatwork group.
- Automatically update Zoho Inventory with new contact info from Chatwork.
- Receive instant Chatwork notifications for new Zoho Inventory payments.
How do I customize Chatwork messages based on inventory changes?
Use Latenode's no-code blocks or JavaScript steps to tailor Chatwork messages based on specific inventory events. Get granular control over message content and format.
Are there any limitations to the Chatwork and Zoho Inventory integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Real-time updates depend on the polling interval set within Latenode.
- Complex data transformations may require JavaScript knowledge.
- Historical data migration between apps is not directly supported.