# Workday Jobs Scraper & New Job Monitor (`nswk_api/workday-jobs-monitor`) Actor

Scrape every open job from any company's Workday career site and monitor new, updated and closed jobs. Filters, clean JSON, no login, no browser.

- **URL**: https://apify.com/nswk_api/workday-jobs-monitor.md
- **Developed by:** [Bryan Masias](https://apify.com/nswk_api) (community)
- **Categories:** Jobs, Lead generation, AI
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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 Jobs Scraper & New Job Monitor

Get every open job from any company's Workday career site (`*.myworkdayjobs.com`), as
clean JSON. Run it once for a full snapshot, or schedule it daily in **changes** mode to
get only the jobs that were **added, updated or closed** since the last run.

No login, no cookies, no browser. It reads the same public job listing that the career
site shows to every visitor, at a polite rate.

### What you can do with it

- **Job boards and aggregators:** many large employers hire only through Workday.
- **Sales teams:** spot hiring signals at enterprise accounts.
- **Recruiters and analysts:** track hiring by company and location over time.
- **AI agents:** one-line input, flat output, and you pay only for the jobs you get.

### Quick start

```json
{ "companies": ["https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"] }
```

Each entry is the career site URL. Any job URL from the site works too, with or without
a language part such as `/en-US/`. `*.myworkdaysite.com/recruiting/...` sites are supported.

Workday's own search stops at 2,000 jobs. For bigger sites the Actor lists them one job
category at a time, so you still get every job (tested on a site with 2,700+ jobs).

### Monitor new jobs

```json
{
  "companies": ["https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"],
  "mode": "changes",
  "keywords": ["engineer"],
  "includeDescription": "none"
}
```

Schedule it daily. Each job comes with `changeType`: `new`, `updated` or `closed`.
Jobs are only reported as closed when the whole list of the site loaded: if a site fails
to load, or a page of it fails, nothing of that site is reported as closed in that run.
If you hit your spending limit, the jobs you did not receive are reported again on the next run.

Use a different `monitorId` for each watch list or set of filters.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `companies` | string\[] | required | Career site URLs |
| `mode` | `all` / `changes` | `all` | Full snapshot, or only changes since the last run |
| `keywords` / `excludeKeywords` | string\[] | `[]` | Match on title, case- and accent-insensitive |
| `locations` | string\[] | `[]` | Match on the listed location, e.g. `remote`, `United States`, `London` |
| `remoteOnly` | boolean | `false` | Only jobs marked as remote |
| `postedWithinDays` | number | none | Only jobs posted in the last N days (up to 30) |
| `includeDescription` | `text` / `html` / `none` | `text` | `text` or `html` loads each returned job's page; `none` is cheaper and faster |
| `maxJobsPerCompany` | number | `1000` | Safety cap per career site |
| `monitorId` | string | `default` | Name of the saved state for `changes` mode |
| `emitOnFirstRun` | boolean | `true` | If off, the first `changes` run only saves a baseline |

### Output

One item per job, in the same format as our Greenhouse, Ashby and Lever Actors. Every field is
always present (`null` when unknown), and dates are UTC ISO 8601.

```json
{
  "jobId": "workday:nvidia:NVIDIAExternalCareerSite:JR2000001",
  "source": "workday",
  "companyToken": "nvidia.wd5.myworkdayjobs.com/nvidia/NVIDIAExternalCareerSite",
  "companyName": "NVIDIA",
  "title": "Senior Backend Engineer",
  "departments": [],
  "offices": ["US, CA, Santa Clara", "US, TX, Austin"],
  "location": "US, CA, Santa Clara",
  "countryCode": "US",
  "workplaceType": "hybrid",
  "isRemote": false,
  "employmentType": "full-time",
  "url": "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite/job/US-CA-Santa-Clara/Senior-Backend-Engineer_JR2000001",
  "firstPublishedAt": "2026-10-21T00:00:00.000Z",
  "updatedAt": null,
  "requisitionId": "JR2000001",
  "language": null,
  "salary": null,
  "descriptionText": "...",
  "descriptionHtml": null,
  "changeType": "new",
  "scrapedAt": "2026-10-25T12:00:00.000Z"
}
```

With `includeDescription: "none"`, only what the job list shows is returned: title,
location (`"3 Locations"` for jobs in several places), requisition ID and a posting date
derived from "Posted N Days Ago" (`null` for jobs older than 30 days). `companyName`,
`employmentType`, all `offices` and the exact posting date come from the job page.
Workday has no structured salary field, so `salary` is `null`; pay ranges, when published,
are inside the description. A run summary (sites checked, failed or incomplete sites,
counts per change type) is saved in the `OUTPUT` record of the run's key-value store.

### Pricing

Pay per event, no subscription:

- $0.002 per job returned ($2 per 1,000 jobs)
- $0.001 per career site checked
- $0.001 per job page loaded (only when `includeDescription` is `text` or `html`)

Filters run **before** you are charged, so you only pay for jobs that match.
A daily monitor of 20 sites with `includeDescription: "none"` that returns 50 changes costs about $0.12 a day.

### Is it legal?

This Actor reads the job listings that each employer publishes on its public Workday
career site, the same data any visitor sees, without logging in. It keeps a low request
rate (about 4 requests per second in total) and does not bypass any access control.
It does not collect data about individuals: emails and phone numbers inside job descriptions
are masked. You are responsible for how you use the data.

### FAQ

**Why did a site fail?**
Check that the URL opens the career site in your browser. Some employers protect their
site against automated traffic; this Actor does not try to get around that and reports the
site as failed instead.

**A location filter misses jobs listed in several places.**
In the job list, those jobs show as `"3 Locations"`. Use `keywords` or `remoteOnly`, or run
without the location filter and filter the output.

**Greenhouse, Ashby or Lever?**
See our Greenhouse, Ashby and Lever Actors: same input, same output.

### Use it from an AI agent

Want Claude, Cursor or your own agent to search these jobs directly? The
[Career Site Jobs MCP Server](https://apify.com/nswk_api/career-site-jobs-mcp) exposes Greenhouse,
Ashby, Lever and Workday as MCP tools (`search_jobs`, `get_job_changes`, `get_salary_stats`),
with company names resolved automatically.

# Actor input Schema

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

Workday career site URLs, e.g. https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite. Any job URL of the site works too.

## `mode` (type: `string`):

"all" returns every matching job. "changes" returns only jobs that are new, updated or closed since the last run with the same monitor ID. Schedule it daily.

## `keywords` (type: `array`):

Keep jobs whose title or department contains any of these words. Case- and accent-insensitive.

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

Drop jobs whose title or department contains any of these words.

## `locations` (type: `array`):

Keep jobs whose location contains any of these, e.g. "remote", "United States", "London". Jobs listed in several places show as "3 Locations" in the list and only match after their page is loaded, so prefer remoteOnly or keywords for those.

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

Keep only jobs marked as remote.

## `postedWithinDays` (type: `integer`):

Keep only jobs posted in the last N days. Workday only gives exact dates up to 30 days back, so values above 30 behave like 30.

## `includeDescription` (type: `string`):

"text" and "html" open each returned job's page to add the description, company name, all locations, job type and exact posting date (charged as job details). "none" is cheaper and faster.

## `maxJobsPerCompany` (type: `integer`):

Safety cap on returned jobs per career site.

## `monitorId` (type: `string`):

Name of the saved state used by "changes" mode. Use a different ID for each watch list or filter set.

## `emitOnFirstRun` (type: `boolean`):

If off, the first "changes" run only saves a baseline and returns nothing.

## Actor input object example

```json
{
  "companies": [
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ],
  "mode": "all",
  "remoteOnly": false,
  "includeDescription": "text",
  "maxJobsPerCompany": 1000,
  "monitorId": "default",
  "emitOnFirstRun": true
}
```

# Actor output Schema

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

One item per job, in the dataset view.

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

Companies checked, failed companies with the reason, and counts per change type.

# 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": [
        "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("nswk_api/workday-jobs-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": ["https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"] }

# Run the Actor and wait for it to finish
run = client.actor("nswk_api/workday-jobs-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": [
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ]
}' |
apify call nswk_api/workday-jobs-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nswk_api/workday-jobs-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/FYeFhswWAesIC0ohs/builds/fom7reI0h5iHJ1Aaj/openapi.json