Communication · Integration
Chatwork
Add Chatwork to your product for your customers, and give your AI agents governed access to it.
Chatwork is the business chat a great many Japanese companies run, and it has one structural difference from the western tools that changes what an integration is for. A task is a first-class object inside a room, with somebody responsible for it and a date it is due, so a message asking for something and the record that it was asked for are the same feature rather than two. That means your product can put work in front of a team, not just a notification they will scroll past. The rest is familiar: rooms with their members, messages with a mention notation for addressing a particular person, and files. Because every message is read by people, sends are deduplicated per event, so a timeout on your side does not leave two identical posts in a room a team is watching. fastn keeps each account's token per tenant and maintains the connector.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Chatwork account so notifications come from their workspace rather than a shared bot.
Post a message into the room a team already watches, addressed to the person who needs to act.
Create a task in a room with an assignee and a due date, so a request is tracked rather than scrolled past.
Read messages and task status back so your product knows whether something was picked up.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises what a room discussed and what was decided.
An agent creates a task for the right person from a request in a conversation, with the action attributed.
An agent reports which tasks in a room are overdue and who they belong to.
Example prompt
Post the deployment summary to the engineering room and create a task for the reviewer due tomorrow.
Set up Chatwork in 4 steps
- 01Enable the Chatwork connector in your fastn dashboard.
- 02Have each customer authorise their own Chatwork account so posts come from their workspace.
- 03Choose the rooms your product writes to, and map the task fields you set when creating one.
- 04Call it from your product and expose the same governed connection to your agents.
Why teams use the Chatwork integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Chatwork integration without building it. Your customers connect their own Chatwork account inside your product and work their messages, conversations and participants there, with no per-customer code on your side.
- Handle the part that actually costs time: anything sent is user-visible, so duplicates and misfires are immediately embarrassing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Chatwork update is not your on-call problem.
- One integration serves your product and your agents. The same governed Chatwork connection powers in-product features and gives AI agents scoped, audited access, so you put the right message in front of the right team automatically without wiring it twice.
Used by these teams
Compare with
Slack
Microsoft Teams
LINEOften used alongside
Tools the same teams tend to run next to Chatwork, across other categories.
Aircall
Calendly
Gong
Google CalendarChatwork integration FAQ
How do I add a Chatwork integration to my product?
Enable the Chatwork connector in your fastn dashboard, then let each customer authenticate their own Chatwork account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Chatwork client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Chatwork account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Chatwork account and only ever sees their own messages, conversations and participants. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Chatwork integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent summarises what a room discussed and what was decided.
Who maintains the Chatwork integration?
fastn does. When Chatwork changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does each customer connect their own Chatwork account?
Yes. Every customer authorises their own Chatwork account, so messages, meetings and notifications originate from their workspace under their permissions. You never proxy through a shared account, which also means a customer revoking access affects only their own connection.
How are duplicate notifications avoided?
Sends are deduplicated per event, so a retry after a network failure does not post the same message twice into a channel people are reading.
What can I build with the Chatwork integration?
A common starting point: let each customer connect their own Chatwork account so notifications come from their workspace rather than a shared bot. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Chatwork integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Chatwork does not change your per-connector cost. You can start free with 3 connected accounts.
Add Chatwork to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.