# SaaS Status & Incident Monitor (`runtime/saas-status-incident-monitor`) Actor

Monitor SaaS status pages, outages, incidents, maintenance notices, affected services, reliability signals, and changes over time.

- **URL**: https://apify.com/runtime/saas-status-incident-monitor.md
- **Developed by:** [scraping automation](https://apify.com/runtime) (community)
- **Categories:** Business, Developer tools, Marketing
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $18.00 / 1,000 monitored status records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#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 Status & Incident Monitor

Monitor SaaS status pages, incidents, outages, maintenance notices, affected services, and reliability signals.

### Who this is for

- Reliability teams
- Customer success teams
- Competitive intelligence teams

### What it helps you do

- Track competitor uptime incidents
- Collect status page updates and affected services
- Build reliability datasets for reporting

### Inputs you can use

- Status page URLs
- Company names
- Maximum incidents

### Data you get

- company
- incident title
- status
- severity
- affected services
- date
- update text
- source URL

### How to get better results

- Start with a narrow, specific query or a small list of source URLs.
- Use realistic limits for the first run, then increase the volume once the output looks right.
- Keep source URLs, dates, and location context when you need repeatable market monitoring.
- Review a few sample records before connecting the dataset to a larger workflow.

### Notes

- Results depend on what the public source exposes at run time.
- Some pages may hide, delay, rename, or remove fields, so individual records can have partial data.
- Use the built-in output table to inspect results before exporting to spreadsheets, dashboards, or automation tools.

### Support

If a run returns unexpected data, open an issue from the Actor page with the input used, the run ID, and the result you expected.

# Actor input Schema

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

SaaS status pages, incident history pages, trust pages, or company homepages to monitor.

## `companies` (type: `array`):

Optional named companies with website, statusPageUrl, statusUrl, incidentUrl, or trustUrl. Names are copied to the output.

## `statusPages` (type: `array`):

Optional named status pages. Use companyName and statusPageUrl for clean outputs.

## `manualPages` (type: `array`):

Optional pages from another workflow. Provide url and html to analyze without live crawling.

## `previousSnapshots` (type: `array`):

Optional previous status rows or incident snapshots from an earlier run. Used to flag new or changed incidents.

## `discoverStatusPages` (type: `boolean`):

When a homepage is provided, follow likely status, system status, incident, uptime, trust, or availability links on the same domain.

## `maxIncidentsPerPage` (type: `integer`):

Maximum detected incidents saved from each page. A status snapshot is still saved when no incident is found.

## `includePageText` (type: `boolean`):

Save a compact page text excerpt for audits and downstream AI workflows.

## `pageTextMaxChars` (type: `integer`):

Maximum text excerpt length when Include page text is enabled.

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

Maximum total pages to analyze.

## `maxPagesPerDomain` (type: `integer`):

Maximum pages analyzed for each domain when discovery is enabled.

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

HTTP request timeout in seconds.

## `failOnNoResults` (type: `boolean`):

Fail the run when no status snapshots or incident records are saved.

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

Optional Apify Proxy configuration. Most public SaaS status pages work without proxy.

## Actor input object example

```json
{
  "startUrls": [
    "https://www.githubstatus.com/"
  ],
  "companies": [
    {
      "name": "GitHub",
      "statusPageUrl": "https://www.githubstatus.com/"
    }
  ],
  "statusPages": [],
  "manualPages": [],
  "previousSnapshots": [],
  "discoverStatusPages": true,
  "maxIncidentsPerPage": 20,
  "includePageText": false,
  "pageTextMaxChars": 1500,
  "maxPages": 25,
  "maxPagesPerDomain": 4,
  "requestTimeoutSecs": 25,
  "failOnNoResults": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `incidents` (type: `string`):

No description

## `status` (type: `string`):

No description

## `services` (type: `string`):

No description

## `changes` (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 = {
    "startUrls": [
        "https://www.githubstatus.com/"
    ],
    "companies": [
        {
            "name": "GitHub",
            "statusPageUrl": "https://www.githubstatus.com/"
        }
    ],
    "statusPages": [],
    "manualPages": [],
    "previousSnapshots": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("runtime/saas-status-incident-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 = {
    "startUrls": ["https://www.githubstatus.com/"],
    "companies": [{
            "name": "GitHub",
            "statusPageUrl": "https://www.githubstatus.com/",
        }],
    "statusPages": [],
    "manualPages": [],
    "previousSnapshots": [],
}

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

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

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

```

## CLI example

```bash
echo '{
  "startUrls": [
    "https://www.githubstatus.com/"
  ],
  "companies": [
    {
      "name": "GitHub",
      "statusPageUrl": "https://www.githubstatus.com/"
    }
  ],
  "statusPages": [],
  "manualPages": [],
  "previousSnapshots": []
}' |
apify call runtime/saas-status-incident-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=runtime/saas-status-incident-monitor",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/AtMAFjqYBbDf13rle/builds/3UtQRZggwnchklMfw/openapi.json