Resources · Make integration

Chatwork Make integrationAutomate Chatwork with Make.

Can Make handle your Chatwork rooms, tasks and messages without code? Mostly, yes. The Chatwork Make integration offers 22 modules, 1 instant trigger among them. This page shows how to connect your account and build a first scenario, step by step.

Try the Chatwork integration on Make See the 22 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Chatwork Make integration do?

The Chatwork Make integration links your Chatwork account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one step such as a trigger, an action or a search. Chatwork brings 22 of them, including 1 instant trigger that reacts to account and room events.

A room for every new client. When a deal closes in your CRM, Create a Groupchat opens a dedicated room and Create a Room Message posts the first brief, so the team starts the project in the right place.

Requests that turn into tasks. Watch Events notices an event in your account, and Create a Room Task gives it a proper task inside the room where the team already talks.

Attachments saved before a room closes. List a Room's Files goes through the files of a room and hands each one, as a bundle (one item passed from a module to the next), to your storage app.

What the integration does not do out of the box: anything beyond these 22 modules goes through Make an API Call. The documentation also marks every field shown in bold as mandatory. If n8n is on your shortlist too, the n8n vs Make comparison lays out the criteria. To learn the editor itself, Make training starts from zero, and Make troubleshooting helps when a run fails.

Connect

How do you connect Chatwork to Make?

01
Add a Chatwork module
Open your scenario, add any Chatwork module, then click Create a connection. A connection is your Chatwork account linked to Make once; every Chatwork module in your scenarios reuses it afterwards.
02
Name it and authorize Make
Give the connection a name if you like, which helps when you manage several accounts. Then authorize Make on the Chatwork page that opens, or paste the key Chatwork gives you, depending on what the window asks for.
03
Save and fill the module
Click Save. Back in the module, Make can now read your Chatwork account and lists what it finds there, so you pick from a list instead of typing.

First scenario

Your first scenario: turn a Chatwork event into a task

GoalWhen an event happens in your Chatwork account, Make creates a task in the room you chose.

01
Create the scenario
On the Scenarios page, create a new scenario and click the + to add its first module. Search for Chatwork and pick Watch Events.
02
Connect and set the trigger
Click Create a connection to link your account, then fill the fields of Watch Events. Bold ones are mandatory, and Make lists what it can read in Chatwork.
03
Add the task module
Click the + on the right of Watch Events and add Create a Room Task. Map the data from the trigger into the task so each event carries its own details.
04
Test with Run once
Click Run once, then cause an event in Chatwork. Read the bundles each module received, and check that the new task shows up in the room.
05
Switch the scenario on
Save and switch the scenario on. Watch Events is instant, so Chatwork calls Make as soon as an event happens; each module run counts as one operation on your plan.

Triggers

What starts a Chatwork scenario

1 module starts a scenario when something happens in Chatwork. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Chatwork as soon as it happens.

Chatwork1Watch Events

Watch Events

Instant trigger

In Make“Watches account events or room events.”

Watch Events starts your scenario the moment something happens in your Chatwork account or in one of its rooms, so the rest of the flow reacts without anyone copying messages by hand.

How it fires

instant: Chatwork calls Make through a webhook as soon as the event happens, which is why the module carries the lightning badge in the editor.

When to use it

as the first module whenever a room event should kick off work elsewhere, like logging a request in a spreadsheet or opening a task for a colleague.

Watch out

fields shown in bold in the module dialog are mandatory, so fill them before your first test.

Modules

What the Chatwork modules do

Chatwork gives you 21 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Chatwork1

Approve a Contact Approval Request

Action

In Make“Approves a contact approval requests.”

Approve a Contact Approval Request accepts someone who asked to join your Chatwork contacts, so new partners land in your list without a manual click on each request.

When to use it

right after a search has shown you the pending requests, for the ones you already know you want to accept.

Watch out

each approval adds a person to your contacts, so test on a single request before running it on a whole list.

Chatwork2

Create a Groupchat

Action

In Make“Creates a groupchat.”

A new group chat, opened by the scenario itself: Create a Groupchat gives a project or a client its own room the moment your other tools know about it.

When to use it

a deal is signed in your CRM and the account team needs a shared space to discuss it.

Watch out

every run creates another room, so check with Run once before switching the scenario on, or duplicates will pile up.

Chatwork3

Create a Room Message

Action

In Make“Sends a message to a room.”

Create a Room Message posts text in a Chatwork room on your behalf, which turns an event from any other app into a notice the team actually reads.

When to use it

a form is submitted or an invoice gets paid, and the right room should hear about it.

Watch out

map data from the previous module into the text, otherwise every post says the same generic line.

Chatwork4

Create a Room Task

Action

In Make“Creates a task in a room.”

With Create a Room Task, a follow-up becomes a Chatwork task inside a room, visible where the team already works instead of hidden in a separate tool.

When to use it

a support ticket needs an owner, or an event caught by Watch Events calls for someone to act.

Watch out

bold fields in the module dialog are required, so check them before the first Run once.

Chatwork5

Decline a Contact Approval Request

Action

In Make“Declines a contact approval request.”

Decline a Contact Approval Request turns down a contact request, which keeps your Chatwork contact list limited to the people you really work with.

When to use it

requests come from people you do not recognize and you prefer the scenario to refuse them rather than leave them waiting.

Watch out

run it on one request with Run once first, since a refusal is not something you want to apply to the wrong person.

Chatwork6

Delete or Leave a Groupchat

Action

In Make“Deletes or leaves a groupchat.”

Delete or Leave a Groupchat closes a room once its job is done: the module either deletes the group chat or makes your account leave it.

When to use it

a project is marked finished in your project tool and its Chatwork room should not stay open.

Watch out

a deleted room does not come back, so save its files and messages first and test on a dummy room.

Chatwork7

Get a Room

Action

In Make“Retrieves a room (groupchat room, direct message room or mychat room).”

Get a Room fetches the details of one room, whether it is a group chat, a direct message room or your own mychat, and passes them to the next module.

When to use it

you already know which room is concerned and need its details before deciding what to post or update.

Watch out

it reads a single room; to go through all of them, start from List Rooms instead.

Chatwork8

Get a Room's File

Action

In Make“Retrieves a file from a room.”

Get a Room's File pulls one file shared in a Chatwork room into your scenario, ready to be saved or forwarded by the module that follows.

When to use it

a client drops a signed contract in the room and you want a copy stored in your drive app.

Watch out

on the Free plan, Make handles files up to 5 MB, so check the size of what your team usually shares.

Chatwork9

Get a Room's Message

Action

In Make“Retrieve a message from a room.”

Get a Room's Message retrieves one specific message from a room, so a later module can quote it, store it or send it somewhere else.

When to use it

an event points to a message you want to copy into a spreadsheet or a ticket.

Watch out

it returns one message only; List a Room's Messages is the right choice when you need everything a room contains.

Chatwork10

Get a Room's Task

Action

In Make“Retrieves a task from a room.”

Get a Room's Task reads a single task from a room and brings its details into the scenario, so later steps can report on it or act on it.

When to use it

a task was created earlier and another tool needs its details to write a status update.

Watch out

for every task of a room at once, List a Room's Tasks fits better and saves you a loop.

Chatwork11

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the Chatwork API with the connection you already set up, which covers whatever the other modules leave out.

When to use it

the action you need has no dedicated module in this list, and you still want it in the same scenario.

Watch out

you describe the request yourself, so keep the Chatwork API reference open while you set it up.

Chatwork12

Update a Groupchat

Action

In Make“Updates a groupchat.”

Update a Groupchat changes an existing group chat, so a room keeps up with the project it belongs to instead of drifting out of date.

When to use it

a project moves to a new stage in your management tool and its Chatwork room needs to reflect that.

Watch out

place Get a Room before it if you want to see the room as it is before changing anything.

Chatwork13

Update a Groupchat's Members

Action

In Make“Updates the members of a room.”

Update a Groupchat's Members changes who belongs to a room in one step, keeping access in line with the people who actually work on the account.

When to use it

a new colleague joins a client account and should be in its room without waiting for someone to invite them.

Watch out

check the current list with List a Room's Members first, so the update does not drop someone by mistake.

Chatwork14

List a Room's Files

In Make“Retrieves all the files of a room.”

List a Room's Files returns every file of a room, one bundle per file, so the next modules can archive or check them one by one.

When to use it

a room is about to be closed and its documents should be saved somewhere else first.

Watch out

each module placed after it runs once per file, and each of those runs is an operation counted on your plan.

Chatwork15

List a Room's Members

In Make“Retrieves all the members of a room.”

Who is in this room? List a Room's Members answers that by returning each member as a separate bundle you can check or copy.

When to use it

before Update a Groupchat's Members, or to compare a room with the team list kept in a spreadsheet.

Watch out

a message module placed right after it would post once per person, so think twice before adding one there.

Chatwork16

List a Room's Messages

In Make“Retrieves all the messages of a room.”

List a Room's Messages brings back the messages posted in a room, which is handy for an archive or a digest kept outside Chatwork.

When to use it

a client project ends and you want its conversation saved next to the rest of the file.

Watch out

a search can return zero, one or many bundles, so test with Run once and read what arrives before you reuse it in the next module.

Chatwork17

List a Room's Tasks

In Make“Retrieves all the tasks of a room.”

Every task attached to a room comes out of List a Room's Tasks, one bundle each, ready to be copied into a tracker or a report.

When to use it

a manager wants the follow-ups of a client room gathered in one spreadsheet.

Watch out

no task in the room, no bundle. The modules after this search then have nothing to work on.

Chatwork18

List Contacts

In Make“Retrieves all your contacts.”

List Contacts returns your whole Chatwork contact list, so a scenario can compare it with your CRM or your mailing tool.

When to use it

you want to make sure every client you talk to in Chatwork also exists in your CRM.

Watch out

it reads the contacts of the account behind the connection, so pick the right connection if several people share the scenario.

Chatwork19

List my Contact Approval Requests

In Make“Retrieves all contact approval requests you've received.”

This search shows the contact requests your account has received, one bundle per request, so the next step can sort them without you opening Chatwork.

When to use it

as the opening move of a cleanup, before Approve or Decline settles each request.

Watch out

without a trigger in front of it, this search only runs when the scenario runs, on the schedule you set.

Chatwork20

List my Tasks

In Make“Retrieves all your tasks.”

Your Chatwork tasks from every room, not just one, come out of this search together, which gives you a personal to-do view to copy into another tool.

When to use it

you want your Chatwork tasks mirrored in your calendar or in your task manager.

Watch out

for the tasks of a single room, List a Room's Tasks is narrower and returns fewer bundles.

Chatwork21

List Rooms

In Make“Retrieves all your rooms (groupchat room, direct message room or mychat room).”

List Rooms returns every room of your account: group chats, direct message rooms and your mychat, each one arriving as a bundle.

When to use it

one announcement has to reach several rooms, or you need to spot the room that belongs to a given client.

Watch out

direct message rooms and mychat come out too, so decide which rooms you really want before a message module posts in all of them.

Need help

Need help automating Chatwork with Make?

A person reads every message.

FAQ

Chatwork and Make: common questions

01Is the Chatwork Make integration free?

Yes. Chatwork is a standard app in Make, so it works on the Free plan. That plan gives you 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the minimum interval down to 1 minute, remove the cap on active scenarios and count usage in credits each month. Your Chatwork subscription is a separate matter this page does not cover.

02What do you need to connect Chatwork to Make?

A Chatwork account and a Make account; the documentation lists no other prerequisite. You add any Chatwork module, click Create a connection, name it if you want, then authorize Make on the Chatwork page or paste the key Chatwork gives you, and click Save. That connection is reused by every Chatwork module you add later, in this scenario and in the next ones. If a module still refuses to run, look at the fields shown in bold, which the documentation marks as mandatory.

03Does the Chatwork trigger in Make work in real time?

Yes. Watch Events, the only Chatwork trigger, is instant: Chatwork calls Make through a webhook as soon as an account or room event happens, instead of Make checking on a schedule. That is why the module shows a lightning badge in the editor. The other Chatwork modules are actions and searches, so they run when the trigger fires or when a scenario that starts with another app reaches them. Test with Run once before switching the scenario on to see what an event actually sends.

04What if the Chatwork module you need is missing in Make?

Use Make an API Call. It reaches any endpoint of the Chatwork API with the connection you already have, so you are not limited to the 22 listed modules. You write the request yourself, which means keeping the Chatwork API reference at hand. Before going that way, check whether a search followed by an action already covers the need, for example List Rooms and then Create a Room Message. The only limit the documentation mentions is that fields shown in bold in a module dialog are mandatory.

05Make or n8n for Chatwork?

It depends on your criteria. On the Make side, Chatwork comes with 22 modules, an instant trigger and Make an API Call, all set up in a visual editor where each step shows the bundles it received. If n8n is also on your list, first check that it offers a Chatwork node covering the actions you need, then compare the two tools on what matters to your team: the modules available, how each one counts usage, and who will maintain the scenarios once they run.

Add a Chatwork module

Name it and authorize Make

Save and fill the module

Create the scenario

Connect and set the trigger

Add the task module

Test with Run once

Switch the scenario on

Need help automating Chatwork with Make?