# Saas Changelog Monitor (`yearly_register/saas-changelog-monitor`) Actor

Monitor public SaaS changelogs for new product updates and release entries, with normalized output for alerts and competitive intelligence.

- **URL**: https://apify.com/yearly\_register/saas-changelog-monitor.md
- **Developed by:** [Automation Tech](https://apify.com/yearly_register) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 changelog checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## SaaS Changelog Monitor

SaaS Changelog Monitor extracts stable product-update entries from public SaaS changelog pages for scheduled monitoring. It is intended for teams that want structured visibility into vendor changes, feature launches, and product updates without manually checking multiple changelog pages.

### What it does

The Actor crawls configured public changelog pages, extracts supported changelog entries, normalizes the results, and writes stable records to the default Apify dataset. The output is designed for repeatable monitoring and downstream automation rather than raw HTML archiving.

Typical use cases include:

- monitoring competitor product launches;
- tracking updates from important software vendors;
- collecting changelog entries for market or product research;
- feeding new updates into alerts, summaries, or internal dashboards;
- scheduling recurring product-intelligence checks through Apify.

### Quick start

1. Add one or more supported public SaaS changelog URLs to the Actor input.
2. Keep request and result limits conservative for the first run.
3. Run the Actor and inspect the default dataset.
4. Confirm that titles, links, dates, and extracted update content match the source page.
5. Tune the available source-specific controls if the page requires them.
6. Once verified, schedule recurring runs or call the Actor through the Apify API.

The Input tab also includes shared crawler settings for request limits, retries, concurrency, timeouts, and proxy configuration.

### Output

Each dataset item represents a normalized changelog or product-update entry together with source and scrape metadata. The Actor's dataset schema defines the exact fields and types. Results can be exported from Apify as JSON, CSV, or Excel or consumed directly through the dataset API.

### Scheduling and integrations

Use an Apify schedule to check changelog pages at an interval that makes sense for the vendors you track. Connect new records to webhooks, Make, Zapier, databases, notification systems, summarization workflows, or other Actors.

### Limitations

Public changelog pages are not standardized. Page structure, pagination, timestamps, and article formatting can change without notice, and some vendors may move updates behind client-side applications or authentication. Verify each target source and review it again if extraction quality changes.

### Pricing

The active pricing model and current rates are shown in the Actor's Apify Store **Pricing** tab. Platform usage depends on the number and complexity of pages, retries, proxy use, and run frequency. Test representative sources before enabling large or high-frequency scheduled monitoring.

# Actor input Schema

## `startUrls` (type: `array`):

List of URLs to start scraping from

## `maxResults` (type: `integer`):

Maximum number of results to scrape

## `maxRequests` (type: `integer`):

Maximum number of requests to process

## `maxConcurrency` (type: `integer`):

Maximum number of concurrent requests

## `maxRequestRetries` (type: `integer`):

Maximum number of retries for failed requests

## `maxRequestsPerMinute` (type: `integer`):

Maximum requests per minute

## `requestTimeoutSecs` (type: `integer`):

Request timeout in seconds

## `proxyConfiguration` (type: `object`):

Proxy configuration for requests

## `debug` (type: `boolean`):

Enable debug logging

## `entrySelector` (type: `string`):

Changelog extraction control.

## `titleSelector` (type: `string`):

Changelog extraction control.

## `linkSelector` (type: `string`):

Changelog extraction control.

## `dateSelector` (type: `string`):

Changelog extraction control.

## `summarySelector` (type: `string`):

Changelog extraction control.

## `dateAttribute` (type: `string`):

Changelog extraction control.

## `maxEntriesPerPage` (type: `integer`):

Changelog extraction control.

## `maxSummaryLength` (type: `integer`):

Changelog extraction control.

## Actor input object example

```json
{
  "startUrls": [],
  "maxResults": 1000,
  "maxRequests": 10000,
  "maxConcurrency": 10,
  "maxRequestRetries": 3,
  "maxRequestsPerMinute": 60,
  "requestTimeoutSecs": 30,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "debug": false,
  "entrySelector": "article",
  "titleSelector": "h1, h2, h3",
  "linkSelector": "a[href]",
  "dateSelector": "time",
  "summarySelector": "",
  "dateAttribute": "datetime",
  "maxEntriesPerPage": 100,
  "maxSummaryLength": 5000
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("yearly_register/saas-changelog-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "proxyConfiguration": { "useApifyProxy": False } }

# Run the Actor and wait for it to finish
run = client.actor("yearly_register/saas-changelog-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call yearly_register/saas-changelog-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,yearly_register/saas-changelog-monitor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/hTF7BhwTXGcQQu4Ca/builds/iT1rej9U2uaqpPimd/openapi.json