# Workday Jobs Scraper & API - Open Roles, Any Company (`neverempty/workday-jobs`) Actor

Track hiring across up to 200 Workday boards in one run, in one row shape you can diff daily. Zero open roles, a board that does not exist and a failed fetch are three different rows - never a silently empty result. Unofficial, not affiliated with Workday.

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

## Pricing

from $1.20 / 1,000 jobs

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/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 Jobs Scraper & API - Open Roles, Any Company

Pull every open job from any company's **Workday** job board, read straight from Workday's own public board API. No HTML scraping, no proxies, no API keys, nothing that breaks when a careers page is redesigned.

*Unofficial. This Actor is not affiliated with, endorsed by, or sponsored by Workday. All product names are trademarks of their respective owners.*

**Don't know a company's board name?** **[ATS Job Board Finder](https://apify.com/neverempty/ats-board-finder)** turns a domain into the board name this Actor takes.

***

### It never returns an empty result to mean two different things

Most job-board Actors return an empty dataset when something goes wrong, and an empty dataset when there is genuinely nothing to report. Those are not the same answer, and if you are monitoring hiring activity the difference is the whole point.

**Every board you ask for produces at least one row**, tagged in the `rowType` column:

| `rowType` | `ok` | What it means | Charged? |
|---|---|---|---|
| `job` | `true` | A real open job | Yes |
| `no-open-roles` | `true` | The board is live and has no open jobs (or none matching your filters) | **No** |
| `board-not-found` | `false` | No board with that name exists on Workday | **No** |
| `unavailable` | `false` | Workday could not be reached, or the entry could not be read as a board; `reason` says why | **No** |
| `budget-reached` | `false` | The run hit the **Max total charge** you set. Names every board that was cut short and every board not fetched because of it | **No** |
| `partial` | `true` | The rows are real, but the board has more than one run returns. Says how many of how many | **No** |

You are charged **only for `job` rows.**

***

### What Workday actually publishes - measured, not estimated

Run on 2026-09-01 with the shipped build and the default input: **622 job rows across 2 boards**.

| | nvidia (500) | redhat (122) |
|---|---|---|
| `title`, `jobUrl`, `locationRaw` | 100% | 100% |
| `postedAt` | **0%** | **0%** |
| `department`, `employmentType`, `workplaceType`, `isRemote` | **0%** | **0%** |
| `salaryMin` / `salaryMax` | **0%** | **0%** |

**Workday carries the least of the five.** Its board listing returns only the title, location, a job code and a relative "Posted 3 Days Ago" string - and a relative phrase is not a date, so `postedAt` stays `null` rather than being turned into a guess. That means **`remoteOnly`, `departmentContains` and `postedWithinDays` filter out every Workday row** - use `titleContains` and `locationContains` instead, or `remoteHint` for the guess. One run returns up to 500 roles per board; if a board has more you get a free `partial` row saying how many of how many you received, so a truncated run can never look complete.

***

### Input

| Field | Type | Default | What it does |
|---|---|---|---|
| `boards` | array | `workday:redhat.wd5.myworkdayjobs.com/jobs`, `workday:nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite` | One entry per company board, up to 200 |
| `titleContains` | string | *(empty)* | Keep only jobs whose title contains this text (case-insensitive) |
| `departmentContains` | string | *(empty)* | Keep only jobs whose department **or** team contains this text |
| `locationContains` | string | *(empty)* | Matches the primary location and every secondary location |
| `remoteOnly` | boolean | `false` | Keep only jobs Workday itself flags as remote - never a guess |
| `postedWithinDays` | integer | `0` (off) | Keep only jobs first published within N days. Unknown dates are excluded rather than assumed recent |
| `maxJobsPerBoard` | integer | `0` (no limit) | Cap of job rows per board, applied after filtering |
| `includeDescription` | boolean | `false` | Add the full description as plain text in `descriptionText` |
| `maxRetries` | integer | `3` | Total attempts per board for temporary errors (HTTP 429 / 5xx). A 404 is a permanent answer and is not retried |

**Naming a board:** the board URL - `https://<tenant>.wd5.myworkdayjobs.com/<Site>`. A bare company name never tries Workday, because the tenant and the site name are both part of the address.

***

### Output columns

`rowType`, `ok`, `reason`, `ats`, `companySlug`, `companyName`, `jobId`, `title`, `department`, `team`, `employmentType`, `locationRaw`, `locationsAll`, `country`, `city`, `workplaceType`, `isRemote`, `remoteHint`, `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryInterval`, `salaryText`, `postedAt`, `updatedAt`, `jobUrl`, `applyUrl`, `descriptionText`, `source`

All 29 columns are present on every row, in the same order - including the marker rows. **The Greenhouse, Lever, Ashby, Workable and Workday Actors all return these same 29 columns**, so adding another ATS never means rewriting your parser.

#### Two things it refuses to invent

- **`isRemote`** is set only when Workday itself says so. A guess based on the location text lives in a separate column called `remoteHint`, so you always know which is which. A job located in "Remote, Oregon" is not a remote job.
- **`salaryMin` / `salaryMax`** come only from structured compensation fields. Nothing is parsed out of prose, and a missing figure stays `null` - never `0`.

***

### How it is checked

- **148 automated checks** across 3 files, run before every publish
- **50 deliberate defects injected into the source; all 50 were caught by those checks** (re-run and verified 2026-09-03)
- Only public job boards are read. Nothing needs a login, and no private ATS data is accessed
- Every request has a 45-second timeout, so a silent server cannot hang the run
- Up to 200 boards per run

***

### The rest of the family

Same 29 columns, same row rules, one ATS each:

- **[greenhouse-jobs](https://apify.com/neverempty/greenhouse-jobs)** - Greenhouse boards
- **[lever-jobs](https://apify.com/neverempty/lever-jobs)** - Lever boards
- **[ashby-jobs](https://apify.com/neverempty/ashby-jobs)** - Ashby boards
- **[workable-jobs](https://apify.com/neverempty/workable-jobs)** - Workable boards
- **[ats-jobs-api](https://apify.com/neverempty/ats-jobs-api)** - all five in one run, for a mixed list
- **[ats-board-finder](https://apify.com/neverempty/ats-board-finder)** - a company domain to the ATS and board name it uses

### Support

Found a board that behaves oddly? Open an issue on the **Issues** tab and include the board name - it will be reproduced against the live API before anything is changed.

# Actor input Schema

## `boards` (type: `array`):

One entry per company job board. Use "<ats>:<board>" (greenhouse:stripe, lever:spotify, ashby:ramp, workable:lyst), or paste the job board URL, or give just the board name to try Greenhouse, Lever, Ashby and Workable. Workday can only be identified by its board URL (https://<tenant>.wd5.myworkdayjobs.com/<Site>), so a bare name never tries Workday. A board that does not exist is reported as a board-not-found row - it is never silently dropped. Up to 200 boards per run.

## `titleContains` (type: `string`):

Keep only jobs whose title contains this text (case-insensitive). Leave empty for all jobs.

## `departmentContains` (type: `string`):

Keep only jobs whose department or team contains this text (case-insensitive). Leave empty for all jobs.

## `locationContains` (type: `string`):

Keep only jobs whose location (primary or any secondary location) contains this text (case-insensitive). Leave empty for all jobs.

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

Keep only jobs the ATS itself flags as remote (Lever workplaceType, Ashby isRemote, Workable telecommuting). Jobs where remote status is only guessed from the location text are NOT included - that guess is exposed separately in the remoteHint column.

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

Keep only jobs first published within this many days. 0 disables the filter. Jobs with an unknown posting date are excluded when this filter is on, so the result never implies a date the source did not give.

## `maxJobsPerBoard` (type: `integer`):

Upper limit of job rows kept per board after filtering. 0 means no limit. You are only charged for job rows actually written to the dataset.

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

Add the full job description as plain text (HTML tags removed) in the descriptionText column. Off by default because it makes each run much heavier - the four default boards download 7.7 MB with descriptions versus 3.7 MB without, and Greenhouse alone goes from 0.35 MB to 4.4 MB (measured 2026-08-28).

## `maxRetries` (type: `integer`):

How many times to try a board in total, including the first attempt, when the ATS returns a temporary error (HTTP 429 or 5xx). Permanent answers such as 404 are not retried.

## Actor input object example

```json
{
  "boards": [
    "workday:redhat.wd5.myworkdayjobs.com/jobs",
    "workday:nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ],
  "titleContains": "",
  "departmentContains": "",
  "locationContains": "",
  "remoteOnly": false,
  "postedWithinDays": 0,
  "maxJobsPerBoard": 0,
  "includeDescription": false,
  "maxRetries": 3
}
```

# Actor output Schema

## `results` (type: `string`):

All rows produced by this run.

# 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 = {
    "boards": [
        "workday:redhat.wd5.myworkdayjobs.com/jobs",
        "workday:nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
    ]
};

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

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

```

## MCP server setup

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

```

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/FheQ1xKz8zYwBq6UU/builds/f0kztAMuDscCIS9IN/openapi.json