# 💼 Workday Job Scraper: Every Job, Past the 2,000 Cap (`findata/workday-job-scraper`) Actor

Scrape every open job from any Workday career site (myworkdayjobs.com). Pages the whole board past the 2,000-job cap. Title, location, pay range, posted date, description and apply link as clean JSON. Only-new mode for monitoring. No login, no proxies.

- **URL**: https://apify.com/findata/workday-job-scraper.md
- **Developed by:** [Fin Data](https://apify.com/findata) (community)
- **Categories:** Jobs
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.10 / 1,000 job 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/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 Job Scraper

Every open job from any Workday career site, as clean JSON. Paste a `myworkdayjobs.com` URL and get title, location, pay range, posted date, description and apply link for the whole board, including boards with more than 2,000 postings.

Built for recruiters and staffing firms watching enterprise employers, sales teams that treat hiring as a buying signal, job boards that need a direct feed, Workday consultants tracking Workday-titled roles, and AI agents that need job data without reverse-engineering Workday's job API.

### Why Workday needs its own scraper

Workday runs the career sites of most large enterprises (banks, hospitals, manufacturers, universities, state governments), and it is the hardest ATS to read well:

- The job API is undocumented and pages 20 jobs at a time.
- Every query stops at 2,000 results, so a board with 2,700 postings silently loses 700 to a naive scraper.
- List pages give relative dates ("Posted 3 Days Ago") and no description, hiring organization or pay.
- Tenant names are case-sensitive, site names vary per tenant, and language segments (`/en-US/`) appear in some URLs and not others.

This actor handles all of it. Boards over the cap are split by job family and location facets and de-duplicated, so you get the whole board. Relative dates are converted to ISO timestamps. With `fetchDetails` on, each job gets its exact posting date, hiring organization name, description, pay range and every listed location.

### What you get

- The whole board, including sites past the 2,000-job cap. Tested on a 2,763-job board.
- Pay ranges parsed from the posting when the employer publishes them ("Primary Location Base Pay Range: $168,000 USD - $252,000 USD" becomes `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryPeriod`).
- Only-new mode. Run it on a schedule and get only postings that were not on the board last time. You pay only for jobs that are output.
- Filters that run before billing and before detail requests: title keywords, exclude words, locations, remote only, posted within N days. A 2,000-job board filtered to one city costs a few dozen detail requests, not 2,000.
- Fail soft. One moved or renamed board is logged and skipped; the rest of the run completes.

### Finding a Workday career site

Open the company's careers page and click any job. If the address bar shows `myworkdayjobs.com`, paste that address as a source; the actor trims it to the board. Typical shapes:

| Shape | Example |
| --- | --- |
| Board URL | https://workday.wd5.myworkdayjobs.com/Workday |
| With a language segment | https://workday.wd5.myworkdayjobs.com/en-US/Workday |
| A job page | https://carrier.wd5.myworkdayjobs.com/jobs/job/Atlanta/Project-Manager_30123 |
| Short form | workday.wd5/Workday |

The tenant (`workday`), the Workday data center (`wd5`) and the site (`Workday`) are all in the URL. Nothing else is needed. If a board returns HTTP 422, the site name is wrong; copy it from a job page URL on that site.

### Input

```json
{
  "sources": [
    "https://workday.wd5.myworkdayjobs.com/en-US/Workday",
    "https://carrier.wd5.myworkdayjobs.com/jobs"
  ],
  "keywords": ["accountant", "financial analyst", "controller"],
  "locations": ["Atlanta", "Georgia", "GA"],
  "postedWithinDays": 14,
  "fetchDetails": true,
  "onlyNew": true
}
```

| Field | Type | Default | What it does |
| --- | --- | --- | --- |
| preset | string | custom | Employer list: `custom` (default), `sample`, `georgia-sc`. `custom` runs the sites you list and falls back to the sample boards when the list is empty |
| sources | string\[] | \[] | Workday career-site URLs or `tenant.wdN/site` identifiers |
| keywords | string\[] | \[] | Keep jobs whose title contains any of these (case-insensitive) |
| excludeKeywords | string\[] | \[] | Drop jobs whose title contains any of these |
| locations | string\[] | \[] | Keep jobs whose location text contains any of these |
| departments | string\[] | \[] | Reserved; Workday list pages do not expose a department |
| remoteOnly | boolean | false | Keep only jobs Workday flags as remote or whose location says remote |
| postedWithinDays | integer | 0 | Keep only jobs posted in the last N days; 0 disables. "30+ Days Ago" postings pass unless fetchDetails is on |
| fetchDetails | boolean | false | One extra request per job (after filtering) for description, exact date, hiring organization, pay range, additional locations |
| includeDescriptionHtml | boolean | false | Add the raw HTML description next to the plain text (needs fetchDetails) |
| onlyNew | boolean | false | Output only jobs not seen on a previous run of this source |
| seenStoreName | string | workday-job-scraper-seen | Key-value store that remembers seen job IDs; use one name per monitor |
| maxJobsPerSource | integer | 0 | Stop after N jobs per board; 0 means the whole board |
| maxConcurrency | integer | 5 | Boards pulled in parallel |

### Output

One record per job.

```json
{
  "vendor": "workday",
  "source": "https://workday.wd5.myworkdayjobs.com/en-US/Workday",
  "company": "Workday, Inc.",
  "jobId": "JR-0110787",
  "title": "Senior Product Manager, Technical",
  "location": "USA, CA, Pleasanton",
  "locations": ["USA, CA, Pleasanton"],
  "country": "US",
  "remote": null,
  "employmentType": "Full Time",
  "postedAt": "2026-11-04T00:00:00.000Z",
  "url": "https://workday.wd5.myworkdayjobs.com/Workday/job/USA-CA-Pleasanton/Senior-Product-Manager--Technical_JR-0110787",
  "descriptionText": "Your work days are brighter here...",
  "salaryMin": 168000,
  "salaryMax": 252000,
  "salaryCurrency": "USD",
  "salaryPeriod": "year",
  "salaryText": "Primary Location Base Pay Range: $168,000 USD - $252,000 USD",
  "extra": { "postedOnText": "Posted Today", "remoteType": null, "bulletFields": ["JR-0110787"], "endDate": null, "externalPath": "/job/USA-CA-Pleasanton/Senior-Product-Manager--Technical_JR-0110787" },
  "scrapedAt": "2026-11-05T01:47:38.912Z"
}
```

| Field | Meaning |
| --- | --- |
| company | Hiring organization name when fetchDetails is on, otherwise the tenant name |
| jobId | Workday requisition ID (the `JR-` or `R` number). Stable across runs; use it as the key |
| location, locations | Primary location and every listed location, primary first. Additional locations need fetchDetails |
| remote | true when Workday's remote type says remote or the location says so; false for on-site; null when Workday does not say |
| postedAt | ISO 8601. From the exact posting date with fetchDetails, otherwise converted from "Posted N Days Ago". "30+ Days Ago" becomes null without fetchDetails |
| employmentType | Workday time type (Full Time, Part Time) with fetchDetails |
| salaryMin, salaryMax, salaryCurrency, salaryPeriod, salaryText | Parsed from the pay range line in the description when the employer publishes one; otherwise null. 401(k) and similar benefit lines are ignored |
| descriptionText | Plain text, needs fetchDetails |
| extra.externalPath | Workday's path for the job; `url` is the full link |

A `RUN_SUMMARY` record in the default key-value store reports boards processed, jobs fetched, filtered, de-duplicated, skipped as already seen, and any board failures with the error text.

### Pricing

Pay per event. You are charged per job record written to the dataset, plus a small actor-start event. Filtered-out jobs and already-seen jobs in only-new mode are not charged. No proxies are needed, so platform usage is minimal: a 2,000-job board costs about 100 list requests and a few cents of platform usage.

### Monitoring new postings

1. Set `onlyNew` to true and give `seenStoreName` a name for this monitor.
2. Add your filters.
3. Schedule the actor (daily is enough; Workday boards change slowly).
4. Connect the dataset to Google Sheets, Slack, Make, Zapier or a webhook from the Integrations tab.

The first run outputs everything on the boards and remembers it. Each later run outputs only what is new.

### Limits and notes

- Public job-board endpoints only. No login, no proxies, no candidate or private data.
- A few employers block datacenter traffic at the network edge and return HTTP 500 for every request. That board is reported in `RUN_SUMMARY` and the run continues.
- Very large boards with coarse facets may still miss a handful of postings above the 2,000 cap.
- This actor reads Workday career sites only. For Greenhouse, Lever, Ashby or SmartRecruiters, or for a mixed list where you do not know the ATS, use the FinData Career Site Job Scraper.

### Related FinData job scrapers

Same engine, same output fields, so records from any of them can be combined.

- [Greenhouse Job Scraper](https://apify.com/findata/greenhouse-job-scraper)
- [Lever Job Scraper](https://apify.com/findata/lever-job-scraper)
- [Ashby Job Scraper](https://apify.com/findata/ashby-job-scraper)
- [Career Site Job Scraper (any company, ATS auto-detected)](https://apify.com/findata/career-site-job-scraper)
- [Workday, Greenhouse, Lever, Ashby, SmartRecruiters Job Scraper (all five in one actor)](https://apify.com/findata/ats-jobs-feed)

### For AI agents

Every field is optional: an empty input `{}` runs the sample boards and returns jobs, so a first call never fails. Pick `"preset": "sample"` to say so explicitly, or `"preset": "georgia-sc"` for the curated Georgia and upstate SC employer list. Minimal call: `{ "sources": ["https://workday.wd5.myworkdayjobs.com/Workday"] }`. Add `"keywords"` and `"locations"` arrays to narrow, `"fetchDetails": true` for descriptions and pay. Every record has the same fields; `jobId` is the stable key.

### Using it from code

```js
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('findata/workday-job-scraper').call({
    sources: ['https://workday.wd5.myworkdayjobs.com/en-US/Workday'],
    keywords: ['engineer'],
    fetchDetails: true,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
```

Works the same through the Apify API, MCP server and the Python client.

# Actor input Schema

## `preset` (type: `string`):

Pick a ready-made list or use your own. "The career sites I list below" runs exactly the sites in the next field, and if that field is empty it falls back to the sample boards so a run never fails for lack of input. The other choices add a curated list on top of anything you paste.

## `sources` (type: `array`):

Workday career-site URLs, one per line. Any page on the site works; the actor trims it to the board. You can also write the short form tenant.wdN/site, for example workday.wd5/Workday. Examples: https://workday.wd5.myworkdayjobs.com/en-US/Workday, https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite, https://carrier.wd5.myworkdayjobs.com/jobs. Optional when an Employer list is chosen above.

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

Keep jobs whose title contains at least one of these words or phrases. Case-insensitive. Leave empty to keep all.

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

Drop jobs whose title contains any of these words or phrases. Case-insensitive.

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

Keep jobs whose location text contains at least one of these, e.g. Atlanta, Georgia, GA, United States. Case-insensitive. Leave empty to keep all. With the Georgia and upstate SC list chosen and this left empty, the list's own Georgia and South Carolina locations are used.

## `departments` (type: `array`):

Keep jobs whose department or team contains at least one of these, e.g. Finance, Engineering, People.

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

Keep only jobs the ATS marks as remote or whose location says remote.

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

Keep only jobs posted or updated within this many days. 0 means no limit. Workday list pages only give relative dates, so this is applied to the parsed value.

## `fetchDetails` (type: `boolean`):

Workday list pages do not include the description, the exact posting date or the hiring organization name. Turn this on to make one extra request per job for those plus pay ranges and additional locations. Title and location filters are applied first, so only jobs that can pass them are fetched. Slower and uses more platform usage.

## `includeDescriptionHtml` (type: `boolean`):

Add the raw HTML description to each record alongside the plain text. Makes datasets larger.

## `onlyNew` (type: `boolean`):

Remember every job ID seen per source in a named key-value store and output only jobs not seen before. Use with a schedule to get a feed of new postings. You are charged only for jobs that are output.

## `seenStoreName` (type: `string`):

Name of the key-value store used by only-new mode. Use a different name per monitor if you run several configurations.

## `maxJobsPerSource` (type: `integer`):

Stop paging a source after this many jobs. 0 means no limit. Workday boards cap at 2,000 per query; the actor splits large boards by facet automatically so you still get the whole board.

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

How many career sites to pull at the same time.

## Actor input object example

```json
{
  "preset": "custom",
  "sources": [
    "https://workday.wd5.myworkdayjobs.com/en-US/Workday",
    "https://ncr.wd1.myworkdayjobs.com/ext_us",
    "https://pultegroup.wd1.myworkdayjobs.com/PGI",
    "https://tsys.wd1.myworkdayjobs.com/tsys",
    "https://carrier.wd5.myworkdayjobs.com/jobs"
  ],
  "keywords": [],
  "excludeKeywords": [],
  "locations": [],
  "departments": [],
  "remoteOnly": false,
  "postedWithinDays": 0,
  "fetchDetails": false,
  "includeDescriptionHtml": false,
  "onlyNew": false,
  "seenStoreName": "workday-job-scraper-seen",
  "maxJobsPerSource": 0,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

One record per job posting, normalized across Workday, Greenhouse, Lever, Ashby and SmartRecruiters.

## `jobsTable` (type: `string`):

Same records in the Console table view.

## `runSummary` (type: `string`):

Sources processed, jobs fetched, filtered, de-duplicated, already seen, and any source failures.

# 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 = {
    "sources": [
        "https://workday.wd5.myworkdayjobs.com/en-US/Workday",
        "https://ncr.wd1.myworkdayjobs.com/ext_us",
        "https://pultegroup.wd1.myworkdayjobs.com/PGI",
        "https://tsys.wd1.myworkdayjobs.com/tsys",
        "https://carrier.wd5.myworkdayjobs.com/jobs"
    ],
    "keywords": [],
    "excludeKeywords": [],
    "locations": [],
    "departments": [],
    "seenStoreName": "workday-job-scraper-seen"
};

// Run the Actor and wait for it to finish
const run = await client.actor("findata/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 = {
    "sources": [
        "https://workday.wd5.myworkdayjobs.com/en-US/Workday",
        "https://ncr.wd1.myworkdayjobs.com/ext_us",
        "https://pultegroup.wd1.myworkdayjobs.com/PGI",
        "https://tsys.wd1.myworkdayjobs.com/tsys",
        "https://carrier.wd5.myworkdayjobs.com/jobs",
    ],
    "keywords": [],
    "excludeKeywords": [],
    "locations": [],
    "departments": [],
    "seenStoreName": "workday-job-scraper-seen",
}

# Run the Actor and wait for it to finish
run = client.actor("findata/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 '{
  "sources": [
    "https://workday.wd5.myworkdayjobs.com/en-US/Workday",
    "https://ncr.wd1.myworkdayjobs.com/ext_us",
    "https://pultegroup.wd1.myworkdayjobs.com/PGI",
    "https://tsys.wd1.myworkdayjobs.com/tsys",
    "https://carrier.wd5.myworkdayjobs.com/jobs"
  ],
  "keywords": [],
  "excludeKeywords": [],
  "locations": [],
  "departments": [],
  "seenStoreName": "workday-job-scraper-seen"
}' |
apify call findata/workday-job-scraper --silent --output-dataset

```

## MCP server setup

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