RSS Reader component (AI Flowi Workflow)
The catalogue describes RSS Reader as “Fetches and parses an RSS feed.” This is the feed-specific entry: rss_url is required, and Articles is returned through a Table-typed port.
RSS Reader is documented in the catalogue; not production-tested by Ai Flowi.
By Ai Flowi · Published
Catalogue reference
The compact RSS Reader interface is identified by data_source.RSSReaderSimple in AI Flowi Workflow 1.9.2, exported 9 October 2026; the component catalogue covers the wider inventory.
Inputs
RSS Reader exports just two settings: the required address and an optional timeout. Only rss_url has accepted connection metadata, which lists Message. On smaller displays, the RSS input table has its own horizontal scroll area for the remaining columns.
| Name | Type | Required | Accepted input types | Plain explanation |
|---|---|---|---|---|
rss_url | str | Yes | Message | Required RSS feed address accepting Message, used for the sample feed location below. |
timeout | int | No | Not listed | Optional integer timeout with no documented unit, default or allowed range. |
Outputs
| Display name | Name | Type |
|---|---|---|
| Articles | articles | Table |
Articles is named articles and declared Table. That gives a connection type, but no feed-field mapping or example row; inspect the table before selecting article fields.
When to use RSS Reader
Choose RSS Reader when the source is a known RSS feed URL and the next step expects tabular articles. For text extraction from that table, use the Parser reference to configure its required inputs rather than assuming a Message result.
When to choose another component
If you need query-based discovery across modes, consult Web Search. If the address points to ordinary web pages for content collection, compare URL; feed parsing and recursive page fetching have separate catalogue descriptions.
Minimal configuration
example configuration, not a recorded test
{
"rss_url": "https://example.com/feed.xml"
}Replace the illustrative rss_url with a feed you intend to read; the example.com path is not a verified feed endpoint. Keep timeout unspecified until its units are confirmed in the editor. Examine articles for the fields your next node needs before attempting a larger feed workflow.
Limitations
- The description specifies RSS without naming versions, Atom support, namespace handling or date parsing. Support for those formats and details remains unverified.
- No feed polling schedule, retained state, caching or duplicate suppression is documented by these two inputs. A fetch-and-parse description does not establish a recurring monitor.
- Article columns, maximum feed size, entry-count limits and malformed-feed behavior are absent from the export; the Table label supplies none of those contracts.
- No headers or credential field appears in the RSS Reader input list. Authenticated-feed configuration is not established here, and the timeout setting does not define retries.
For broader automation starting points and their evidence, read the documented workflow hub.
Node usage
Feed-workflow estimates belong in the cost guide, alongside published pricing.
Related components
Web Search · URL · Parser · Loop