How to Auto-Post RSS to Stoat (Formerly Revolt)

Updated: 2026-09-28

Short answer: create a channel webhook in your Stoat channel settings and paste its URL into PostRSS under Accounts → Add new Stoat account. Then open Target → Add feed, choose Stoat 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 with its text and a link. Self-hosted instances work too, as long as they are reachable over HTTPS on port 443. Stoat is included from the Professional plan.

Stoat is the new name of Revolt, the open-source chat platform that grew up as a Discord alternative for people who wanted the same shape of product without the same company behind it. If you followed a Revolt server, you are already on Stoat — the rename did not move anything. This guide is the long version; the auto-post RSS to Stoat page has the short one.

What the rename means for you

Practically, nothing. Existing servers, channels and accounts carried over, and the webhook mechanism is unchanged. The only thing worth updating is your own documentation: if an internal runbook still says Revolt, the person who reads it in six months will be looking for a product that no longer answers to that name.

PostRSS lists the destination as Stoat (formerly Revolt) for the same reason — so that people searching for either name find it.

How the connection works

A channel webhook is created inside the channel's own settings by somebody with rights to manage it. Stoat returns a URL, and anything holding that URL can post into that one channel. There is no bot to invite, no application to register and nothing to get approved.

As with every webhook destination, the URL is the entire credential. Keep it out of public repositories and shared documents, and regenerate it if it leaks.

Self-hosting, and the one requirement

A large share of Stoat use is self-hosted — that is much of the point of an open-source Discord alternative. PostRSS posts to your instance over the internet, so it has to be reachable from outside over HTTPS on port 443.

That is the normal configuration for any instance with a public address. What will not work is a server reachable only inside a private network or behind a VPN, or one listening on a non-standard port. If your instance is deliberately private in that sense, no external service can reach it, and a script running inside the same network is the honest answer instead.

What belongs in a Stoat channel

Stoat servers are communities more often than workplaces, which changes the calculation. A community channel tolerates a feed when the feed is what the community is there for:

• Project releases and changelogs for an open-source project's own server.
• Your blog, where the community follows the author rather than the company.
• Status and uptime feeds for a service the community uses.
• A filtered news feed on the subject the server exists for.

What fails is treating somebody else's community server as a distribution channel. Ask the administrators first; on a self-hosted server that is one person, and they will tell you plainly.

Stoat next to Discord

The comparison is unavoidable, because Revolt was built as a Discord alternative and Stoat inherits that shape. From an integration standpoint the two behave almost identically: a channel webhook, no bot to invite, a message with text and a link. PostRSS supports both, and both sit on the Professional plan.

The differences are about ownership. Discord is one company's service, with one moderation policy and one set of rules that can change. Stoat is open source, so a community can run its own instance and answer to nobody. For a project that cares about that — and most projects that moved from Discord to Revolt did — it is the whole reason the platform exists.

If you run both, connecting both costs nothing extra: the same feed is the source for two Targets, and communities that chose one platform over the other rarely overlap much.

Setting it up, step by step

1. Create a webhook in your Stoat channel settings and copy its URL.
2. In PostRSS, open Accounts and choose Add new Stoat account. Paste the webhook URL.
3. Open Targets and click Add feed. One feed going to one destination is one Target.
4. In Target settings, choose Stoat and the account you just connected.
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.

What the channel sees

Each new feed item arrives 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

Stoat 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 Stoat page has the short version of the setup.

When messages stop arriving

• The webhook was deleted or regenerated. The old URL stops working immediately and nothing notifies you.
• A self-hosted instance is unreachable. It must answer over HTTPS on port 443 from outside your network.
• The channel was deleted. A webhook belongs to one channel.
• A certificate expired. An external service will refuse a connection that a browser might have been told to accept.

Frequently Asked Questions

Is Stoat the same thing as Revolt?

Yes. Stoat is the new name of Revolt, and existing servers, channels and accounts carried over unchanged. Only your internal documentation needs updating.

Do I need to create a bot?

No. A channel webhook is created in the channel's settings and its URL is the whole connection. There is no bot to build or invite.

Does a self-hosted Stoat instance work?

Yes, as long as it is reachable over HTTPS on port 443. An instance that is only reachable inside a private network cannot receive posts from an external service.

Is the webhook URL sensitive?

Yes. It is the entire authorisation, so anyone holding it can post into that channel.

Can PostRSS read messages in the channel?

No. A webhook only sends. PostRSS cannot see the conversation or reply to it.

Should I connect a feed to a community server I do not run?

Ask the administrators first. On a self-hosted server that is usually one person, and an unannounced feed in somebody else's community is the quickest way to have it removed.

Which plan includes Stoat?

The Professional plan, alongside the other chat destinations.

The bottom line

Stoat is Revolt under a new name, and it connects the way its Discord-shaped design suggests: one channel webhook, no bot, nothing to approve. Self-hosted instances work provided they answer over HTTPS on port 443. It is included from the Professional plan.