Monitor RSS feeds with Apify and store new items in data tables
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 9 nodes and runs on a schedule (every hour). Along the way it connects Apify (community).
How it runs
Trigger: On a schedule (every hour).
- Run RSS Monitoring Task (Apify): run task (actor tasks)
- If: checks a condition and branches into true / false
- Fetch Dataset Records (Apify): get items (datasets)
- Report No Dataset Found (Code): runs custom JavaScript code
- Process Dataset Records (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Upsert RSS Items (Data table): create or update (row)
- Report Ingestion Outcome (Code): runs custom JavaScript code
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @apify/n8n-nodes-apify is verified or supports 3.0 (used in Run RSS Monitoring Task, Fetch Dataset Records).
Nodes used (5)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Apify
@apify/n8n-nodes-apify.apify - If
n8n-nodes-base.if - Code
n8n-nodes-base.code - Data table
n8n-nodes-base.dataTable
From the author
Quick overview This workflow runs hourly to execute an Apify RSS monitoring Task, retrieves the run’s dataset items, normalizes them into a stable delivery key, and upserts new or updated feed entries into an n8n Data Table for idempotent storage and run…