# Workday Job Scraper — Enterprise Careers Sites at Scale (`atsdata/workday-job-scraper`) Actor

Scrape every open job from any Workday careers site (\*.myworkdayjobs.com). Handles tenant, host and site resolution, pagination, and per-job detail fetching for full descriptions.

- **URL**: https://apify.com/atsdata/workday-job-scraper.md
- **Developed by:** [ATS Data](https://apify.com/atsdata) (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

from $0.00005 / actor start

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

## Workday Job Scraper — Enterprise Careers Sites at Scale

Scrape every open job from any Workday careers site (\*.myworkdayjobs.com). Handles tenant, host and site resolution, pagination, and per-job detail fetching for full descriptions.

```
Input:   ["nvidia.com","https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"]
Output:  every open job — normalized, deduplicated, salary parsed
```

***

### What you actually get

Real rows from a live run:

| Job title | Company | Department | Location | Level | Salary |
|---|---|---|---|---|---|
| Software Engineer, Linux Graphics | nvidia | `null` | US, CA, Santa Clara | mid | `null` |
| Senior Applied Research Scientist, Multimodal Foundation Models | nvidia | `null` | US, CA, Santa Clara | senior | `null` |

Salary reads `null` when the company doesn't publish one — it is never guessed or filled in. Workday's list endpoint also omits department, so that field is `null` unless the posting carries it.

#### Straight to a spreadsheet

Export as CSV and nested fields flatten with `/` — no post-processing:

```csv
title,companySlug,department,locations/0,workplaceType,seniority,salary/min,salary/max,salary/currency,postedAt,source
"Software Engineer, Linux Graphics",nvidia,,"US, CA, Santa Clara",,mid,,,,2026-08-25,workday
"Senior Applied Research Scientist, Multimodal Foundation Models",nvidia,,"US, CA, Santa Clara",,senior,,,,2026-08-25,workday
```

Full records also carry `jobId`, `employmentType`, `applyUrl`, `descriptionText`, `descriptionHtml`,
`contentHash` and `scrapedAt`. Turn off `includeDescription` for a smaller, faster payload.

***

### Input

Accepts any of these, mixed freely:

Company domain (nvidia.com) or a Workday careers URL (https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite).

| Field | Type | Default | Description |
|---|---|---|---|
| `companies` | array | — | See above |
| `onlyNewJobs` | boolean | `false` | Return only jobs added or changed since the previous run |
| `trackingKey` | string | `default` | Track multiple company lists independently |
| `includeRemovedJobs` | boolean | `false` | Also emit jobs that disappeared |
| `includeDescription` | boolean | `true` | Include full description text and HTML |
| `maxJobsPerCompany` | integer | `0` | Cap per company (`0` = no limit) |
| `workdayFetchDetails` | boolean | `true` | Fetch each job's description (one extra request per job) |

You don't need to know the board slug. Pass the company domain and it gets resolved automatically.

***

### Change tracking — turn it into a hiring monitor

Set **`onlyNewJobs: true`** and schedule the Actor. Each run returns only what changed:

- `added` — posted since the last run
- `updated` — title, salary, location or description changed
- `removed` — job closed or pulled

The first run stores a baseline; every run after that is a diff. Useful for sales intelligence (hiring is a buying signal), recruiting, and keeping a job index fresh without re-ingesting everything.

***

### Output

```json
{
  "jobId": "workday:acme:12345",
  "source": "workday",
  "companySlug": "acme",
  "companyDomain": "acme.com",
  "title": "Senior Backend Engineer",
  "department": "Engineering",
  "team": "Platform",
  "locations": ["New York, NY", "Remote (US)"],
  "workplaceType": "hybrid",
  "employmentType": "FullTime",
  "seniority": "senior",
  "salary": { "min": 180000, "max": 240000, "currency": "USD", "period": "year" },
  "descriptionText": "…",
  "descriptionHtml": "…",
  "applyUrl": "https://…",
  "postedAt": "2026-04-07T17:12:35.753Z",
  "scrapedAt": "2026-08-24T18:03:28.104Z",
  "contentHash": "593a0ec77ef05d3c",
  "changeType": "added"
}
```

`contentHash` changes only when meaningful content changes — use it for your own diffing.

`seniority` is derived from the title: `intern`, `junior`, `mid`, `senior`, `principal`, `manager`, `director`, `executive`.

***

### Salary

Salary ranges are parsed out of the posting text, handling the formats companies actually use. Version numbers, headcounts and date ranges are not mistaken for salary.

```
$173,000.00 - $259,600.00/yr      →  173000–259600 USD/year
€55k–€70k per year                →  55000–70000 EUR/year
USD 90000 to 120000 annually      →  90000–120000 USD/year
The salary range is $10,000/month →  10000 USD/month
```

Companies that don't publish salary return `salary: null`. Nothing is invented.

***

### Speed

No browser, no proxies — just the public JSON endpoint Workday already serves.

| Board | Jobs | Time |
|---|---|---|
| Workday / nvidia | 2,000 | depends on detail fetching |

***

### A note on `workdayFetchDetails`

Workday's list endpoint returns no description, and for jobs open in several offices it returns `"2 Locations"` instead of naming them.

- **`true` (default)** — one extra request per job. You get the full description and the real location (`US, CA, Santa Clara`).
- **`false`** — much faster and cheaper, but descriptions are empty and multi-office jobs read `"N Locations"`.

Use `false` when you only need titles and a job count; use the default when you need usable data.

***

### Need more than Workday?

**[ATS Job Scraper](https://apify.com/atsdata/ats-job-scraper)** covers Greenhouse, Lever, Ashby and Workday in a single run with the same output schema — useful when your company list spans several ATS platforms.

***

### Notes

- Only **public** job board data is collected — the same pages any visitor can open. No accounts, no logins, no personal candidate data.
- Companies that can't be matched to a Workday board are skipped with a warning; the rest of the run continues.

# Actor input Schema

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

Company domain (nvidia.com) or a Workday careers URL (https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite).

## `onlyNewJobs` (type: `boolean`):

Compare against the previous run and return only added or changed jobs. Schedule this Actor daily to track hiring in near real time. The first run returns everything.

## `trackingKey` (type: `string`):

Name of the change-tracking state. Use different keys for independent company lists.

## `includeRemovedJobs` (type: `boolean`):

Also emit records for jobs that disappeared since the previous run.

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

Include full description text and HTML. Turn off for smaller, faster output.

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

Safety cap per company. 0 means no limit.

## `workdayFetchDetails` (type: `boolean`):

Workday's list endpoint has no descriptions, so each job needs one extra request. Turn off for titles and locations only, much faster.

## Actor input object example

```json
{
  "companies": [
    "nvidia.com",
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ],
  "onlyNewJobs": false,
  "trackingKey": "default",
  "includeRemovedJobs": false,
  "includeDescription": true,
  "maxJobsPerCompany": 0,
  "workdayFetchDetails": true
}
```

# Actor output Schema

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

All job records from this run, one item per job.

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

Counts for this run — total found, written, and the added/updated/removed breakdown when change tracking is on.

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

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

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,atsdata/workday-job-scraper"
        }
    }
}

```

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/2CFb9HQolD4iCq4Cb/builds/vUnw6Gvf5PcOSxfel/openapi.json