SaaS Integration Directory Monitor

Compare public SaaS integration directories and produce structured rows for added, removed, recategorized, unavailable, or materially changed listings.

What It Monitors

• New and removed integrations.
• Availability or listing status changes.
• Category changes.
• Listing and documentation URL changes.
• Name, vendor, and description changes.

The parser accepts JSON arrays and common wrappers such as integrations, apps, items, results, and data. It can also extract named links from public HTML directories and resolve relative links against the source URL.

Input

Use targets for multiple directories, or provide direct single-directory fields at the top level.

Field	Purpose
targets	Capped previous/current directory comparisons.
vendor	Vendor or ecosystem represented by a direct comparison.
sourceUrl / urls	Public current-directory URLs. Retrieval occurs only when fetchUrls is true and current content is absent.
previousSnapshot / currentSnapshot	Directory JSON or HTML.
previousIntegrations / currentIntegrations	Structured listing records.
records	Pre-paired records containing old and new listing values.
html	Current HTML when currentSnapshot is omitted.
includeUnchanged	Include listings whose supported fields did not change.
includeReport	Write results, summary, and Markdown report records.
maxTargets	Directory cap, from 1 through 50.
maxIntegrationsPerTarget	Listing cap per side, from 1 through 10,000.
maxItems	Dataset row cap.
maxTextBytes	Snapshot size cap, up to 2,000,000 bytes.

{
  "sourceId": "commerce-integrations",
  "vendor": "Acme Commerce",
  "previousIntegrations": [
    { "id": "slack", "name": "Slack", "categories": ["Messaging"], "status": "available" }
  ],
  "currentIntegrations": [
    { "id": "slack", "name": "Slack", "categories": ["Messaging", "AI"], "status": "available" },
    { "id": "teams", "name": "Microsoft Teams", "categories": ["Messaging"], "status": "available" }
  ],
  "maxItems": 25,
  "includeReport": true
}

Dataset Rows

Each row identifies one listing change or source diagnostic. Important fields include:

• integrationKey, integrationName, and vendor.
• changeType, oldStatus, and newStatus.
• oldCategories, newCategories, oldIntegrationUrl, and newIntegrationUrl.
• oldDocsUrl, newDocsUrl, oldDescription, and newDescription.
• sourceId, sourceUrl, sourceType, severity, score, checkedAt, and recommendation.
• diagnosticCode and sourceError for blocked retrieval or an empty directory parse.

Change types are added, removed, status-changed, category-changed, url-changed, details-changed, and unchanged.

Stored Artifacts

• Dataset: one row per listing change, unchanged listing, or diagnostic that passes configured filters and caps.
• SAAS_INTEGRATION_DIRECTORY_MONITOR_RESULTS.json: emitted rows.
• SAAS_INTEGRATION_DIRECTORY_MONITOR_SUMMARY.json: listing counts by change type, diagnostics, and charge-limit status.
• SAAS_INTEGRATION_DIRECTORY_MONITOR_REPORT.md: readable directory change digest.

Usage Charges

The actor uses pay per event. Platform usage is included in these event prices.

Event	Price	When charged
actor-start	$0.02000	Once before paid work starts.
target-checked	$0.00650	Before each directory target is processed.
snapshot-compared	$0.00650	Before a successfully prepared directory pair is compared.
change-detected	$0.01300	Before each changed listing row is emitted.
digest-generated	$0.05000	Before JSON result and summary records are written.
executive-report-generated	$0.10000	Before the Markdown report is written.

If Apify reports that a charge was limited or only partly accepted, the actor stops before the corresponding paid output. Set includeReport to false when KVS report artifacts are not needed.

Public Tasks

Five capped task inputs cover new integrations, removed integrations, category moves, listing updates, and a directory digest. The task inputs use concrete listing records and bounded row counts.

Retrieval Safety

• Only http and https URLs are accepted.
• Credentials in URLs and redirects are rejected.
• Loopback, link-local, and private network destinations are blocked unless allowPrivateUrls is explicitly enabled for controlled testing.
• Response length, retained snapshot bytes, target count, listing count, and request duration are bounded.
• Fetch failures and empty parses produce explicit diagnostic rows. The actor does not invent listings or categories.

Limitations

• JavaScript-only directories must expose JSON or server-rendered links; the actor does not run a browser.
• HTML extraction requires named links and cannot recover metadata that is absent from the markup.
• Scheduling and baseline retention are managed by the caller. Pass prior directory content into each comparison.
• Authenticated partner directories and credentialed endpoints are not supported.