# SaaS Integration Directory Extractor (`junipr/saas-integration-directory-extractor`) Actor

Extract integrations, app directory listings, categories, partner names, descriptions, install or connect CTAs, logos, and marketplace detail links from SaaS integration directories

- **URL**: https://apify.com/junipr/saas-integration-directory-extractor.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $11.50 / 1,000 directory page analyzeds

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## SaaS Integration Directory Extractor

Extract integrations, app directory listings, categories, partner names, descriptions, install/connect CTAs, logos, and marketplace detail links from SaaS integration directories.

### What it does

Extracts public integration listings, partners, categories, descriptions, CTAs, logos, detail links, positions, and duplicate partners.

Every row is source-backed and schema-complete. Missing, blocked, or unmatched evidence produces diagnostics instead of invented values.

### Uses

- Extract SaaS integration directory listings
- Inventory partner ecosystem pages
- Find duplicate integration listings
- Export app directory categories
- Compare competitor integrations

### Input

Use authorized public HTTP(S) URLs or deterministic `htmlInputs`. Private-network targets are rejected and `allowedDomains` can narrow fetching.

- `startUrls`
- `sitemapUrls`
- `htmlInputs`
- `allowedDomains`
- `maxPages`
- `maxDepth`
- `includeEvidence`
- `includeRawSnapshots`
- `requestDelayMs`
- `timeoutMs`
- `userAgentMode`
- `directoryUrls`
- `followIntegrationLinks`
- `categoryFilters`
- `maxListings`
- `extractPartnerMetadata`
- `dedupeByPartner`
- `maxDirectoryPages`
- `maxIntegrations`
- `maxCategories`
- `maxPartnerRecords`
- `maxChargeUsd`
- `includeReport`

Limits in `maxDirectoryPages, maxIntegrations, maxCategories, maxPartnerRecords, timeoutMs` and `maxChargeUsd` are enforced. Zero is a hard zero charge budget.

### Dataset

- `sourceUrl`
- `sourceType`
- `pageTitle`
- `recordType`
- `recordName`
- `issueCode`
- `severity`
- `evidenceSnippet`
- `recommendation`
- `canonicalUrl`
- `httpStatus`
- `scannedAt`
- `directoryUrl`
- `integrationName`
- `integrationUrl`
- `partnerName`
- `category`
- `description`
- `ctaText`
- `logoAltText`
- `detailPageUrl`
- `listingPosition`
- `duplicatePartnerGroup`

Reports:

- `saas-integration-directory-extractor-summary-report.md`
- `saas-integration-directory-extractor-records.csv`
- `saas-integration-directory-extractor-issues.json`
- `saas-integration-directory-extractor-evidence-samples.json`
- `saas-integration-directory-extractor-run-metadata.json`

### PPE pricing

Platform-usage pass-through is off.

| Event | Price |
| --- | ---: |
| `actor-start` | $0.035 |
| `directory-page-analyzed` | $0.0115 |
| `integration-record-extracted` | $0.0065 |
| `ecosystem-signal-emitted` | $0.0115 |
| `executive-report-generated` | $0.4 |

The actor-start event is accepted before fetching. Source, record, signal, gap, and blocker events are deduplicated and charged before their paid output. Partial charges, event limits, and local caps stop later output. Reports are written only after the report event is accepted.

### Safety and limitations

- Public evidence only; no login, CAPTCHA bypass, or access-control evasion.
- Output reflects source content at scan time.
- Attribution, claim permission, pricing interpretation, partner status, and launch decisions require human ownership.
- Store discounts, tasks, categories, icons, publication, and scheduling are separate gated live configuration.

### Local verification

```bash
pnpm --filter @junipr/saas-integration-directory-extractor build
pnpm --filter @junipr/saas-integration-directory-extractor test
pnpm --filter @junipr/saas-integration-directory-extractor smoke
```

# Actor input Schema

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

startUrls for SaaS Integration Directory Extractor.

## `sitemapUrls` (type: `array`):

sitemapUrls for SaaS Integration Directory Extractor.

## `htmlInputs` (type: `array`):

htmlInputs for SaaS Integration Directory Extractor.

## `allowedDomains` (type: `array`):

allowedDomains for SaaS Integration Directory Extractor.

## `maxPages` (type: `integer`):

maxPages for SaaS Integration Directory Extractor.

## `maxDepth` (type: `integer`):

maxDepth for SaaS Integration Directory Extractor.

## `includeEvidence` (type: `boolean`):

includeEvidence for SaaS Integration Directory Extractor.

## `includeRawSnapshots` (type: `boolean`):

includeRawSnapshots for SaaS Integration Directory Extractor.

## `requestDelayMs` (type: `integer`):

requestDelayMs for SaaS Integration Directory Extractor.

## `timeoutMs` (type: `integer`):

timeoutMs for SaaS Integration Directory Extractor.

## `userAgentMode` (type: `string`):

userAgentMode for SaaS Integration Directory Extractor.

## `directoryUrls` (type: `array`):

directoryUrls for SaaS Integration Directory Extractor.

## `followIntegrationLinks` (type: `boolean`):

followIntegrationLinks for SaaS Integration Directory Extractor.

## `categoryFilters` (type: `array`):

categoryFilters for SaaS Integration Directory Extractor.

## `maxListings` (type: `integer`):

maxListings for SaaS Integration Directory Extractor.

## `extractPartnerMetadata` (type: `boolean`):

extractPartnerMetadata for SaaS Integration Directory Extractor.

## `dedupeByPartner` (type: `boolean`):

dedupeByPartner for SaaS Integration Directory Extractor.

## `maxDirectoryPages` (type: `integer`):

maxDirectoryPages for SaaS Integration Directory Extractor.

## `maxIntegrations` (type: `integer`):

maxIntegrations for SaaS Integration Directory Extractor.

## `maxCategories` (type: `integer`):

maxCategories for SaaS Integration Directory Extractor.

## `maxPartnerRecords` (type: `integer`):

maxPartnerRecords for SaaS Integration Directory Extractor.

## `maxChargeUsd` (type: `number`):

maxChargeUsd for SaaS Integration Directory Extractor.

## `includeReport` (type: `boolean`):

includeReport for SaaS Integration Directory Extractor.

## Actor input object example

```json
{
  "startUrls": [],
  "sitemapUrls": [],
  "htmlInputs": [
    {
      "sourceUrl": "https://example.com/integrations",
      "html": "<title>Integrations</title><article class='integration-card' data-partner='HubSpot' data-category='CRM'><img alt='HubSpot logo'><h2><a href='/integrations/hubspot'>HubSpot</a></h2><p>Sync contacts and deals.</p><a href='/integrations/hubspot'>Learn more</a></article>"
    }
  ],
  "allowedDomains": [],
  "maxPages": 5,
  "maxDepth": 5,
  "includeEvidence": false,
  "includeRawSnapshots": false,
  "requestDelayMs": 5,
  "timeoutMs": 5,
  "userAgentMode": "",
  "directoryUrls": [],
  "followIntegrationLinks": true,
  "categoryFilters": [],
  "maxListings": 50,
  "extractPartnerMetadata": true,
  "dedupeByPartner": true,
  "maxDirectoryPages": 5,
  "maxIntegrations": 50,
  "maxCategories": 10,
  "maxPartnerRecords": 100,
  "maxChargeUsd": 75,
  "includeReport": true
}
```

# Actor output Schema

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

No description

## `report` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("junipr/saas-integration-directory-extractor").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("junipr/saas-integration-directory-extractor").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 '{}' |
apify call junipr/saas-integration-directory-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/saas-integration-directory-extractor"
        }
    }
}

```

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/mRCDeu6kNJ4c7QhN1/builds/dLu02AvY8ZVj2ut43/openapi.json