How to Auto-Post an RSS Feed to Rubika Channels and Groups

Updated: 2026-09-28

Short answer: connect a Rubika bot with its token and the chat ID of your channel or group under Accounts → Add new Rubika account. Then open الأهداف → Add feed, choose Rubika in Target settings and add your feed under Add source (Type = RSS feed, Link = your feed address). Each new item is posted as text with a link, or as an image with a caption. Persian right-to-left text is supported. Rubika is included from the Professional plan.

Rubika is an Iranian messaging platform, and unlike the other two in this group it accepts feeds into both channels and groups — which changes what you can sensibly send. This guide is the long version; the auto-post RSS to Rubika page has the short one.

Channels and groups are different audiences

A channel is a broadcast surface: you publish, subscribers receive, and nobody replies in line. A group is a conversation, and a feed posting into one is a participant rather than a publisher.

Because Rubika supports both, and because PostRSS lets you point different feeds at different chats, the useful pattern is to treat them differently. A channel can take your full publishing feed. A group — especially one you do not administer — should get a narrow, genuinely relevant feed, or nothing at all. The tolerance for volume in a conversation is far lower than in a channel, and it is the sort of thing members raise quickly.

The bot, the token and the chat ID

PostRSS posts through your own Rubika bot, using its token and the chat ID of the destination. The bot needs rights to post in that chat; without them the result is silence rather than an error message.

Because the chat ID is a per-Target setting, one connected bot can serve several channels and groups with different feeds, which is the arrangement most people end up with.

Right-to-left text, handled properly

Persian is written right to left, and that creates two problems for any tool posting text it did not compose.

The first is direction: mixing a right-to-left title with a left-to-right URL can render in a confusing order if the message is assembled carelessly. The second is truncation. Persian is written in a connected script, and cutting a message at an arbitrary byte can split a character in half, producing a broken glyph at the end of the post.

PostRSS supports right-to-left Persian text and never cuts a post in the middle of a character. If you publish in Persian, that is the detail that decides whether the channel looks professional or looks automated in the wrong way.

Rubika next to the other Iranian destinations

Of the three Iranian messengers PostRSS supports, Rubika is the one that accepts groups as well as channels:

• Rubika — bot token and chat ID; channels and groups.
• Bale — a bot created with @BotFather inside the app, channels.
• Eitaa — an Eitaayar API token, no bot at all.

All three are on the Professional plan and all three handle Persian text correctly. Running the same feed into all three is a common setup, because the platforms are used by overlapping but distinct audiences.

What to send to a channel

A channel is a notification surface, and every post is something arriving on somebody's phone. Three habits keep subscribers:

• Send a filtered feed, not everything. If your site publishes several categories, point the channel at the one subscribers actually signed up for.
• Make the title carry the post. In a channel message the headline is most of what people see, so titles written to sit under a hero image on your own site often land flat.
• Check the image is real. A generic stock photo attached to every item trains people to ignore the posts; no image is better than a meaningless one.

None of that is automation advice, but a muted channel is worth nothing however reliably it is fed, and these are decisions you make once when choosing which feed to connect.

Setting it up, step by step

1. Create a Rubika bot and note its token and the chat ID of the channel or group it should post to.
2. In PostRSS, open Accounts and choose Add new Rubika account. Paste the bot token and the chat ID.
3. Open Targets and click Add feed. One feed going to one destination is one Target.
4. In Target settings, choose Rubika 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.

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 channel goes quiet, the feed is usually the cause. Open its URL in a browser first.

• Anything new since you connected it? Only items appearing after the Target starts running are posted.
• Do the titles stand alone? In a channel message the title does most of the work.
• Is there an image in the item? It has to be in the feed, not merely on the page the item links to.
• Absolute links? Relative URLs work on your site and break everywhere else.

Which plan includes it

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

When posts stop arriving

• The token was regenerated. The old one stops working immediately; paste the new value.
• The bot lost its rights in the channel. A bot that is not an administrator cannot publish, and the symptom is silence.
• The channel identifier is wrong. Check it against the channel you actually want.
• Nothing new in the feed. Only items appearing after the Target starts running are posted.

Frequently Asked Questions

Can Rubika receive posts in a group as well as a channel?

Yes. Rubika accepts both, and different feeds can point at different chats. The editorial rule is that a group tolerates far less volume than a channel.

What do I need to connect?

A Rubika bot token and the chat ID of the channel or group. The bot needs rights to post there.

Is Persian text supported?

Yes, including right-to-left rendering, and posts are never cut in the middle of a character.

When do posts include an image?

When the feed item carries one; otherwise the item is posted as text with a link back to your article.

Can one bot serve several chats?

Yes. The chat ID is a Target setting, so one connected bot can post different feeds into different channels and groups.

Which plan includes Rubika?

The Professional plan, alongside Bale and Eitaa.

The bottom line

Rubika takes a bot token and a chat ID, and it is the one of the three that also posts into groups. Keep the full feed for channels and send groups something narrower. Persian text is handled correctly throughout. It is included from the Professional plan.