n8n RSS Read nodeConfigure RSS Read in n8n.

One thing to get straight first: this node does not start a workflow. It runs on each incoming item, so something has to fire before it. A Schedule Trigger every morning, a HTTP Request chain that already produced a list of feed addresses, or the trigger of any other tool. n8n also provides a separate trigger node for RSS Read when the feed itself should be what wakes the workflow up.

The first scenario is the one most teams build: a competitor or industry feed checked on a schedule, with the new entries pushed into Slack so a channel sees them without anyone opening a reader. Second scenario, an archive. The same fetch runs, but the entries land in Google Sheets, one row per entry, which gives a searchable history a feed reader never keeps. Third, a digest: entries collected across several feeds, filtered on a keyword, then sent as one message through Gmail instead of a notification per post.

When should something else do the job? If the source publishes JSON over an API rather than a feed, this node has nothing to parse and HTTP Request is the right call. The same goes for anything that is not HTTP at all: a file drop belongs to FTP, a remote command to SSH. RSS Read is for feeds, and it is deliberately narrow.

The limits follow from that narrowness. The node exposes 2 parameters, the feed URL and an Options collection holding Custom Fields and Ignore SSL Issues. There is no filter, no date range, no built-in memory of what was already read. Deduplication is your job, usually by comparing an entry value against what a previous run stored. And because the node version documented here is version 1, an older workflow can show fewer options than the panel described on this page. A node never changes version on its own.

If the question behind all this is whether n8n is the right platform in the first place, the n8n review goes through that separately.