Latenode

Site monitor to RSS

This template runs on a schedule, opens each URL in a headless browser, and compares visible text to the last snapshot in Latenode Database.

When the change crosses your threshold, JavaScript builds RSS XML and Google Drive saves the feed file. Connect Google Drive. Keep snapshots in Latenode Database keyed by URL.

Updated Sep 16, 2026Est. run: 9sEst. cost: $0.0006
How Latenode estimates time and cost

Latenode bills workflow runtime in CPU seconds. The first 10,000 CPU seconds are free each month, then usage follows pay-as-you-go CPU-second pricing. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.

Full pricing — how CPU seconds work →

Workflow preview

What this template does

  • Turns website changes into an RSS file without copying them by hand
  • Loads JavaScript-heavy pages with a headless browser
  • Stores snapshots in Latenode Database
  • Saves the feed XML in Google Drive

How it works

1
Trigger

Run on a schedule

The scenario starts on the interval you set.

2
Action

Load each watched page

The headless browser opens the URLs you list and returns the visible text or a selector you choose.

3
Logic

Compare to the last snapshot

JavaScript reads the last snapshot from Latenode Database, diffs the text, and keeps only meaningful changes.

4
Action

Save the RSS file

JavaScript builds RSS XML for those changes. Google Drive writes the file to the folder you set. The new snapshot is stored back in Latenode Database.

Setup guide

1

Set the schedule and URL list

Add a schedule trigger. Put the pages you are allowed to check in JavaScript or in Latenode Database.

2

Load pages and store snapshots

Add a headless browser step for each URL. Store the last visible text in Latenode Database keyed by URL so the next run can diff.

3

Connect Google Drive and build RSS

Add a Google Drive connection with write access to the folder that will hold the feed file. In JavaScript, turn each meaningful change into RSS item XML or a full feed document, then create or update that Drive file. Test with one URL.

Requirements

A list of URLs you are allowed to check automatically
A schedule interval you are willing to run
Latenode Database to store the last snapshot per URL
A Google Drive folder Latenode can write to

FAQ

Common questions about this template

Each run uses credits on your Latenode plan. We charge for processing time (1 credit = 30 seconds). Your actual cost depends on your plan and how long the run takes. See pricing plans for plans and how credits work.