Monitor RSS, Atom, and JSON feed changes with Apify Feed Contract Monitor
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 4 nodes and runs on a schedule (every hour). Along the way it connects Feed Contract Monitor (community).
How it runs
Trigger: On a schedule (every hour).
- Set feed variables (Edit Fields (Set)): sets 4 fields: feedUrl, stateNamespace, firstRunMode…
- Monitor feed changes (Apify Feed Contract Monitor): uses Apify Feed Contract Monitor
- Keep new or changed items (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 n8n-nodes-feed-contract-monitor is verified or supports 3.0 (used in Monitor feed changes).
Nodes used (4)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - Apify Feed Contract Monitor
n8n-nodes-feed-contract-monitor.apifyFeedContractMonitor - Code
n8n-nodes-base.code
From the author
Quick overview This workflow runs hourly to monitor an RSS/Atom/JSON feed using Apify Feed Contract Monitor, keeps a persistent baseline state, and outputs only new or changed feed items for downstream processing. How it works 1. Runs every hour on a schedule…