
Updated: 2026-09-28
Short answer: add the Incoming Webhook app from the Zoom App Marketplace to the Zoom Team Chat channel you want posts in, and paste the webhook details it gives you into PostRSS under Accounts → Add new Zoom Team Chat account. Then open เป้าหมาย → Add feed, choose Zoom Team Chat in Target settings and add your feed under Add source (Type = RSS feed, Link = your feed address). Each new item is posted to the channel as a message with a link to the article. The Incoming Webhook app needs a paid Zoom plan, and your Zoom admin may need to approve it. Zoom Team Chat is included from the Professional plan.
Zoom is known for video, but most organisations that run Zoom also run Zoom Team Chat, and it quietly becomes where a lot of day-to-day conversation happens — especially in companies that never adopted a separate chat tool. If that describes yours, the channel your colleagues already have open is a better place for your release notes than an email nobody reads. This guide is the long version; the auto-post RSS to Zoom Team Chat page has the short one.
Zoom Team Chat differs from most of the other webhook destinations in one practical way, and it is better to find out now than after you have set everything up.
Neither is something PostRSS can work around — they are Zoom's rules about its own marketplace. Both are usually a short conversation rather than a real obstacle, but they are the reason a Zoom setup sometimes takes a day longer than a Mattermost or Zulip one.
Each new feed item arrives as a message with a link to the article. It is deliberately brief. A work channel scrolls quickly, and the job of the message is to tell people something exists and let them decide whether to open it — not to reproduce the article inside the chat.
One behaviour to know before connecting anything: PostRSS publishes items that appear in the feed after the Target starts running. It does not import the back catalogue, which is deliberate — the alternative is a channel flooded with years of archive on its first day.
The discipline that keeps any of this welcome is sending less than you could. If your site publishes several categories, point the channel at the category feed that concerns that team rather than at everything. A channel people mute is worth nothing however reliably it is fed.
Zoom Team Chat is included from the Professional plan, together with the other team-chat destinations. Each channel you connect is one Target, and your plan sets how many Targets and how many posts a month you get. The current limits are on the pricing page, and the full lineup of 66 networks is on the supported networks page. The Zoom Team Chat page has the short version of the setup.
Nobody picks Zoom Team Chat the way they pick Slack or Mattermost. It arrives with Zoom, and in organisations that already pay for Zoom licences it quietly becomes the default because there is no second purchase to justify. That is its strength as a destination: your colleagues are already there, and no one has to be persuaded to install anything.
Compared with the alternatives, the practical differences are the two prerequisites above. Google Chat, Mattermost, Zulip and Webex all hand you a webhook without a plan requirement or a marketplace approval step. Zoom asks for both. Against that, it is the only one of them that is already open on the screen of everyone who joins your meetings.
If your organisation runs both Zoom and a dedicated chat tool, the sensible pattern is not to choose: connect both, and send each the feed that suits its audience. Every destination is another Target, and the same feed can serve as the source for as many as you need.
Yes. The Incoming Webhook app that Zoom Team Chat uses is not available on free Zoom accounts, so there is no webhook to connect. This is Zoom's own requirement rather than a PostRSS one.
Possibly. Many organisations restrict the Zoom App Marketplace so that apps must be pre-approved. If yours does, the Incoming Webhook app has to be allowed before you can add it to a channel.
No. The Incoming Webhook app already exists in the marketplace; you add it to a channel and copy the details it gives you. There is nothing to develop, publish or submit for review.
Yes. Each channel is a separate Target with its own webhook, and the same feed can be added as a source on each of them. In practice it is usually better to send each team the feed that concerns it.
No. An incoming webhook only sends. PostRSS has no visibility into the conversation and cannot respond to anything posted there.
PostRSS checks each feed every 5 minutes on standard plans and every minute on Enterprise, so a new article normally reaches the channel within a few minutes of going live.
Zoom Team Chat is straightforward to connect once the two Zoom-side prerequisites are met: a paid plan and, in many organisations, admin approval for the Incoming Webhook app. After that it is a webhook like any other — paste it into PostRSS, point a Target at the right feed, and the team sees each new item where it already works. It is included from the Professional plan.
What changed in the networks, what broke, and how to fix it before it costs you reach.