{"product_id":"n8n-rss-feed-change-monitor-with-apify-feed-contract-monitor","title":"n8n RSS Feed Change Monitor with Apify Feed Contract Monitor","description":"\u003ch3\u003eMonitor RSS\/Atom\/JSON feed changes every hour—without reprocessing everything\u003c\/h3\u003e\n\u003cp\u003eThis n8n workflow uses the \u003cstrong\u003eApify Feed Contract Monitor\u003c\/strong\u003e to continuously check your RSS\/Atom\/JSON feed, store a persistent baseline state, and output \u003cstrong\u003eonly new or changed feed items\u003c\/strong\u003e for downstream automation.\u003c\/p\u003e\n\n\u003ch3\u003eWhat this workflow does\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eRuns hourly\u003c\/strong\u003e using an \u003cstrong\u003en8n schedule trigger\u003c\/strong\u003e to keep feed monitoring up to date.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eConfigures feed settings\u003c\/strong\u003e (feed URL, \u003cem\u003estate namespace\u003c\/em\u003e, \u003cem\u003efirst-run mode\u003c\/em\u003e, and a per-run \u003cem\u003eitem limit\u003c\/em\u003e) via a set step.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eFetches and compares feed content\u003c\/strong\u003e by calling the \u003cstrong\u003eApify Feed Contract Monitor\u003c\/strong\u003e actor through the community node \u003ccode\u003en8n-nodes-feed-contract-monitor\u003c\/code\u003e.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eMaintains a persistent baseline\u003c\/strong\u003e so the workflow can detect changes over time.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eFilters results\u003c\/strong\u003e to keep only records that represent \u003cstrong\u003enew or changed feed items\u003c\/strong\u003e, discarding unchanged entries.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eUse cases\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSaaS operators\u003c\/strong\u003e tracking product updates or changelogs from an RSS feed and triggering alerts only when something actually changes.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eAutomation engineers\u003c\/strong\u003e building reliable pipelines that react to new announcements, without wasting processing time on repeated items.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003en8n users\u003c\/strong\u003e integrating feed monitoring into broader workflows such as indexing, moderation, or notifications based on detected changes.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eTechnical details\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003eNode types used: \u003cstrong\u003eset\u003c\/strong\u003e, \u003cstrong\u003ecode\u003c\/strong\u003e, \u003cstrong\u003esticky note\u003c\/strong\u003e, \u003cstrong\u003eschedule trigger\u003c\/strong\u003e, and \u003cstrong\u003en8n-nodes-feed-contract-monitor\u003c\/strong\u003e (Apify Feed Contract Monitor).\u003c\/li\u003e\n  \u003cli\u003eApify integration: configure an \u003cstrong\u003eApify API credential\u003c\/strong\u003e for the Feed Contract Monitor node.\u003c\/li\u003e\n  \u003cli\u003eFirst run setup: set \u003cstrong\u003efirst-run mode\u003c\/strong\u003e to \u003ccode\u003ebaseline_only\u003c\/code\u003e to establish the initial baseline before enabling the hourly schedule.\u003c\/li\u003e\n  \u003cli\u003eOutputs both feed-health records and changed-item records, then \u003cstrong\u003efilters\u003c\/strong\u003e to retain only new\/changed items.\u003c\/li\u003e\n\u003c\/ul\u003e","brand":"N8N Commerce","offers":[{"title":"Default Title","offer_id":45785749684403,"sku":"N8N-17895","price":31.99,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0749\/6279\/6723\/files\/0ehDGRL4oOu1nVp61c_eG_EM4VwXQM.png?v=1786180536","url":"https:\/\/buyflowscripts.com\/products\/n8n-rss-feed-change-monitor-with-apify-feed-contract-monitor","provider":"N8N Commerce","version":"1.0","type":"link"}