SaaS Changelog Monitor

Monitor public SaaS changelogs, Stripe changelogs, release notes, status-page incident feeds and component snapshots, API docs, pricing pages, cookie/privacy policy pages, subprocessor pages, favicon/brand asset pages, GraphQL schema files, and OpenAPI specs for competitor updates, payment/API changes, release digest signals, SLA incidents, status component drift, compliance/vendor drift, brand asset drift, docs/API drift, schema drift, OpenAPI endpoint diffs, and breaking-change alerts.

This Actor is designed for scheduled product and competitor monitoring. It is intentionally narrower than generic page scraping: the first value is a compact digest of new update items that matter to product, sales, developer-relations, and agency workflows.

Input

• sources: public changelog, Stripe changelog, release-note, RSS/Atom, status-page incident feed, statuspage component JSON, API docs, pricing-page, cookie/privacy-policy, subprocessor page, favicon/brand asset page, GraphQL schema, or OpenAPI spec URLs. Use type: "status" for status/incident feeds or component snapshots, type: "policy" for cookie/privacy policy pages, type: "subprocessor" for vendor/subprocessor pages, type: "favicon" for favicon/web-manifest/theme-color brand asset pages, type: "docs" for API docs/deprecation pages, type: "pricing" for pricing/package/billing pages, type: "graphql" for public SDL/schema text, type: "openapi" for OpenAPI JSON/YAML, type: "release" for release-note digest snapshots, and type: "stripe" for Stripe payment/API changelog snapshots.
• previousItemIds: optional IDs from a previous run.
• previousOpenApiSurfaces: optional previous OpenAPI surface snapshots for local diff testing. Scheduled runs normally load these from snapshotKey.
• snapshotKey: key-value-store record used for scheduled change detection and OpenAPI surface diffs.
• alertKeywords: terms such as breaking, deprecated, migration, security, pricing, or api.
• maxItems: maximum rows to output.

Output

Dataset rows include:

• source label and URL
• update title and URL
• NEW or SEEN status
• category such as OUTAGE, DEGRADED, MAINTENANCE, SECURITY, COMPLIANCE, PRICING, BREAKING_CHANGE, API, or FEATURE
• generic breaking-change evidence: matched terms, affected surfaces, effective date hints, action hints, risk signals, and risk score
• statusSeverity, statusComponents, slaImpactScore, incident stage, time hints, duration hint, customer-impact hint, impact terms, digest risk signals, and digest score for status-page sources, separating OUTAGE, DEGRADED, MAINTENANCE, RESOLVED, and INFO while identifying affected components such as API, webhooks, auth, billing, database, email, queue, search, CDN, and website
• statuspage component snapshot fields: component names, status by component, component state counts, degraded/operational/maintenance component lists, component risk signals, action hints, and component health score
• alert flag, priority, matched keywords, and reasons
• policy fingerprint, matched policy terms, cookie categories, consent/reject/preference controls, jurisdiction signals, retention hints, data subject rights, legal bases, transfer mechanisms, sensitive/children data categories, sale/share/opt-out signals, privacy contacts, policy date hints, risk signals, and third-party sharing signals for type: "policy" sources
• pricing fingerprint, matched pricing terms, amount hints, plan hints, and pricing change hint for type: "pricing" sources
• subprocessor fingerprint, vendor count, vendor names, vendor domains, service categories, region hints, data categories, critical vendors, risk signals, and risk score for type: "subprocessor" sources
• favicon fingerprint, icon URLs, rels, sizes, manifest URL, theme colors, apple-touch/mask icon counts, SVG/PNG hints, and completeness risk signals for type: "favicon" sources
• docs fingerprint, matched docs terms, endpoint hints, section headings, HTTP methods, code-block count, parameter/auth/rate-limit/pagination/error/response-format hints, deprecated versions, removal dates, replacement endpoints, sunset/removal/migration/auth-impact hints, docs drift risk signals, and deprecation/drift risk scores for type: "docs" sources
• schema fingerprint, type names, type-kind counts, operation types, root field names, connection/page type hints, directive names, auth directive hints, deprecated count, and breaking/deprecation hints for type: "graphql" sources
• OpenAPI fingerprint, previous fingerprint, version, path count/path list, methods, operation list, deprecated count, deprecated operations/operation IDs, required request-body operations, operation IDs, tags, server URLs, security scheme names, request/response schema counts, response status codes, security-scheme hint, breaking-risk signals, previous-snapshot diff signals for removed paths/operations/operation IDs/security schemes, diff risk score, and action hints for type: "openapi" sources
• release fingerprint, version hints, feature/fix counts, security hint, breaking/deprecation hint, CVEs, impact areas, migration/deprecation counts, config-change hint, risk signals, action hints, and risk score for type: "release" sources
• Stripe fingerprint, API version hints, product areas, payment method hints, breaking/deprecation hint, and webhook hint for type: "stripe" sources

Key-value-store records:

• SUMMARY: machine-readable counts by source and category
• REPORT: Markdown digest for quick inspection
• ALERTS: only actionable rows where alert=true; use this for automation and future paid-event counting
• SAAS_CHANGELOG_SNAPSHOT: saved item IDs plus OpenAPI surface snapshots for scheduled NEW versus SEEN detection and breaking-change diffs

Status-page summaries include outage/degraded/maintenance/resolved counts, high-impact incident counts, unresolved/long-running/customer-impact/multi-component incident counts, affected component counts, component snapshot/degraded/buyer-visible/low-health counts, and per-row impact/digest/component scores so scheduled runs can act as a lightweight SLA and component-health digest, not only a raw status feed scraper.

The Markdown report includes focused watchlists for paid-digest style workflows:

• Status Incident Watchlist
• Breaking Change Watchlist
• Compliance Watchlist
• API Change Watchlist
• Pricing Watchlist
• Release Notes Watchlist
• Stripe Changelog Watchlist

Monetization plan

First release should be free or usage-cost-only. If organic usage appears, clean paid units are:

• breaking-change-alert: a new update classified as breaking, migration, deprecation, security, API, or pricing relevant, with generic breaking evidence such as affected surface, effective date, action hint, and risk score.
• sla-status-alert: a new status incident or component snapshot classified as outage, degraded performance, partial outage, buyer-visible component degradation, or maintenance, using statusSeverity, statusComponents, slaImpactScore, incident stage, customer-impact hints, time/duration hints, component status, component health score, digest risk signals, and the status summary counts.
• competitor-release-digest: a scheduled digest containing at least one meaningful update.
• pricing-page-change-alert: a detected pricing/package/plan change.
• policy-change-alert: a new cookie/privacy/compliance policy fingerprint, cookie category/control/jurisdiction signal, retention hint, data subject right, legal basis, transfer mechanism, sensitive/children data category, sale/share opt-out signal, privacy contact, policy date, third-party sharing signal, or policy sentence match.
• subprocessor-change-alert: a new vendor/subprocessor fingerprint, vendor/domain drift, AI/payment/personal-data processor signal, region hint, service-category shift, or critical-vendor signal.
• brand-asset-change-alert: a new favicon/web-manifest/theme-color fingerprint, missing mobile icon, missing manifest, missing theme color, or brand asset URL drift.
• api-docs-drift-alert: a new API docs fingerprint, endpoint hint, section/HTTP-method/code-sample/parameter/auth/rate-limit/pagination/error/response-format surface, deprecated version, dated removal/sunset, replacement endpoint, auth-impact signal, or deprecation/removal/migration term.
• graphql-schema-change-alert: a new public GraphQL schema fingerprint, type/root-field/directive/auth surface change, connection/page type signal, or breaking/deprecation schema hint.
• openapi-spec-change-alert: a new public OpenAPI fingerprint, deprecated operation, required request body, security-scheme, operationId, tag, server URL, request/response schema, response status, breaking-risk score/action hint, or path/method drift.
• openapi-breaking-change-diff: a scheduled OpenAPI diff with removed paths, removed methods, removed operation IDs, removed security schemes, or a changed spec fingerprint. This is the cleanest PPE candidate because it is a concrete audit result rather than a raw scrape.
• release-notes-digest: a new release-note fingerprint with version, feature, fix, security, CVE, migration, deprecation, config-change, impact-area, or action-hint signals.
• stripe-changelog-alert: a new Stripe API/payment changelog fingerprint with API version, product area, payment method, webhook, breaking, or migration signal.

Use the ALERTS record as the future event-count source. Do not charge for unchanged pages, empty reports, low-signal cosmetic edits, or diagnostic errors.

Local validation

npm test
npm run sample
npx apify-cli validate-schema
npm pack --dry-run --json