Merge RSS Data from Multiple Executions

Demonstrates merging data from multiple sequential RSS Feed Read executions into a single object using custom functions and looping logic.

n8n
Merge RSS Data from Multiple Executions

This n8n workflow showcases a technique to aggregate data generated across multiple executions of the same node, specifically RSS Feed Read nodes. It begins with a Manual Trigger, followed by a Function node that generates an array of RSS feed URLs (e.g., Medium and Dev.to n8n feeds). The SplitInBatches node processes these one at a time, feeding each into the RSS Feed Read node to fetch items sequentially.

An IF node checks the SplitInBatches context for 'noItemsLeft' to control the loop: if items remain, it loops back to SplitInBatches; otherwise, it proceeds to the Merge Data Function. The key innovation is in the Merge Data Function, which uses $items('RSS Feed Read', 0, counter) to retrieve json data from all prior executions of the RSS node by incrementing a counter until an error occurs (indicating no more data), then combines everything into a single 'allData' array.

Benefits include overcoming n8n's limitations on parallel processing for resource-intensive nodes like RSS reads, enabling scalable data aggregation without complex sub-workflows. Use cases: consolidating multiple RSS/API feeds for newsletters, dashboards, or analytics; merging paginated results; or batch-processing similar data sources in IT/development pipelines. Note: Post-merge, convert the single item back to multiple items for further processing.

$12.99
Last updated November 14, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Development & IT workflows

More from Juliet Weber

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.