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


Chatwork
⚙
WordPress.com

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

Chatwork
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Chatwork, WordPress.com, 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 WordPress.com integration works as expected. Depending on your setup, data should flow between Chatwork and WordPress.com (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 WordPress.com
WordPress.com + Google Sheets + Chatwork: When a new post is published on a WordPress.com site, the post details are added to a Google Sheet. A message is then sent to a Chatwork room to notify the team about the new post.
WordPress.com + Chatwork + Slack: When a new post is published on a WordPress.com site, a message summarizing the post is sent to both a dedicated Chatwork room and a Slack channel to keep the team informed.
Chatwork and WordPress.com 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 WordPress.com
Automate WordPress.com content management with Latenode. Automatically create posts, update pages, and manage comments based on triggers from other apps. Streamline content workflows & connect WordPress.com to your CRM, marketing tools, or databases. Scale publishing tasks with no-code ease or custom JavaScript logic.
Similar apps
Related categories
See how Latenode works
FAQ Chatwork and WordPress.com
How can I connect my Chatwork account to WordPress.com using Latenode?
To connect your Chatwork account to WordPress.com 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 WordPress.com accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I post Chatwork messages for new WordPress.com blog posts?
Yes, you can! Latenode automates this, instantly notifying your team on Chatwork about new WordPress.com content, improving team awareness and engagement.
What types of tasks can I perform by integrating Chatwork with WordPress.com?
Integrating Chatwork with WordPress.com allows you to perform various tasks, including:
- Posting new WordPress.com comments to a specific Chatwork group.
- Creating new WordPress.com posts from messages received on Chatwork.
- Sending daily summaries of WordPress.com activity to a Chatwork room.
- Notifying a Chatwork room when a WordPress.com plugin is updated.
- Creating WordPress.com user accounts from Chatwork member data.
What Chatwork events can trigger workflows inside Latenode?
Latenode triggers on new Chatwork messages, room updates, and member additions, powering automations across your connected apps.
Are there any limitations to the Chatwork and WordPress.com integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- File attachments from Chatwork messages are not directly transferred to WordPress.com.
- Custom post types in WordPress.com may require custom JavaScript for full integration.
- High-volume Chatwork message processing might require scaling your Latenode instance.