How to Auto-Post RSS to Chatwork Rooms (2026)

Updated: 2026-09-28

Short answer: create an API token in your Chatwork settings and paste it into PostRSS under Accounts → Add new Chatwork account. Then open Cibles → Add feed, choose Chatwork in Target settings, pick the room, and add your feed under Add source (Type = RSS feed, Link = your feed address). Each new item is posted as a message with its text and a link. Chatwork is included from the Professional plan.

Chatwork is the business chat tool that dominates in Japan the way Slack does elsewhere — used across hundreds of thousands of companies, and frequently the only chat application a Japanese organisation has. If your audience or your colleagues are there, it is the room your updates should reach. This guide is the long version; the auto-post RSS to Chatwork page has the short one.

An API token, not a webhook

Most team-chat destinations use an incoming webhook tied to one channel. Chatwork works differently: you create an API token in your own account settings, and the token acts on behalf of your account.

That difference has two consequences. First, you choose the room inside PostRSS rather than baking it into the credential, so changing the destination does not mean creating a new connection. Second, the token carries your account's permissions — it can reach the rooms you can reach — which makes it a more powerful credential than a single-channel webhook and worth protecting accordingly.

If your organisation is careful about this, the tidy arrangement is a dedicated account for automated posting, with access only to the rooms that should receive feeds. Revoking its token then affects nothing else.

Choosing the room

The room is a Target setting, so different feeds can go to different rooms from the same connected account. In practice that maps neatly onto how Chatwork is used: a room per project or per client, and a feed pointed at the room it concerns.

Chatwork rooms are often shared with clients rather than being purely internal, which is worth remembering before connecting anything. A room containing a customer is a place for release notes and service announcements, not for the whole company blog.

What belongs in a Chatwork room

• Release notes and maintenance notices for a room shared with a client.
• Status-page incidents for an internal operations room.
• Your own publishing, for the team that talks to customers.
• Vendor and regulatory feeds, where a room already exists for that subject.

The discipline is the same everywhere: send the room the feed it would have subscribed to, not everything you publish.

Setting it up, step by step

1. Create an API token in your Chatwork settings.
2. In PostRSS, open Accounts and choose Add new Chatwork account. Paste the API token.
3. Open Targets and click Add feed. One feed going to one destination is one Target.
4. In Target settings, choose Chatwork and the account you just connected. Pick the room where new articles should be posted.
5. Click Add source. Set Type to RSS feed and paste your feed address into Link. Save.
6. Check the first item that arrives. PostRSS checks the feed every 5 minutes, and every minute on Enterprise plans.

Chatwork next to the Western tools

Outside Japan, Chatwork is almost unknown; inside it, assuming a partner uses Slack is frequently wrong. For companies doing business in both directions, the practical answer is not to choose — connect both, and let each audience read in the tool it actually opens.

The technical difference worth noting is the credential model. Slack, Mattermost, Zulip and most of the rest use a per-channel incoming webhook, so the destination is fixed inside the credential. Chatwork uses an account-level API token with the room chosen separately, which is more flexible and correspondingly more powerful — another reason a dedicated posting account is worth setting up in a larger organisation.

If your Japanese operation also runs a blog, the Japanese blogging platforms on the same plan — Hatena Blog, Livedoor Blog, FC2 Blog and Qiita — are worth connecting from the same feed.

What the room sees

Each new feed item is posted as a message with its text and a link back to your article.

PostRSS publishes items that appear in the feed after the Target starts running. It does not import the back catalogue — the alternative would be a destination flooded with years of archive on its first day.

Check the feed before you check the integration

When a destination goes quiet, the feed is the more likely cause. Open the feed URL in a browser first.

• Has anything been published since you connected it? Only items appearing after the Target starts running are posted.
• Do the titles stand alone? Away from your site, the title is doing most of the work.
• Are the links absolute? Relative URLs work on the site and break everywhere else.
• Does the URL return XML? A feed address that returns an HTML error page produces silence rather than an error.

All four are fixed in your content system rather than at the destination.

Which plan includes it

Chatwork is included from the Professional plan. Each destination you connect counts as one Target, and your plan decides how many Targets and how many posts a month you get. An annual subscription is cheaper than paying monthly. Current limits per tier are on the pricing page, and the full lineup of 66 networks is on the supported networks page. The Chatwork page has the short version of the setup.

When messages stop arriving

• The token was regenerated or revoked. Tokens are managed in your Chatwork settings and stop working the moment they change.
• The account lost access to the room. The token carries your account's permissions; if the account leaves the room, posting stops.
• The room was archived or deleted. Re-select a room in Target settings.
• Nothing new in the feed. Items appearing after the Target starts running are the ones that get posted.

Frequently Asked Questions

Do I need a webhook for Chatwork?

No. Chatwork uses an API token created in your own account settings, and the room is chosen inside PostRSS rather than being fixed in the credential.

Which account should the token belong to?

For a small setup, your own is fine. In an organisation that is careful about access, a dedicated account with rights only to the rooms that receive feeds is tidier, because revoking its token affects nothing else.

Can I send different feeds to different rooms?

Yes. The room is a Target setting, so one connected account can serve several rooms with different feeds.

Is it safe to connect a room shared with a client?

Technically yes, editorially be careful. Client-facing rooms suit release notes and service announcements; they do not suit your whole blog.

Can PostRSS read messages in the room?

No. PostRSS posts and nothing else.

Will connecting a feed post our old articles?

No. Only items appearing after the Target starts running are published.

Which plan includes Chatwork?

The Professional plan, alongside the other chat destinations and the Japanese blogging platforms.

The bottom line

Chatwork is the chat tool most Japanese companies actually use, and it connects with one API token rather than a per-channel webhook — which makes the room a setting you can change rather than a credential you have to recreate. It is included from the Professional plan.