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


Chatwork
âš™
Memberstack

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

Chatwork
âš™
âš™
Iterator
âš™
Webhook response

Save and Activate the Scenario
After configuring Chatwork, Memberstack, 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 Memberstack integration works as expected. Depending on your setup, data should flow between Chatwork and Memberstack (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 Memberstack
Memberstack + Google Sheets + Chatwork: When a Memberstack member's subscription changes, the event details are logged in a Google Sheet for tracking and reporting. A message is then sent to a designated Chatwork group to notify the team of the subscription change.
Memberstack + Chatwork + Slack: When a member cancels their subscription in Memberstack, a message containing the member's information is sent to a specified Chatwork room, and a notification is also posted to a dedicated Slack channel to alert the team.
Chatwork and Memberstack 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 Memberstack
Automate Memberstack user management with Latenode. Create workflows to onboard/offboard users based on triggers in other apps. Use webhooks to sync data, grant access, or update profiles. Connect Memberstack to CRMs, email tools, or databases for automated membership lifecycle management—all visually, without code, and at scale.
Similar apps
Related categories
See how Latenode works
FAQ Chatwork and Memberstack
How can I connect my Chatwork account to Memberstack using Latenode?
To connect your Chatwork account to Memberstack 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 Memberstack accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I send Chatwork messages for new Memberstack signups?
Yes, you can! Latenode automates notifications, instantly alerting your team in Chatwork when new members join Memberstack, improving team response time and member onboarding.
What types of tasks can I perform by integrating Chatwork with Memberstack?
Integrating Chatwork with Memberstack allows you to perform various tasks, including:
- Send Chatwork messages for new Memberstack subscriptions.
- Update Memberstack member data based on Chatwork commands.
- Create new Chatwork tasks from Memberstack events.
- Automatically invite new members to specific Chatwork groups.
- Post summaries of new Memberstack members in Chatwork channels.
How do I trigger Chatwork actions based on Memberstack events?
Use Latenode's visual builder to create event-based triggers. Connect Memberstack events to automated Chatwork messages, no coding required.
Are there any limitations to the Chatwork and Memberstack integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations may require JavaScript knowledge.
- Rate limits of Chatwork and Memberstack APIs apply.
- Historical data migration needs separate workflows.