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


Chatwork
⚙

ClickMeeting


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

ClickMeeting
Trigger on Webhook
⚙

Chatwork
⚙
⚙
Iterator
⚙
Webhook response


Save and Activate the Scenario
After configuring Chatwork, ClickMeeting, 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 ClickMeeting integration works as expected. Depending on your setup, data should flow between Chatwork and ClickMeeting (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 ClickMeeting
Chatwork + ClickMeeting + Google Calendar: When a message in Chatwork triggers the creation of a new conference in ClickMeeting, a corresponding event is automatically created in Google Calendar, ensuring all attendees are informed.
ClickMeeting + Chatwork + Slack: When a ClickMeeting conference has a new recording, the recording is sent to a dedicated Chatwork channel and a summary message is posted in Slack, ensuring team members are notified and have access to the recording.
Chatwork and ClickMeeting 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 ClickMeeting
Automate ClickMeeting tasks within Latenode. Trigger webinars based on CRM data or user actions. Sync attendee info to databases, send follow-ups, and analyze engagement, all without manual work. Latenode adds flexibility via custom logic and AI, going beyond basic scheduling for smarter event workflows.
Similar apps
Related categories
See how Latenode works
FAQ Chatwork and ClickMeeting
How can I connect my Chatwork account to ClickMeeting using Latenode?
To connect your Chatwork account to ClickMeeting 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 ClickMeeting accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically notify my team about ClickMeeting webinar registrations?
Yes, you can! Latenode lets you trigger Chatwork messages when someone registers, ensuring your team stays informed. Use advanced logic and JavaScript to customize alerts.
What types of tasks can I perform by integrating Chatwork with ClickMeeting?
Integrating Chatwork with ClickMeeting allows you to perform various tasks, including:
- Send Chatwork notifications for new ClickMeeting registrants.
- Post ClickMeeting recording links to Chatwork after events.
- Create automated Chatwork reminders before ClickMeeting webinars.
- Update Chatwork status when ClickMeeting webinars start.
- Log ClickMeeting attendance data to a Chatwork channel.
What Chatwork triggers are available within Latenode's integration builder?
Latenode provides triggers for new messages, updated messages, and new users in Chatwork, enabling real-time automation of key workflows.
Are there any limitations to the Chatwork and ClickMeeting integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex conditional logic may require JavaScript knowledge.
- Real-time updates are subject to Chatwork and ClickMeeting API rate limits.
- Custom field mapping requires careful configuration.