💼 Workday Job Scraper: Every Job, Past the 2,000 Cap avatar

💼 Workday Job Scraper: Every Job, Past the 2,000 Cap

Pricing

from $2.10 / 1,000 job records

Go to Apify Store
💼 Workday Job Scraper: Every Job, Past the 2,000 Cap

💼 Workday Job Scraper: Every Job, Past the 2,000 Cap

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.

Pricing

from $2.10 / 1,000 job records

Rating

0.0

(0)

Developer

Fin Data

Fin Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Security

Limited permissions

Share

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:

ShapeExample
Board URLhttps://workday.wd5.myworkdayjobs.com/Workday
With a language segmenthttps://workday.wd5.myworkdayjobs.com/en-US/Workday
A job pagehttps://carrier.wd5.myworkdayjobs.com/jobs/job/Atlanta/Project-Manager_30123
Short formworkday.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

{
"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
}
FieldTypeDefaultWhat it does
presetstringcustomEmployer list: custom (default), sample, georgia-sc. custom runs the sites you list and falls back to the sample boards when the list is empty
sourcesstring[][]Workday career-site URLs or tenant.wdN/site identifiers
keywordsstring[][]Keep jobs whose title contains any of these (case-insensitive)
excludeKeywordsstring[][]Drop jobs whose title contains any of these
locationsstring[][]Keep jobs whose location text contains any of these
departmentsstring[][]Reserved; Workday list pages do not expose a department
remoteOnlybooleanfalseKeep only jobs Workday flags as remote or whose location says remote
postedWithinDaysinteger0Keep only jobs posted in the last N days; 0 disables. "30+ Days Ago" postings pass unless fetchDetails is on
fetchDetailsbooleanfalseOne extra request per job (after filtering) for description, exact date, hiring organization, pay range, additional locations
includeDescriptionHtmlbooleanfalseAdd the raw HTML description next to the plain text (needs fetchDetails)
onlyNewbooleanfalseOutput only jobs not seen on a previous run of this source
seenStoreNamestringworkday-job-scraper-seenKey-value store that remembers seen job IDs; use one name per monitor
maxJobsPerSourceinteger0Stop after N jobs per board; 0 means the whole board
maxConcurrencyinteger5Boards pulled in parallel

Output

One record per job.

{
"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"
}
FieldMeaning
companyHiring organization name when fetchDetails is on, otherwise the tenant name
jobIdWorkday requisition ID (the JR- or R number). Stable across runs; use it as the key
location, locationsPrimary location and every listed location, primary first. Additional locations need fetchDetails
remotetrue when Workday's remote type says remote or the location says so; false for on-site; null when Workday does not say
postedAtISO 8601. From the exact posting date with fetchDetails, otherwise converted from "Posted N Days Ago". "30+ Days Ago" becomes null without fetchDetails
employmentTypeWorkday time type (Full Time, Part Time) with fetchDetails
salaryMin, salaryMax, salaryCurrency, salaryPeriod, salaryTextParsed from the pay range line in the description when the employer publishes one; otherwise null. 401(k) and similar benefit lines are ignored
descriptionTextPlain text, needs fetchDetails
extra.externalPathWorkday'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.

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

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

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.