How to Auto-Post RSS to Twist (2026)

Updated: 2026-09-28

Short answer: add an incoming webhook integration to your Twist channel and paste its URL into PostRSS under Accounts → Add new Twist account. Then open Sasaran → Add feed, choose Twist in Target settings and add your feed under Add source (Type = RSS feed, Link = your feed address). Each new item is posted with its text and a link. Twist is included from the Professional plan.

Twist is team chat for people who decided that real-time chat was the problem. Everything lives in threads, nothing demands an immediate answer, and the tool is explicitly designed to be read later. That makes it a good destination for some feeds and a bad one for others, which is worth settling before you connect anything. This guide is the long version; the auto-post RSS to Twist 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.

Twist is built for not-right-now, and that changes what you send

Twist is the outlier among team-chat tools. It was built by the Doist team around the argument that real-time chat is a productivity problem rather than a solution, so it organises everything into threads that people read when they choose to. There are no presence indicators pushing you to reply immediately and no expectation that a message is seen within minutes.

That design has a direct consequence for feeds. A destination where people deliberately read later is a poor place for anything urgent — a status-page incident posted to Twist may sit unread for hours, which is exactly what the tool is for and exactly wrong for an outage. It is an excellent place for everything that benefits from being read properly: long-form articles, release notes with detail, research, industry analysis.

If you run Twist alongside something real-time, the useful split is obvious: urgent feeds go to the real-time tool, considered ones go to Twist.

What belongs in a Twist channel

• Your own long-form publishing. Articles people will actually read rather than skim.
• Release notes and changelogs that carry enough detail to be worth a thread.
• Industry and research feeds, filtered, for teams that need to stay current.
• Competitor or market monitoring, where a day's delay costs nothing.

What to keep out: anything where the value expires. Twist will deliver it faithfully and nobody will see it in time.

A thread per item, and why that is an advantage

Because Twist is thread-first, each posted item becomes something a colleague can reply to without derailing a channel. An article that prompts a discussion keeps that discussion attached to it, and the thread is still readable three months later.

That is a meaningfully different outcome from a fast-scrolling channel, where a good conversation about a link is buried by lunchtime. For teams that use feeds as an input to actual decisions rather than as ambient awareness, it is the reason to prefer Twist as the destination.

Setting it up, step by step

1. Add an incoming webhook integration to the Twist channel that should receive the posts, and copy its URL.
2. In PostRSS, open Accounts and choose Add new Twist 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 Twist 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

Twist 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 Twist 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

Is Twist a good place for urgent feeds like status pages?

No. Twist is deliberately asynchronous — people read threads when they choose to, not immediately. Send urgent feeds to a real-time tool and keep Twist for content that benefits from being read properly.

Do I need to build a Twist integration?

No. You add an incoming webhook integration to the channel from inside Twist and paste its URL into PostRSS.

Is the webhook URL sensitive?

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

Can colleagues reply to the posted items?

Yes, in Twist's own threads. PostRSS does not see those replies — an incoming webhook is send-only — but the conversation stays attached to the item for as long as the thread exists.

Can one feed go to several Twist channels?

Yes. Each channel has its own webhook and is a separate Target.

Will connecting a feed post our archive?

No. Only items appearing after the Target starts running are published.

Which plan includes Twist?

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

The bottom line

Twist takes a standard incoming webhook, and the interesting decision is editorial rather than technical: send it the feeds that reward being read properly, and keep the urgent ones somewhere real-time. It is included from the Professional plan.