SaaS Changelog Monitor

What does SaaS Changelog Monitor do?

SaaS Changelog Monitor watches any list of public changelog pages and returns new or changed release entries as clean, structured JSON. Point it at pages like github.blog/changelog or tailscale.com/changelog, and it extracts every release entry — title, version, date, categories and a summary. Change detection persists between runs: schedule it daily and you only get what's new since the last check.

Because it runs on the Apify platform, you get API access, scheduling, webhooks, integrations (Slack, Make, n8n, Zapier) and monitoring out of the box.

Why use SaaS Changelog Monitor?

• Competitive intelligence — know the moment a competitor ships something new, without visiting dozens of changelog pages by hand.
• Product & engineering teams — track upstream dependencies and vendors for breaking changes and security fixes.
• VCs & analysts — monitor shipping velocity across a portfolio or market.
• AI agents & RAG pipelines — structured changelog entries are ideal input for agents that answer "what changed at X?". Categories are normalized (Added, Fixed, Improved, Security, …) so you can filter programmatically.
• Predictable flat pricing — you pay per source checked, never per entry. Competitors charge per page or per entry, which gets expensive fast.

How to use SaaS Changelog Monitor

1. Open the Actor and go to the Input tab.
2. Paste the changelog URLs you want to monitor (up to 25 per run).
3. Click Start. The first run returns all current entries (your baseline).
4. Optionally, create a Schedule (e.g. daily). Subsequent runs return only new or changed entries.
5. Connect a webhook or integration to push new entries to Slack, email or your own API.

Input

Field	Type	Default	Description
changelogUrls	array	– (required)	Public changelog/release-notes URLs to check. Hard cap: 25 per run.
maxEntriesPerSource	integer	50	Maximum entries parsed per source (cap: 200).
onlyNewEntries	boolean	true	Return only entries that are new or changed since the previous run. Set to false to always return everything.

{
    "changelogUrls": [
        "https://github.blog/changelog/",
        "https://tailscale.com/changelog"
    ],
    "onlyNewEntries": true
}

Output

One dataset item per (new) changelog entry. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

{
    "sourceUrl": "https://tailscale.com/changelog",
    "title": "Tailscale v1.98.4",
    "version": "v1.98.4",
    "date": "2026-05-28T00:00:00.000Z",
    "categories": ["Fixed"],
    "summary": "An issue causing a deadlock when processing peer changes...",
    "entryHash": "3f9a…",
    "isNew": true,
    "detectedAt": "2026-07-04T20:55:41.141Z"
}

A per-run report is stored in the key-value store under SUMMARY (per source: status, entries found, new entries).

Field	Description
sourceUrl	The changelog page this entry came from
title	Entry title
version	Detected version (e.g. v1.98.4), or null
date	Entry date in ISO 8601, or null if not detected
categories	Normalized labels: Added, Fixed, Improved, Changed, Security, Deprecated, Removed, New
summary	Plain-text summary (max 500 characters)
entryHash	Stable hash used for change detection
isNew	Whether this entry is new/changed vs. the previous run

How much does it cost to monitor changelogs?

Pricing is a flat fee per source checked — all entries included, no per-entry fees. A source is only charged when it is successfully checked and at least one entry is recognized; failed or unreadable pages are never charged. A run where nothing changed is still a successful check (that's the monitoring service), so it is charged.

Example: monitoring 10 changelogs daily costs 10 × the per-source fee per day — regardless of how many entries those pages contain. Comparable actors charge per page or per entry, which typically costs 5-10× more for the same monitoring job.

Tips

• Schedule daily or weekly and set onlyNewEntries: true (default) — you'll only pay for the check and only receive what's new.
• The parser handles most common changelog layouts (heading-based and container-based). JavaScript-rendered changelogs that ship no HTML content are not supported; those sources are reported in SUMMARY and never charged.
• Use maxEntriesPerSource to bound very long changelog pages.

FAQ & disclaimers

Is it legal to scrape changelogs? This Actor only reads public product-update pages — marketing content intended for broad distribution. It collects no personal data. Please still make sure your use complies with the target sites' terms.

A source returns 0 entries — why? The page is likely rendered client-side with JavaScript or uses a very unusual layout. You are not charged for such sources. Open an issue via the Issues tab and we'll look into adding support.

Found a bug or missing a feature? Please report it via the Issues tab — feedback is usually answered within a few days.