Multi RSS Read icon

Multi RSS Read

Reads data from multiple RSS Feeds in parallel
Join our community

Overview

The Multi RSS Read node reads and parses multiple RSS feeds in parallel, allowing users to aggregate data from various sources efficiently. It is useful for scenarios such as monitoring news sites, blogs, or any content published via RSS feeds. The node fetches each feed URL, parses the RSS content, and outputs the items found.

Practical examples include:

  • Aggregating articles from multiple news websites.
  • Monitoring updates from several blogs or podcasts.
  • Collecting event announcements from different calendars published as RSS.

This node supports error handling options to continue processing other feeds even if some fail, and it allows customization of HTTP headers and user-agent strings to improve compatibility with different servers.

Properties

Name Meaning
URLs A collection of one or more RSS feed URLs to read. Each URL must be a valid RSS feed address (e.g., https://example.com/rss).
Continue On Error Whether to continue processing other feeds if one feed fails. If enabled, errors from individual feeds are captured but do not stop the entire execution.
Custom Fields A comma-separated list of additional RSS item fields to include in the output beyond the default ones. For example, "author, contentSnippet" will add those fields if present in the feed items.
Custom Headers Allows adding multiple custom HTTP headers to each request when fetching RSS feeds. Useful for authentication or bypassing restrictions.
Ignore SSL Issues (Insecure) Whether to ignore SSL/TLS certificate validation issues. Enabling this can help access feeds with invalid or self-signed certificates but reduces security.
Include Source URL Whether to include the source RSS feed URL in each output item, helping identify which feed an item came from.
User Agents A collection of User-Agent strings; one is randomly selected per request. This helps mimic different browsers or clients to avoid blocking by some servers.

Output

The node outputs two streams:

  1. Success Output: An array of items where each item corresponds to an RSS feed entry. Each item contains a json object representing the parsed RSS item fields. If "Include Source URL" is enabled, each item also includes a sourceUrl field indicating the original feed URL.

  2. Error Output: Items representing failed feed fetches. Each error item contains a json object with:

    • error: A descriptive error message.
    • sourceUrl: The URL of the feed that failed.
    • message: A summary message about the failure.

No binary data is output by this node.

Dependencies

  • Requires internet access to fetch RSS feeds.
  • Uses an HTTP client library to perform GET requests with configurable headers and SSL options.
  • Parses RSS XML using an RSS parsing library.
  • No special credentials are required unless accessing protected feeds, in which case custom headers can be used for authentication.

Troubleshooting

Common Issues

  • Invalid URLs: The node validates URLs before fetching. Invalid URLs cause immediate errors.
  • Network Errors: Connection timeouts, refused connections, or DNS failures may occur if the feed URL is unreachable.
  • HTTP Errors: Status codes like 403 (forbidden), 404 (not found), or 429 (too many requests) are handled gracefully if "Continue On Error" is enabled.
  • SSL Certificate Issues: Feeds with invalid SSL certificates may fail unless "Ignore SSL Issues" is enabled.

Error Messages and Resolutions

  • "At least one URL must be provided!": Ensure you have added at least one valid RSS feed URL.
  • "The following URLs are not valid: ...": Check and correct the malformed URLs.
  • "Access forbidden (403)": The server may block automated requests. Try adding custom headers or user agents.
  • "Too many requests (429)": Rate limiting by the server. Wait and retry later.
  • "RSS feed not found (404)": Verify the feed URL is correct and still active.
  • "Domain not found": Check your internet connection and the domain spelling.
  • "Connection refused" or "Connection timeout": The server might be down or blocking requests.
  • "Network error": General connectivity issue; verify network status.

If "Continue On Error" is disabled, any feed failure will stop the node execution with an error.

Links and References

This summary is based on static analysis of the node's source code and input property definitions.

Discussion