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


Chatwork
âš™

Google contacts


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

Google contacts
Trigger on Webhook
âš™

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


Save and Activate the Scenario
After configuring Chatwork, Google contacts, 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 Google contacts integration works as expected. Depending on your setup, data should flow between Chatwork and Google contacts (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 Google contacts
Chatwork + Google Contacts + Google Sheets: When a new contact is added in Google Contacts, the contact's information is retrieved and then added as a new row in a specified Google Sheet. Chatwork integration not possible with new contact trigger.
Google Contacts + Google Calendar + Chatwork: When a new contact is created in Google Contacts, an event is created in Google Calendar. Then, a new Chatwork room is created to discuss the new Google Contact event.
Chatwork and Google contacts 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 Google contacts
Sync Google Contacts with Latenode to automate contact management. Update records, trigger follow-ups, or enrich profiles based on events in other apps. Avoid manual data entry; use Latenode’s visual builder to create flows that sync contacts across your marketing and sales tools, adding custom logic without coding.
Similar apps
Related categories
See how Latenode works
FAQ Chatwork and Google contacts
How can I connect my Chatwork account to Google contacts using Latenode?
To connect your Chatwork account to Google contacts 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 Google contacts accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Chatwork tasks from new Google contacts?
Yes, you can! Latenode allows you to create automated workflows that trigger Chatwork task creation whenever a new contact is added to Google contacts. Save time and ensure no lead is missed.
What types of tasks can I perform by integrating Chatwork with Google contacts?
Integrating Chatwork with Google contacts allows you to perform various tasks, including:
- Create Chatwork tasks for new Google contacts automatically.
- Send Chatwork messages when a Google contact is updated.
- Update Google contact details based on Chatwork activity.
- Synchronize contact information between Chatwork and Google contacts.
- Trigger workflows based on contact events in either application.
Can I filter Google contacts before sending Chatwork messages?
Yes, use Latenode's visual editor to filter contacts based on criteria like location or job title before sending targeted Chatwork messages.
Are there any limitations to the Chatwork and Google contacts integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits imposed by Chatwork and Google contacts APIs may affect high-volume workflows.
- Complex data transformations might require custom JavaScript code.
- Real-time synchronization depends on the polling frequency set in your workflow.