How to Auto-Post an RSS Feed to BAND Groups (2026)

Updated: 2026-09-28

Short answer: BAND is currently being tested. Everything is built and working on the PostRSS side; publishing is awaiting approval of the app by BAND, so you can see exactly how it will work but cannot publish through it yet. When it goes live, you will sign in through the official BAND login under Accounts → Add new BAND account — PostRSS never sees your password — choose the bands you are allowed to post in, then open Цели → Add feed, choose BAND in Target settings and add your feed under Add source. Each item will be posted with its title, text and a link. BAND does not accept pictures through its API. BAND is assigned to the Professional plan.

BAND is a group-communication app built for communities rather than companies: clubs, school classes, sports teams, church groups, hobby societies. It is widely used in Korea, and has a real presence in Taiwan, Japan and the United States, where it tends to be the tool a group adopts when a chat thread stops being enough. This guide is the long version; the auto-post RSS to BAND page has the short one.

Status: being tested, and what that means

Being straight about this matters more than the rest of the article. The integration is built and working on our side, and it is waiting on approval of the app by BAND. Until that approval arrives, publishing does not happen.

The practical advice that follows is simple: do not choose a plan today because BAND is on its list. Everything described here is how it will work, not how it works right now. If BAND is the only destination you need, wait for the approval rather than subscribing in advance.

The network page for BAND carries the same status, and it will change there first when the situation changes.

How the connection will work

Connecting goes through BAND's own OAuth login. You sign in on BAND, approve the connection there, and PostRSS receives a token — it never sees your password, and access can be revoked from your BAND account at any time.

After signing in you choose which bands new items should go to. That list is limited to the bands where you are allowed to post, which is the right constraint: a group-communication app is full of spaces that belong to other people, and the permission model rather than the tool is what decides where you can publish.

Text and a link, and no pictures

Each item will be posted with its title, text and a link to the article. Pictures are not included, and that is a BAND limitation rather than a choice: BAND does not accept images through its API.

It is worth knowing in advance because it changes what suits the destination. A feed whose value is visual will arrive as text; a feed of announcements, schedules, newsletters and articles will arrive intact. If images matter to your audience, the honest answer is that BAND is not where that content should go.

What BAND is actually for

• Clubs and societies publishing a newsletter or a blog their members already follow.
• Schools and classes, where BAND frequently replaces a mailing list.
• Sports teams with a schedule or results page that produces a feed.
• Community organisations whose website is updated more often than anyone remembers to tell the group.

The common thread is that the group already exists and already reads BAND. This is not a channel for reaching strangers; it is a way of keeping people who already joined something informed without a volunteer having to copy links every week.

Etiquette in a community space

BAND groups are small, personal and often moderated by one volunteer. Two things matter more here than on a public network.

First, ask before automating a band you do not run. The permission model will stop you posting where you are not allowed, but being technically permitted and being welcome are different things.

Second, send less than you could. A group that joined for match schedules does not want your whole blog. Point the Target at the narrow category feed that matches why the group exists, and the posts will be read instead of muted.

Setting it up, step by step

1. Have your BAND account ready — the connection is made through BAND's own login, once the app is approved.
2. In PostRSS, open Accounts and choose Add new BAND account. Sign in through the official BAND login and approve the connection.
3. Open Targets and click Add feed. One feed going to one destination is one Target.
4. In Target settings, choose BAND and the account you just connected. Choose the bands where you are allowed to post.
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.

Get the source feed right first

Because BAND carries text rather than images, the feed matters in a specific way.

• Titles that stand alone. With no picture to carry the post, the headline does all the work.
• Full text or a useful summary. Either is fine; an empty description is not.
• Absolute links. Relative URLs work on your site and break everywhere else.
• Anything new since you connected it. Only items appearing after the Target starts running are posted.

Which plan includes it

BAND 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 BAND page has the short version of the setup. It is assigned to that tier and will publish from it once BAND approves the app.

When it goes live and posts do not arrive

• The app is still awaiting approval. Until BAND approves it, nothing publishes. This is the expected state today.
• Access was revoked on BAND. Reconnect the account under Accounts; revoking happens in your BAND settings.
• You are not allowed to post in that band. The list of bands is limited by your permissions inside BAND itself.
• You expected a picture. BAND does not accept images through its API, so items arrive as title, text and a link.

Frequently Asked Questions

Can I use BAND with PostRSS today?

Not yet. The integration is built and working on our side, but publishing is awaiting approval of the app by BAND. Do not choose a plan today because BAND appears on its list.

Will pictures be included in the posts?

No. BAND does not accept images through its API, so each item is posted with its title, text and a link. That is a platform limitation rather than a choice.

Does PostRSS see my BAND password?

No. Connecting goes through BAND's own login, where you sign in and approve it. PostRSS receives a token and never the password.

Which bands can I post to?

Only the ones where you are already allowed to post. BAND's own permission model decides the list, and being permitted is not the same as being welcome — ask the moderator of a band you do not run.

Which plan is BAND on?

The Professional plan. It is assigned to that tier and will publish from it once the app is approved.

Where will I see that it has gone live?

The BAND network page carries the current status and will change there first.

What should I send to a band?

The narrow feed that matches why the group exists — schedules, announcements, the newsletter — rather than your whole site. Community groups mute high-volume sources quickly.

The bottom line

BAND is built, tested on our side and waiting on approval from BAND itself, so treat everything here as a description of how it will work rather than how it works today. When it goes live it will be a sign-in, a choice of bands, and text-and-link posts into groups that already exist. It is assigned to the Professional plan.