How to Connect Slack to Chatwork and Forward Messages Automatically | Including How Approval Works

Internal communication happens in Slack, while conversations with customers and partner companies happen in Chatwork. In that case, someone has to rewrite what was decided in Slack into Chatwork. This article walks through automatically posting messages from a Slack channel to a Chatwork room.

The Slack and Chatwork specifications here were checked against official documentation and the connection's declarations as of November 4, 2026.

Summary

  • Use a service integration and a connector. Start the workflow with Slack's "Channel Message Received," and post to Chatwork with a "Run external service" step
  • Posts run without a person checking them. Publishing counts as approval, and runs are kept in the approval records. If an administrator has set this operation to "Always ask," it's refused and stops
  • Posts appear in Chatwork under the name of the person who connected it. This is because Chatwork API tokens are tied to a person's account

What it can and cannot do

Which messages arrive: "Channel Message Received" picks up public channels, private channels, and group DMs. One-on-one DMs are a separate event, "Direct Message Received."

Which fields arrive: only channel and ts are always present. text and user may be missing. If you put text in the body and it didn't arrive, the run fails rather than leaving it blank. user and channel are IDs, so people's names and channel names don't appear in Chatwork.

Cost: a service integration costs about ¥0.5 per event at the moment it arrives. It's the same even if nothing runs. Chat messages are a high-volume event; a channel that gets 100 messages a day comes to about ¥50 a day. Adding more filters doesn't necessarily reduce the bill. Plan on using it only for channels with few messages.

Limits on the Chatwork side: the body must be 1 to 65,535 characters. The posting API allows up to 10 calls per 10 seconds per room and up to 300 calls per 5 minutes across the whole API; beyond that, it returns 429.

What you need

  • Manager or higher permission in Samurai App (needed to add a service integration)
  • Help from an administrator or manager who can add "Connectors"
  • An account that can connect to Slack
  • A Chatwork API token (except on the personal plan, you need to submit an "API usage request" to your organization's administrator)
  • The ID of the destination room (the number after rid in the URL when you open the chat)

Steps

1. Issue a Chatwork API token

From your user name at the top right of Chatwork, open "Service integrations" and issue a token under "API token" on the left. The owner of this token becomes the name posts appear under.

That person must be a member of the destination room. Posts to rooms they haven't joined are refused with 403.

2. Connect the connectors

On the "Connectors" tab in "Settings," "Add" Slack and Chatwork and connect each one. Chatwork asks for credentials when connecting, so enter the token from step 1.

3. Build the workflow

From "Create" in "Workflows," choose "New."

  1. Under "Workflow inputs," use "Add input field" to create a field named event of the type "Group of fields." Slack messages go in here
  2. From "Connect," place a "Run external service" step, and under "Service operation" choose the operation that posts a message, under the Chatwork heading. Right after connecting, it can take about 10 seconds to appear in the list
  3. Enter the values to pass as follows. You can add names from the button below the field
Name Value
room_id The ID of the destination room
body From Slack: {{input.event.text}}

If you don't want messages without text to fail, place a "Branch" before it. Use "Add condition" to set "Has a value" for input.event.text, and proceed to posting only when it matches.

To build it in chat, choose "Build in chat" under "Create" and ask something like:

Build a workflow that receives Slack messages as input.event and posts input.event.text to Chatwork room 123456

Replace the room ID with the actual number.

4. Test the post, then publish

On the "Test" tab, use "Try this step" to pass values to the posting step and press "Try." It actually posts to Chatwork, so test it in a room with nobody else involved. If there are no problems, press "Publish version N" on the "Versions" tab. Triggers run the published version.

5. Add a service integration

On the "Triggers" tab, open "Add service integration" and proceed in order.

  1. Under "Which service to watch," choose the Slack connection
  2. Under "What triggers it," choose "Channel Message Received." Specify the channel in the filter fields, and set it to exclude bot posts (the field names show the English declarations from the Slack side)
  3. Check "What to do" and "Finish," and create it

6. Post a message and check

Post a message in the target channel and check the Chatwork room. Events don't always run the moment they arrive, so wait a little. Runs are kept as "Started by an event" under "Recent runs" on the "Runs" tab.

How it relates to approval

"Run external service" runs with the connection of the person who started it. For a trigger, that's the person who registered the trigger. To use someone else's connection, use "Lend to this workflow" under the step's "Credentials used to run."

An unattended run has nobody to check it. So depending on the connector's operation settings, it goes one of the following ways.

  • Writes that need confirmation by default: they run and are kept in the approval records
  • Operations an administrator set to "Always ask": they're refused, and the step fails
  • Operations set to "Forbid": they're refused, and the step fails

When it doesn't work

  • The step is refused with "Always ask" or "Forbid": Ask an administrator to check the setting for the Chatwork posting operation. "Always ask" can't be used for unattended runs
  • The posting step fails with 403 or 401: 403 means the token's owner isn't a member of the room or lacks permission; 401 means the token is invalid
  • Posts keep bouncing back and forth: If the reverse integration is also running, forwarded posts get forwarded again. Exclude bot posts with the filter on the Slack side
  • Only some messages fail: They may be messages without text, such as file-only posts. Look at the input under "Recent runs" and add a "Branch"

FAQ

Can posts appear under a shared company name?

Chatwork posts appear under the name of the token's owner. If you want a shared name, prepare an account for that purpose and connect with that account's token.

Are thread replies forwarded too?

There's a declaration that lets you specify this with is_thread_reply in the filter. Check the field on the actual screen and set it.

Can I also send Chatwork posts to Slack?

Yes, but the mechanism is different. Chatwork events aren't in the service integrations, so you receive them with a webhook. See How to forward Chatwork to Slack.

Related guides

Sources

Related featureConnect business tools to AI over MCPSamurai App connects your business tools to AI over MCP. Operate accounting and HR SaaS from chat within each person's own permissions, call the agent from Slack or Teams, and use it from outside AI clients over MCP.

More automation examples

See every way to connect and automate Slack

See every way to connect and automate Chatwork

Back to How-to articles

Everyday work comes together, connects, and becomes the company's strength.

Contact usOpen Samurai App

See the demoContact us