How to Auto-Post RSS to Flock Channels (2026)

Updated: 2026-09-28

Short answer: add an incoming webhook to your Flock channel and paste its URL into PostRSS under Accounts → Add new Flock account. Then open Στόχοι → Add feed, choose Flock 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. Flock is included from the Professional plan.

Flock is team chat aimed at getting out of the way: channels, threads, a few integrations, and not much else to configure. For an RSS feed that simplicity is welcome — there is one thing to create and one URL to copy. This guide is the long version; the auto-post RSS to Flock page has the short one.

How the connection works

The connection is an incoming webhook: somebody who can administer the channel creates it, the platform returns a URL, and anything holding that URL can post into that one place. No developer account, no application to submit, nothing to get approved.

The security consequence is blunt — the URL is the credential. There is no username and no second factor, so keep it out of public repositories, shared documents and support tickets, and treat regenerating it as the way to revoke access.

Set it once, and then leave it

The argument for automating a channel at all is not that posting a link is hard. It is that doing it reliably, every time, for months, is something people stop doing during a busy week — and a channel that is current half the time is worse than one nobody expects to be current at all, because people stop trusting it.

A feed removes the decision. Once the webhook is connected, new articles reach the channel whether or not anyone remembered, whether or not the person who used to post them is on holiday, and whether or not it is a Friday afternoon. That consistency is the actual product here; the five minutes of setup is incidental.

What belongs in a Flock channel

Flock is used heavily by distributed teams and by organisations in India and South-East Asia where it has a strong presence. In both cases the channels tend to be team-shaped rather than company-shaped, which suits narrow feeds:

• A category feed matching the channel's subject, rather than the whole blog.
• Status and incident feeds for whoever is on call.
• Release notes for the team that ships or supports the product.
• A filtered industry feed, where the filter is doing real work.

The test is simple: if the people in that channel would not have subscribed to the feed themselves, it does not belong there.

One feed, several destinations

Because every channel is a separate Target, the same feed can go to a Flock channel, a Mattermost channel and a Telegram channel at once. That is genuinely useful in organisations that ended up with more than one chat tool, or during a migration from one to another — both can run in parallel and the feed keeps working throughout.

It is also the easiest way to irritate everyone simultaneously. The better pattern is one feed per audience rather than one feed everywhere, using the per-category feeds your content system already publishes.

Setting it up, step by step

1. Add an incoming webhook to the Flock channel that should receive the posts, and copy its URL.
2. In PostRSS, open Accounts and choose Add new Flock 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 Flock 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. It is deliberately compact: a working channel scrolls, and the job of the message is to say that something exists, not to reproduce it.

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 chat 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, so silence on an unchanged feed is correct behaviour.
• Do the titles stand alone? In a chat message the title is effectively the whole post; a feed shipping "Untitled" or a bare date produces messages nobody opens.
• Are the links absolute? Some generators emit relative URLs, which work on the site and break everywhere else.
• Does the URL return XML? A feed address that quietly returns an HTML error page produces silence rather than an error message.

All four are fixed in your content system. No destination can repair a feed that never carried the information.

Which plan includes it

Flock 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 Flock 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.
• The channel was archived or renamed. A webhook belongs to one channel; if it is gone, so is delivery.
• Permissions changed. Whoever created the webhook may no longer have rights to that channel.
• Nothing new in the feed. Items appearing after the Target starts running are the ones that get posted.

Frequently Asked Questions

Do I need to build a Flock app?

No. An incoming webhook is added to the channel from inside Flock, and its URL is the whole connection. There is nothing to develop or submit.

Is the webhook URL sensitive?

Yes. It is the entire authorisation, so anyone holding it can post into that channel. Keep it private and regenerate it if it leaks.

Can PostRSS read or reply to messages?

No. An incoming webhook only sends. PostRSS cannot see the conversation or respond to anything in it.

Can one feed reach several Flock channels?

Yes. Each channel has its own webhook and is a separate Target, and the same feed can be a source for all of them.

Will connecting a feed post our old articles?

No. Only items that appear after the Target starts running are posted, so an established feed does not backfill its archive.

How quickly do posts appear?

PostRSS checks each feed every 5 minutes on standard plans and every minute on Enterprise, so a new article normally arrives within a few minutes of going live.

Which plan includes Flock?

The Professional plan, alongside the other team-chat destinations.

The bottom line

Flock takes an incoming webhook and nothing else. Add it to the channel, paste the URL into PostRSS, point a Target at the feed that channel actually needs, and the updates arrive without anyone remembering to post them. It is included from the Professional plan.