RSS to Google Chat, Mattermost, Webex and Zulip: Team-Chat Notifications From Any Feed

Updated: 2026-09-28

Short answer: all four work the same way: create an incoming webhook in the space, channel or organisation you want posts in, copy its URL, and paste it into PostRSS under Accounts → Add new <platform> account. Then open Sihtplatvormid → Add feed, choose the platform in Target settings and add your feed under Add source (Type = RSS feed, Link = your feed address). Each new item arrives as a message with a link to the article. There is no app to build and nothing to get approved. All four are included from the Professional plan.

Google Chat, Mattermost, Webex and Zulip have almost nothing in common as products. One is part of Google Workspace, one is the open-source Slack alternative that organisations self-host, one is Cisco's enterprise collaboration suite, and one is the threaded chat tool beloved of open-source projects and universities. What they share is the mechanism that matters here: an incoming webhook, which is the shortest path from a feed to a room.

Why the webhook is the whole trick

Publishing to a social network usually means registering as a developer, creating an application, requesting permissions and waiting for a review. An incoming webhook skips every step. Someone with rights to the space creates it, the platform hands back a URL, and anything holding that URL can post into the room. Nothing is submitted, nothing is approved, and removing it is one click.

That has a security consequence worth stating plainly: the URL is the credential. There is no username, no token exchange and no second factor. Anyone who has the URL can post into your team's channel, so it does not belong in a public repository, a shared document or a support ticket.

Creating the webhook on each platform

Google Chat

Open the space, go to Apps & integrations, and add a webhook. Google Chat hands you a URL, and that is all PostRSS needs — there is no Chat app to build, publish or get approved, which is the part that stops most teams before they start.

Mattermost

Create an incoming webhook under Integratsioonid. Mattermost Cloud and self-hosted installs both work; a self-hosted server needs to be reachable over HTTPS on port 443, which is the normal setup but worth checking if yours sits behind a VPN or on a non-standard port.

Webex

Add the Incoming Webhooks integration to the space and copy its URL. No bot account is needed, which matters in organisations where creating a bot identity means a conversation with IT.

Zulip

Create an incoming webhook in your Zulip organisation and paste its URL. As with Mattermost, self-hosted Zulip works provided the server is reachable over HTTPS on port 443.

Setting it up, step by step

1. Create the incoming webhook on the platform, as described above, and copy its URL.
2. In PostRSS, open Accounts and choose Add new Google Chat, Mattermost, Webex or Zulip account. Paste the webhook URL. That single value is the entire authorisation.
3. Open Targets and click Add feed. One feed going to one destination is one Target.
4. In Target settings, choose the platform and the account you just connected. Different feeds can point at different spaces, so each team only gets the updates that concern it.
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 (every minute on Enterprise plans), so the wait is short.

What the room sees

Each new feed item arrives as a message carrying the item and a link back to the article. It is deliberately compact. A working channel scrolls fast, and a full article pasted into it is worse than a headline someone can click — the point is to tell the team something happened, not to reproduce the piece.

Where this is genuinely useful

• Release notes and changelogs. Engineering teams already have a channel; a feed keeps it current without anyone remembering to post.
• Status pages. Most status providers publish an RSS feed of incidents. Pointing it at the on-call channel is five minutes of setup that pays for itself the first time something breaks.
• Competitor and industry monitoring. A filtered news feed into a marketing channel beats fifteen people separately subscribing to the same newsletter.
• Your own publishing. Sales and support teams usually find out about a new article last. A feed into their channel fixes that permanently.
• Regulatory and security advisories. Vendor advisories almost always have a feed, and a compliance channel is the right place for them.

One feed, several platforms — and when that is the wrong idea

Because every destination is just another Target, the same feed can go to a Google Chat space, a Mattermost channel and a Zulip stream at once. In organisations that ended up with two or three chat tools after an acquisition, that is genuinely useful.

It is also the easiest way to annoy everybody simultaneously. The better pattern is one feed per audience rather than one feed everywhere: engineering gets the changelog, marketing gets the blog, on-call gets the status page. Most CMSes and status providers publish per-category feeds, and using them is the difference between a channel people read and a channel people mute.

What it does not do

PostRSS publishes items that appear in the feed after the Target starts running. Connecting an established feed does not import its back catalogue, which is deliberate — the alternative is a destination flooded with years of archive on day one.

None of these integrations read the room, reply to messages, or act on anything said in the channel. Traffic is strictly one way: new feed item in, message out.

Which plan includes it

Google Chat, Mattermost, Webex and Zulip is included from the Professional plan. Each destination you connect counts as one Target, and your plan sets how many Targets and how many posts a month you get. An annual subscription is cheaper than paying monthly. The current limits for every tier are on the pricing page, and the full list of 66 networks is on the supported networks page. Each has its own page: Google Chat, Mattermost, Webex ja Zulip.

When messages stop arriving

• The webhook was deleted or regenerated. The old URL stops working immediately and nothing notifies you. Create a new one and update it in PostRSS.
• The space was archived or the channel renamed. A webhook belongs to one space; if it is gone, so is the delivery.
• A self-hosted server is unreachable. Mattermost and Zulip installs must be reachable over HTTPS on port 443. Servers behind a VPN or on a custom port will not receive posts.
• Nothing new in the feed. PostRSS publishes items that appear after the Target starts running, so an unchanged feed correctly produces nothing.

Frequently Asked Questions

Do I need to build a chat app or bot for any of these?

No. All four use an incoming webhook, which is created inside the space or organisation itself. There is no application to build, publish or get approved, and Webex specifically needs no bot account.

Is the webhook URL sensitive?

Yes. It is the entire authorisation — anyone holding it can post into that room. Treat it like a password: keep it out of public repositories, shared documents and tickets.

Do self-hosted Mattermost and Zulip servers work?

Yes, as long as the server is reachable over HTTPS on port 443. A server behind a VPN or listening on a non-standard port will not receive posts.

Can one feed post into several platforms at once?

Yes. Each space or channel is its own Target, and the same feed can be added as a source on all of them. In practice it is usually better to send different feeds to different audiences than the same feed everywhere.

Will the integration read or reply to messages in the channel?

No. An incoming webhook only sends. PostRSS has no visibility into the conversation and cannot respond to anything posted there.

Which plan do I need?

All four are included from the Professional plan, along with the other team-chat destinations such as Rocket.Chat, Zoom Team Chat, Pumble, Flock, RingCentral, Zoho Cliq, Twist and Stoat.

The bottom line

Google Chat, Mattermost, Webex and Zulip are among the quickest destinations to connect because the incoming webhook needs no developer account and no approval. Create it in the space, paste the URL into PostRSS, point a Target at the right feed for that audience, and the team sees each new item in the tool they already have open. All four are included from the Professional plan.