# Workday, Greenhouse, Lever & Ashby Jobs Scraper + Change Alerts (`signalyard/hiring-signal-monitor`) Actor

Scrape jobs from Workday, Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Recruitee career sites using just a company domain. Re-run to get only new and filled roles, tagged with hiring signals for sales teams and recruiting agencies. Pay only for companies found.

- **URL**: https://apify.com/signalyard/hiring-signal-monitor.md
- **Developed by:** [Signalyard](https://apify.com/signalyard) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.80 / 1,000 job returneds

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Workday, Greenhouse, Lever & Ashby Jobs Scraper + Change Alerts

**Scrape every open job from a company's career site using just its domain**, across Workday, Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Recruitee. Re-run it (or schedule it) to get only the roles that were **posted** or **filled** since the last check, each tagged with the hiring signal it suggests. Built for **sales teams** and **recruiting agencies**. You only pay for companies we find.

Supported hiring platforms: **Workday, Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee**.

### Why sales and recruiting teams use it

- **Hiring = buying intent.** A company posting its first *Head of Security* is about to buy security
  tools. Five new *Account Executive* roles means the sales team is growing and needs tooling.
- **Changes, not dumps.** Schedule it daily or weekly in `changes` mode and you get a short feed of
  what's new instead of re-downloading thousands of unchanged jobs.
- **Just domains.** You don't need to know which hiring platform a company uses or what its board is
  called. Paste `stripe.com` and the tool finds the board.
- **Clean, official sources.** It reads each platform's public job-board API (the same feeds companies
  use to show jobs on their own careers pages). No logins, no browser automation, no personal data.

### Input

```json
{
  "companies": ["stripe.com", "linear.app", "https://jobs.lever.co/palantir"],
  "outputMode": "changes",
  "titleKeywords": ["security", "data engineer"],
  "locationKeywords": ["New York", "Remote"]
}
```

| Field | What it does |
|---|---|
| `companies` | Domains or job-board URLs. |
| `outputMode` | `all` = every open job; `new` = posted since last run; `changes` = new + removed. |
| `titleKeywords` / `excludeKeywords` | Whole-word filters on title, department and team. |
| `locationKeywords`, `remoteOnly` | Location filters. |
| `signals` | Your own tag → keywords map (defaults: leadership-hire, security, data-ai, sales-expansion, revops-crm). |
| `stateStoreName` | Separate "memory" per watchlist. |

### Output (one row per job)

```json
{
  "status": "new",
  "company": "openai.com",
  "ats": "ashby",
  "title": "Senior Technical Program Manager - Security",
  "department": "Security",
  "location": "US - Remote; New York City; Seattle; Washington, DC; San Francisco",
  "remote": true,
  "compensation": "$165.4K – $285K • Offers Equity • Multiple Ranges",
  "postedAt": "2026-06-25T17:30:54.205+00:00",
  "url": "https://jobs.ashbyhq.com/openai/c414f15f-...",
  "signals": ["security"],
  "firstSeenAt": "2026-11-02T19:40:56.884Z",
  "matchedBy": "slug-guess"
}
```

`status` is `baseline` (first run), `new`, `seen` or `removed`. A run summary (companies resolved,
not found, ambiguous matches, new and removed counts) is saved as `OUTPUT` in the default key-value store.

`matchedBy` tells you how the board was found:

- `input-url`: you gave the board URL.
- `careers-page`: a link was found on the company's website.
- `slug-guess`: a board named like the domain. These are checked against the board's public name
  and how recent its postings are, but treat them as likely rather than certain. Pass the board URL to pin it.

### Pricing (pay per event)

| Event | Price |
|---|---|
| Company checked (only when a job board is found) | $0.004 |
| Job returned | $0.0008 |

**You only pay for companies we find.** Companies on unsupported platforms are listed as
"not found" in the run summary and cost nothing.

Watching 500 companies weekly in `changes` mode costs roughly **$10/month**. Downloading every job
from a database priced per job usually costs far more for the same accounts.

### Limitations (v0.1)

- **Workday:** found automatically when the company's careers page links to it, or when its board uses a common name. Some large employers use unusual board names that can't be guessed. Paste the Workday URL (e.g. `https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite`) to pin it.
- **Workday dates:** Workday only shows vague dates ("Posted 30+ Days Ago"), so `postedAt` is filled for recent jobs only. The original text is in `postedText`, and `firstSeenAt` tracks exactly when the tool first saw each job.
- **Workday size:** Workday returns at most 2,000 jobs per board.
- Not yet supported: iCIMS, SuccessFactors, BambooHR, Personio, Teamtailor.
- Careers pages that only render with JavaScript fall back to the name-based guess.
- Greenhouse and Lever boards rarely publish salary ranges; Ashby boards often do.

***

#### Developer notes

- `src/ats.js`: board detection + one reader per platform (normalized output).
- `src/signals.js`: filters and signal tags.
- `src/main.js`: Apify glue: input, change detection (named key-value store), dataset, pay-per-event charges.
- Run locally: put input in `storage/key_value_stores/default/INPUT.json`, then `npm start`.
- Deploy: `npm i -g apify-cli`, `apify login`, `apify push`. Then set pay-per-event prices in
  Console → Actor → Publication → Monetization, using the event names `company-checked` and `job-result`.

# Actor input Schema

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

Company domains (stripe.com) or job-board URLs (https://jobs.lever.co/palantir). The board is found automatically.

## `outputMode` (type: `string`):

Schedule the Actor (e.g. daily) with 'new' or 'changes' to get a feed of hiring changes at your target accounts.

## `titleKeywords` (type: `array`):

Matched as whole words against title, department and team. Leave empty for all roles.

## `excludeKeywords` (type: `array`):

Skip jobs whose title contains any of these words (whole-word match).

## `locationKeywords` (type: `array`):

e.g. 'New York', 'London', 'Remote'. Leave empty for anywhere.

## `remoteOnly` (type: `boolean`):

Only return jobs marked as remote by the hiring platform.

## `signals` (type: `object`):

Tag name -> keywords. Every returned job gets the tags it matches. Leave empty to use the defaults shown.

## `includeBaselineOnFirstRun` (type: `boolean`):

In 'new'/'changes' mode the first run has nothing to compare against. Turn off to only start reporting from the second run.

## `includeDescription` (type: `boolean`):

Add the full job description text to each result (makes results much larger).

## `stateStoreName` (type: `string`):

Named key-value store that remembers which jobs were already seen. Use different names for separate watchlists.

## `maxConcurrency` (type: `integer`):

How many companies to check at the same time. Keep it low to stay polite to the hiring platforms.

## Actor input object example

```json
{
  "companies": [
    "stripe.com",
    "linear.app",
    "palantir.com"
  ],
  "outputMode": "all",
  "excludeKeywords": [
    "intern"
  ],
  "remoteOnly": false,
  "signals": {
    "leadership-hire": [
      "vp",
      "vice president",
      "head of",
      "director",
      "chief"
    ],
    "security": [
      "security",
      "ciso",
      "soc 2",
      "compliance",
      "grc"
    ],
    "data-ai": [
      "data engineer",
      "machine learning",
      "ml engineer",
      "ai engineer",
      "data scientist",
      "analytics engineer"
    ],
    "sales-expansion": [
      "account executive",
      "sales development",
      "sdr",
      "bdr",
      "sales manager"
    ],
    "revops-crm": [
      "revops",
      "revenue operations",
      "salesforce",
      "hubspot",
      "crm"
    ]
  },
  "includeBaselineOnFirstRun": true,
  "includeDescription": false,
  "stateStoreName": "hiring-monitor-state",
  "maxConcurrency": 5
}
```

# Actor output Schema

## `jobs` (type: `string`):

One row per job: status (baseline/new/seen/removed), company, title, department, location, remote, signals, compensation, posted date and link.

## `summary` (type: `string`):

Companies resolved, companies not found (not charged), ambiguous matches, and counts of new and removed jobs.

# 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 = {
    "companies": [
        "stripe.com",
        "linear.app",
        "palantir.com"
    ],
    "excludeKeywords": [
        "intern"
    ],
    "signals": {
        "leadership-hire": [
            "vp",
            "vice president",
            "head of",
            "director",
            "chief"
        ],
        "security": [
            "security",
            "ciso",
            "soc 2",
            "compliance",
            "grc"
        ],
        "data-ai": [
            "data engineer",
            "machine learning",
            "ml engineer",
            "ai engineer",
            "data scientist",
            "analytics engineer"
        ],
        "sales-expansion": [
            "account executive",
            "sales development",
            "sdr",
            "bdr",
            "sales manager"
        ],
        "revops-crm": [
            "revops",
            "revenue operations",
            "salesforce",
            "hubspot",
            "crm"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("signalyard/hiring-signal-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 = {
    "companies": [
        "stripe.com",
        "linear.app",
        "palantir.com",
    ],
    "excludeKeywords": ["intern"],
    "signals": {
        "leadership-hire": [
            "vp",
            "vice president",
            "head of",
            "director",
            "chief",
        ],
        "security": [
            "security",
            "ciso",
            "soc 2",
            "compliance",
            "grc",
        ],
        "data-ai": [
            "data engineer",
            "machine learning",
            "ml engineer",
            "ai engineer",
            "data scientist",
            "analytics engineer",
        ],
        "sales-expansion": [
            "account executive",
            "sales development",
            "sdr",
            "bdr",
            "sales manager",
        ],
        "revops-crm": [
            "revops",
            "revenue operations",
            "salesforce",
            "hubspot",
            "crm",
        ],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("signalyard/hiring-signal-monitor").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 '{
  "companies": [
    "stripe.com",
    "linear.app",
    "palantir.com"
  ],
  "excludeKeywords": [
    "intern"
  ],
  "signals": {
    "leadership-hire": [
      "vp",
      "vice president",
      "head of",
      "director",
      "chief"
    ],
    "security": [
      "security",
      "ciso",
      "soc 2",
      "compliance",
      "grc"
    ],
    "data-ai": [
      "data engineer",
      "machine learning",
      "ml engineer",
      "ai engineer",
      "data scientist",
      "analytics engineer"
    ],
    "sales-expansion": [
      "account executive",
      "sales development",
      "sdr",
      "bdr",
      "sales manager"
    ],
    "revops-crm": [
      "revops",
      "revenue operations",
      "salesforce",
      "hubspot",
      "crm"
    ]
  }
}' |
apify call signalyard/hiring-signal-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,signalyard/hiring-signal-monitor"
        }
    }
}
```

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/OGBZBUOtJaHoHSNiv/builds/dHKTh97WSllYKG5Fa/openapi.json