# Monitor Website SaaS Adoption for Sales

**Use case:** 

Monitor public target-account websites for supported CRM, marketing, support, analytics, and payment SaaS adoption. Replace the sample domains and CRM IDs, then keep the same Task and watch list. The first run creates a BASELINE; later complete scans emit exact additions and confirmed two-scan removals.

## Input

```json
{
  "domains": [
    {
      "domain": "apify.com",
      "externalId": "sample-target-apify"
    },
    {
      "domain": "shopify.com",
      "externalId": "sample-target-shopify"
    }
  ],
  "mode": "monitor",
  "outputMode": "changesOnly",
  "watchTechnologies": [
    "Adyen",
    "Crisp",
    "Drift",
    "HubSpot",
    "Intercom",
    "Klarna",
    "Klaviyo",
    "Mailchimp",
    "Marketo",
    "PayPal",
    "Segment",
    "Stripe",
    "Zendesk"
  ],
  "includeDns": false,
  "includeTls": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

## Output

```json
{
  "external_id": {
    "label": "External ID",
    "format": "string"
  },
  "domain": {
    "label": "Domain",
    "format": "string"
  },
  "status": {
    "label": "Status",
    "format": "string"
  },
  "change_type": {
    "label": "Change type",
    "format": "string"
  },
  "events": {
    "label": "Monitoring events",
    "format": "array"
  },
  "technologies": {
    "label": "Technologies",
    "format": "array"
  },
  "fingerprint": {
    "label": "Semantic fingerprint",
    "format": "string"
  },
  "scraped_at": {
    "label": "Observed at",
    "format": "string"
  }
}
```

## About this Actor

This example demonstrates how to use [Website Tech Stack Scraper & Change Monitor](https://apify.com/automa-flow/website-tech-stack-monitor.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/automa-flow/website-tech-stack-monitor.md) to learn more, explore other use cases, and run it yourself.


## 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.
This Task's input is already configured above — use it as-is rather than inventing a new one.

- **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 full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/automa-flow/website-tech-stack-monitor.md

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).