RSS Action

Fetches a feed and turns its items into payloads. It parses RSS, Atom, RDF and JSON Feed, remembers what it already emitted so a scheduled run only produces new items, and can go fetch the full article behind each link.

Setup

None. A public feed needs no credential — the node is an HTTP fetch with a parser and a memory.


Feed

The URL to fetch, and the format: Auto, XML or JSON Feed. Auto is right almost always — the parser has two paths, XML and JSON, and it detects which one to use from the body rather than trusting the content type.

Forcing JSON Feed is rarely what you want: a valid JSON feed is always detected. The setting earns its keep in the other direction — XML served with a JSON content type, which without the override would be handed to a JSON parser and fail.

How many, and filters

How many caps the items taken from the feed per run. Filters narrow them further — by title, by content, by date — so a busy feed can still drive a quiet flow.

Dedup across runs

On by default, and the reason the node is usable on a schedule: without it, every run re-emits every item still in the feed. With it, an item is emitted once and remembered, so a Scheduled Workflow pointing at a news feed produces new items only.

Content enrichment

Many feeds carry a summary rather than the article. Enrichment fetches the linked page and pulls the full text, which is what makes the output worth handing to an AI Node or a Vector Store. It costs one HTTP request per item, so it pairs with a sensible How many.

Format and timeout

Format shapes each item before it leaves the node; Timeout bounds the fetch. A slow feed that blows the timeout fails the node rather than hanging the run.

Test RSS fetch

The panel fetches the feed on demand and shows what came back. It is the fastest way to find out that a feed needs enrichment, or that its dates are in a format the filter is not matching.


Mode — action or AI toolkit

The Mode selector decides who drives the node. In Action mode you pick one operation and fill its fields, and the node does that every time it runs. In AI toolkit mode the operations become tools an AI Node can call, and the model chooses which one and with what arguments.

Toolkit mode is opt-in per node, and it is what makes this node show up in an AI Node's tool picker. A node left in Action mode is invisible to agents.

Gotchas

  • Without dedup, a scheduled run re-emits everything still in the feed, every time. It is on by default for that reason.
  • Enrichment is one extra request per item. On a feed of fifty items that is fifty fetches per run.
  • Feeds lie about their format. That is why detection reads the body instead of the content type — leave the format on Auto unless you have measured otherwise.
  • This is the RSS action, which fetches when the flow runs. To start a flow when a feed changes, use a trigger instead.