How to Auto-Post an RSS Feed to Feishu / Lark Groups (2026)

Updated: 2026-09-28

Short answer: create a custom bot inside the Feishu or Lark group you want posts to land in, copy its webhook address and its signing key, then in PostRSS open Accounts → Add new Feishu / Lark account and paste both. Open Στόχοι → Add feed, choose Feishu / Lark in Target settings and add your feed under Add source (Type = RSS feed, Link = your feed address). Every new item arrives in the group as a title, a short summary and a link. There is no developer registration and no app review — the bot belongs to the group. Feishu / Lark is included from the Professional plan ($10/month).

Feishu and Lark are the same product under two names: Feishu is the version used inside mainland China, Lark the international one. Both are ByteDance's workplace suite — chat, docs, calendar and approvals in one app — and both expose the same group bot mechanism, which is what makes automated posting into them straightforward.

Why a group bot and not an app

Publishing to most networks means registering as a developer, creating an application, requesting permissions and waiting for a review. A Feishu group bot skips all of that. It is created by a member of the group, it exists only inside that group, and it is addressed by a single webhook URL. Nobody approves it, nothing is published to a marketplace, and removing it is one click by anyone who can administer the chat.

The practical consequence is that setup takes about two minutes and does not involve your IT department, a company account or a Chinese business licence.

Creating the bot, step by step

1. Open the group you want posts delivered to. You need permission to manage the group's bots; in most organisations that means being an owner or administrator of the chat.
2. Open the group settings and find the Bots section (labelled Group Bot in some versions).
3. Add a bot and choose Custom Bot. Give it a name and description your colleagues will recognise — "Blog updates" beats the default.
4. Set the security option to signature verification. Feishu offers a choice here, and this is the one to pick. Copy the signing key it shows you.
5. Copy the webhook URL. It looks like https://open.feishu.cn/open-apis/bot/v2/hook/… on Feishu, or https://open.larksuite.com/open-apis/bot/v2/hook/… on Lark. Treat it as a credential: anyone holding it can post into the group.
6. In PostRSS, open Accounts → Add new Feishu / Lark account and paste the webhook address and the signing key.
7. Open Targets → Add feed, choose Feishu / Lark in Target settings, then Add source with Type = RSS feed and your feed address in Link. Save.

Why signature verification rather than keywords

Feishu's security options for a custom bot are a keyword list, an IP allowlist, or signature verification. The keyword option looks simplest and is the wrong choice for a feed. It works by rejecting any message that does not contain one of the words you listed, which means the moment you publish an article whose title happens not to include your keyword, the message is silently dropped. You would only find out by noticing the gap.

An IP allowlist is fragile for a different reason: it ties delivery to the addresses a service happens to send from today. Signature verification has neither problem. Each request carries a timestamp and a hash computed with the signing key, Feishu verifies it, and the content of the message is irrelevant to whether it is accepted.

What the group actually sees

Each new feed item arrives as a message carrying the item's title, a short summary drawn from the feed, and the link back to the original. It is clean and readable, and it is deliberately compact: a chat group scrolls, and a wall of full article text in a working channel is worse than a headline someone can click.

One honest limitation: a Feishu custom bot cannot attach images. Sending a picture through Feishu's API requires uploading it first and referencing the resulting image key, and that path is only open to a full registered application, not to a group webhook. So where DingTalk and WeCom render a card with a thumbnail, Feishu items arrive as text and a link. If images in the chat matter more than setup simplicity, that is the trade-off to know about in advance.

Rate limits and volume

A group bot is built for notifications, not for bulk delivery, and Feishu throttles a bot that posts too quickly. In practice this never bites an RSS feed: PostRSS checks each feed every 5 minutes and sends one message per new item, so even a busy publishing day is a handful of messages an hour. If you are importing a backlog or running several feeds into one group, stagger them across separate targets rather than firing everything into a single chat at once.

What to do when nothing arrives

• Signature errors. Re-copy the signing key; it is easy to grab a trailing space. If you regenerated the bot, both the webhook and the key change.
• The bot was removed from the group. Any administrator can delete it, and delivery stops immediately with no notice to you.
• Keyword security was left on. Messages that do not contain the listed word are rejected. Switch to signature verification.
• Nothing new in the feed. PostRSS publishes items that appear after the Target starts running, so a feed that has not updated produces nothing.
• Feishu and Lark mixed up. A webhook issued on open.feishu.cn belongs to a Feishu tenant, and one on open.larksuite.com to a Lark tenant. They are not interchangeable.

Group chats are not public feeds

This is the one thing worth being clear about before you set anything up. A group bot posts into a conversation — a team channel, a customer group, a community room. It does not publish to a public timeline, nobody outside the group sees it, and there is no follower count attached to it. That makes it excellent for internal distribution, release notes, support announcements and community updates, and useless as a marketing channel on its own.

If what you actually want is to publish articles to a Chinese public audience, the destination for that is a WeChat Official Account, which PostRSS supports from Professional Plus at $20/month for approved accounts. And to answer the question that always follows: Bilibili is not supported, and not because of a missing integration — its publishing API requires a Chinese legal entity, which puts it out of reach for a company registered elsewhere.

Which plan includes it

It is part of the Professional plan at $10/month, the same tier as Discord, Pinterest boards, VKontakte, Tumblr, Nostr, WordPress and Blogger. Feishu / Lark, DingTalk and WeCom all sit there together, so one subscription covers all three if your organisation uses more than one. Professional allows 10 targets and 10,000 posts a month; each group you post into is one target. An annual subscription is 20% cheaper. Exact limits per tier are on the pricing page, and the full lineup of 26 networks is on the supported networks page.

Frequently Asked Questions

Do I need a Feishu developer account to post into a group?

No. A custom group bot is created inside the group itself and needs no developer registration, no application and no review. That is the main reason this route is so much faster than publishing to a public social network.

Why does PostRSS ask for a signing key as well as the webhook?

Because signature verification is the security mode that works reliably for a feed. The alternative — a keyword list — silently drops any message whose text does not contain one of your keywords, which for article titles means unpredictable gaps.

Can Feishu posts include the article image?

No. A custom bot cannot attach images, because sending a picture requires uploading it through a registered application first. Items arrive as a title, a summary and a link. DingTalk and WeCom group bots do render a card with an image.

Does this work with Lark as well as Feishu?

Yes, and the setup is identical. The only difference is the domain in the webhook address: Feishu tenants issue open.feishu.cn webhooks, Lark tenants open.larksuite.com ones.

Can one feed post into several Feishu groups?

Yes. Each group is one Target, so add the feed as a source on as many Targets as you need. Professional allows 10 targets in total.

Is this a way to reach a public Chinese audience?

No. A group bot posts into a conversation, not to a public timeline. For publishing articles to a public Chinese audience, a WeChat Official Account is the destination, and Bilibili is not supported at all because its publishing API requires a Chinese legal entity.

The bottom line

Feishu and Lark are among the easiest destinations PostRSS supports, precisely because a group bot is a feature of the chat rather than a developer platform. Create the bot, choose signature verification, paste the webhook and the key, point a Target at your feed, and your team sees each new article in the channel they already have open. It is on the Professional plan at $10/month, alongside DingTalk and WeCom.