Workday Jobs Scraper: Job Postings From Any Company's Careers Site

Workday Jobs Scraper turns any company's Workday-hosted careers site into clean, structured job data. Search by keyword and facet filters inside one or more company sites, or paste careers-page and direct job URLs to scrape as-is. Get title, full description, locations, time type, posting dates, employer details, apply link, and structured country and geo for every job, then export to JSON, CSV or Excel, read the dataset through the API, or send a summary into the apps you already use.

Why This Scraper?

• Works with any Workday-hosted employer automatically. The regional cluster and site id are read straight out of the careers URL you give it, no manual lookup needed.
• Two ways to start. Run a keyword and facet search inside one or more company careers sites, or paste any Workday careers or job URL and scrape it exactly as given, including filters already carried on the link.
• Comprehensive job record. Structured country and location, job requisition and posting ids, employer details, apply type and link, and a best-effort salary breakdown, on top of the full HTML and plain-text description.
• Filters matched against the live site, not guessed. Job category, job type, time type and location values you type are checked against each company site's own current facet list, and anything that does not match is dropped with a warning instead of silently narrowing or widening your results.
• Saves each job as it is collected. A run that stops partway still delivers what it found, and resumeFromRunId can continue one interrupted pull without re-collecting or re-charging jobs it already has.
• Built for recurring monitoring. Incremental mode classifies every job as NEW, UPDATED, UNCHANGED or EXPIRED across scheduled runs against state the actor keeps for you, no dataset id to paste each time.

Use Cases

• Recruiting and talent sourcing teams: track new openings at target or portfolio companies as they post, by keyword or category.
• Market and competitive research: monitor hiring volume and role mix across companies over time to spot expansion or contraction.
• Job boards and aggregators: pull structured listings from any number of Workday-hosted employers into one consistent schema.
• Sales and business development: watch a prospect's hiring signals, such as new roles in a region or department, as a proxy for growth.
• Data science and workforce research: build a dataset of job titles, locations and posting dates for trend analysis.

Data You Get

Sample shape: values are illustrative placeholders, not from a live listing.

Field	Example
rowType	"job"
title	"Sample Software Engineer"
jobReqId	"JR0000000"
jobUrl	"https://company.wd5.myworkdayjobs.com/en-US/SiteName/job/Location/Title_JR0000000"
externalPath	"/job/Location/Title_JR0000000"
locationText	"US, CA, Sample City"
country	"US" (from the job detail page; null when fetchDetails is off)
timeType	"Full time" (detail page only)
postedOn	"Posted 5 Days Ago"
startDate	"2026-01-01" (detail page only)
employerName	"Sample Company" (from the detail page; falls back to the tenant slug from the URL host when no employer name is available or full details are off)
applyUrl	"https://company.wd5.myworkdayjobs.com/en-US/SiteName/job/Location/Title_JR0000000/apply"
applyType	"workday" (also "external"; detail page only, otherwise null)
salary	{ "rawText": "$120,000 - $150,000", "min": 120000, "max": 150000, "currency": "USD", "period": "year" } (best-effort, parsed from the description; all null when no figure is found)
description / descriptionText	full HTML and stripped plain-text job description (detail page only)
jobPostingId	"00000000-0000-0000-0000-000000000000" (detail page only)
canApply	true (detail page only)
location	{ "text": "US, CA, Sample City", "additional": [], "requisitionLocation": {} }
employer	{ "name": "Sample Company", "tenantSlug": "company", "careersUrl": "...", "url": "..." }
scrapedAt	"2026-01-01T00:00:00.000Z"

The full record also carries postingInternalId, jobPostingSiteId, questionnaireId, posted, includeResumeParsing, externalUrl, hiringOrganization and similarJobs, all null or empty unless fetchDetails fetched that job's detail page, plus a source object recording the search URL, site id, tenant, regional cluster and language the job came from. In incremental mode, every record also carries changeType (NEW, UPDATED, UNCHANGED, REAPPEARED or EXPIRED), changedFields, firstSeenAt and lastSeenAt.

How to Use

1. Pick a mode: search (keyword and facet search inside one or more company careers sites) or url (scrape any Workday careers or job URL exactly as given).
2. For search mode, add one or more company careers-site URLs and, optionally, a keyword and facet filters. For URL mode, paste careers-page and/or direct job URLs, mixed freely.
3. Leave Fetch full job details on for the full field set, set Max jobs to control run size and cost, then click Start.
4. Download the dataset as JSON, CSV or Excel, read it through the API, or schedule the run and turn on Incremental mode for recurring monitoring.

Search one company site by keyword:

{
  "mode": "search",
  "companyUrls": ["https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite"],
  "keyword": "engineer",
  "timeType": "Full time",
  "maxItems": 100,
  "fetchDetails": true
}

Search across several companies at once, with a category filter (the scheme is optional):

{
  "mode": "search",
  "companyUrls": [
    "company-a.wd1.myworkdayjobs.com/en-US/Careers",
    "company-b.wd5.myworkdayjobs.com/en-US/External"
  ],
  "jobCategory": "Engineering",
  "maxItems": 200,
  "fetchDetails": false
}

Scrape Workday URLs directly, mixing a filtered careers page and a single job:

{
  "mode": "url",
  "urls": [
    "https://company.wd5.myworkdayjobs.com/en-US/SiteName?q=engineer",
    "https://company.wd5.myworkdayjobs.com/en-US/SiteName/job/Location/Title_JR0000000"
  ]
}

Recurring daily monitoring of one company's search, only new and changed jobs:

{
  "mode": "search",
  "companyUrls": ["https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite"],
  "keyword": "data scientist",
  "incrementalMode": true,
  "stateKey": "nvidia-data-scientist"
}

Run it from your code

Python:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("abotapi/myworkdayjobs-scraper").call(run_input={
    "mode": "search",
    "companyUrls": ["https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite"],
    "keyword": "engineer",
})
for job in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(job["title"], job["locationText"])

JavaScript:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('abotapi/myworkdayjobs-scraper').call({
  mode: 'search',
  companyUrls: ['https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite'],
  keyword: 'engineer',
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Or connect it to Make, Zapier, n8n, Google Sheets or webhooks from the Integrations tab.

Resume and recurring updates

• Resume (resumeFromRunId) continues one interrupted run: paste its run or dataset ID and the actor skips every job it already collected there, so a large walk-all pull can be finished across separate runs without paying twice. Pasting a run or dataset ID this Apify account cannot read fails the run outright, before anything is scraped.
• Incremental mode (incrementalMode) is for running the same search or URL list again and again, for example daily. Each job is classified NEW, UPDATED (with changedFields), UNCHANGED (suppressed and not billed unless emitUnchanged is on), or EXPIRED (only after a run that scanned every tracked entry to its natural end, and only with emitExpired on; a run capped by Max jobs, or a resumed run, skips expiry detection and leaves the previous state as-is). REAPPEARED is a distinct case: it is only produced for a job that a previous run already marked EXPIRED, and it then turns up again in a later run. It never appears on a state key where emitExpired has not been used. stateKey names or shares one monitoring campaign; leave it empty and the actor derives a key from the mode, sites/URLs and filters, so different searches never mix state. With incremental mode off, output is exactly as before.
• Turning incrementalMode on together with resumeFromRunId fails the run if that state key already has tracked jobs from an earlier run, since the two are different ways of avoiding duplicate work and mixing them on an established campaign is ambiguous. It succeeds as a one-time bootstrap when the state key has no history yet.

Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step after the scrape: the Apify dataset is never changed.

What gets written to the connector: a condensed, human-readable summary of each job, not the full JSON. Each job becomes one entry with a title and its key fields flattened to plain text. The complete record always stays in the Apify dataset.

1. Authorize a connector once under Apify → Settings → Integrations (Notion, Linear, Airtable, or Apify).
2. Select it in the "Pipe results into your apps" input field. (If the picker is empty, you haven't authorized a connector yet.)
3. For Notion, also set notionParentPageUrl to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.

Input Parameters

Parameter	Type	Default	Description
mode	string	search	search = keyword/facet search inside the sites in companyUrls. url = scrape the entries in urls as-is.
companyUrls	array	none (prefill: a sample NVIDIA careers URL shown in the UI)	Search mode. One or more company careers-site URLs or hosts to search within (scheme optional).
keyword	string	(none)	Search mode. Free-text keyword applied as the Workday search query. Leave empty to list all jobs.
jobCategory	string	(none)	Search mode. Job category (job family group) filter, matched against the site's live facet list.
jobType	string	(none)	Search mode. Job type (worker sub type) filter, matched against the live facet list.
timeType	string	(none)	Search mode. Time type filter, for example Full time, matched against the live facet list.
location	string	(none)	Search mode. Location filter, matched against the live facet list.
urls	array	none	URL mode. Workday careers-page and/or direct job URLs, scraped as-is. Mix freely.
fetchDetails	boolean	true	Fetch each job's detail page for the full field set (description, structured country/geo, employer, apply type, ids). Off returns only the fields available on the listing card.
maxItems	integer	20	Maximum job rows to emit per company site or careers URL entry. 0 means unlimited.
proxy	object	Apify Proxy (datacenter)	Connection settings. The default works directly against Workday's public job API.
residentialCountries	array	["US","GB","DE","CA","AU","FR","NL","SG"]	Exit countries rotated through when a run falls back to residential.
residentialBudgetGb	string	(none, no cap)	Hard cap on bandwidth for the automatic residential fallback. 0 disables that fallback. Does not limit a residential group you select yourself under Connection.
mcpConnectors	array	(none)	Optional: send a summary of each job to apps you authorized under Integrations.
notionParentPageUrl	string	(none)	Notion connector only: page under which job pages are created.
maxNotifyListings	integer	50	Cap on items written to each connector per run. Does not affect the dataset.
resumeFromRunId	string	(none)	Continue one interrupted run without re-collecting or re-charging jobs it already has.
incrementalMode	boolean	false	Turn on for recurring monitoring: classify jobs as NEW, UPDATED, UNCHANGED, REAPPEARED or EXPIRED against remembered state.
stateKey	string	(none)	Names or shares one incremental-mode monitoring campaign. Auto-derived from mode/sites/filters when left empty.
emitUnchanged	boolean	false	Also return (and bill) jobs unchanged since the last run.
emitExpired	boolean	false	Also return (and bill) jobs no longer found, after a complete scan of the tracked search.

Output Example

Sample shape: values are illustrative placeholders, not from a live listing.

{
  "rowType": "job",
  "jobReqId": "JR0000000",
  "postingInternalId": "00000000000000000000000000000000",
  "jobPostingId": "00000000-0000-0000-0000-000000000000",
  "jobPostingSiteId": null,
  "questionnaireId": null,
  "title": "Sample Software Engineer",
  "jobUrl": "https://company.wd5.myworkdayjobs.com/en-US/SiteName/job/Location/Title_JR0000000",
  "externalPath": "/job/Location/Title_JR0000000",
  "postedOn": "Posted 5 Days Ago",
  "startDate": "2026-01-01",
  "timeType": "Full time",
  "posted": true,
  "canApply": true,
  "includeResumeParsing": true,
  "locationText": "US, CA, Sample City",
  "country": "US",
  "employerName": "Sample Company",
  "description": "<p>Full job description HTML appears here.</p>",
  "descriptionText": "Full job description text appears here.",
  "salary": { "rawText": "$120,000 - $150,000", "min": 120000, "max": 150000, "currency": "USD", "period": "year" },
  "applyUrl": "https://company.wd5.myworkdayjobs.com/en-US/SiteName/job/Location/Title_JR0000000/apply",
  "applyType": "workday",
  "externalUrl": null,
  "location": { "text": "US, CA, Sample City", "additional": [], "requisitionLocation": {} },
  "employer": { "name": "Sample Company", "tenantSlug": "company", "careersUrl": "https://company.wd5.myworkdayjobs.com/en-US/SiteName", "url": "https://company.wd5.myworkdayjobs.com/en-US/SiteName" },
  "hiringOrganization": { "name": "Sample Company" },
  "similarJobs": [],
  "source": { "searchUrl": "https://company.wd5.myworkdayjobs.com/en-US/SiteName", "site": "SiteName", "tenant": "company", "dc": "wd5", "host": "company.wd5.myworkdayjobs.com", "lang": "en-US" },
  "scrapedAt": "2026-01-01T00:00:00.000Z"
}

Plan Requirement

The default connection setting works directly against Workday's public job API and needs no special access. If requests keep failing, the actor automatically falls back to residential connections, rotating through residentialCountries; residentialBudgetGb caps that fallback's bandwidth, and 0 disables it. For the rare company that geo-restricts its careers content you can also select the residential group under Connection yourself; that traffic is not counted against residentialBudgetGb.

FAQ

How much does it cost?

You pay a small fee when a run starts, a per-job fee for each job row returned, and an extra detail-enrichment fee only for jobs whose detail page was fetched and parsed, which happens when fetchDetails is on. The Pricing tab shows the current rates. Use Max jobs to cap the size, and cost, of any run.

Is it legal to scrape a company's Workday careers site?

This actor collects only publicly available job postings. You are responsible for how you use it: follow the site's terms and the laws that apply to you, and get legal advice if you plan commercial redistribution of the data.

Can I get only new or changed jobs on a schedule?

Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new and updated jobs by default. Jobs that disappear are only returned, marked EXPIRED, once you also turn on Emit expired and a run scans its whole tracked search; a job that later reappears after being marked EXPIRED that way comes back marked REAPPEARED.

What is the difference between Resume and Incremental mode?

Resume (resumeFromRunId) continues one specific interrupted run so you do not re-collect or re-pay for jobs it already has. Incremental mode is for running the same search again and again over time and getting only what changed. Combining both on a search that already has incremental history fails the run on purpose, so the two mechanisms cannot silently disagree about what "already collected" means.

Why did my run return an empty dataset instead of failing?

Search mode with no company site, or URL mode with no URLs, finishes successfully with nothing to scrape rather than failing. The same is true for a Workday URL the actor cannot recognize, or a company site whose requests keep being rejected after the built-in retry attempts: that entry is skipped with a warning in the run log, and any other entries in the same run still complete and are returned.

Why did my run fail instead of returning an empty dataset?

The run fails outright, before scraping, only when resumeFromRunId points to a run or dataset your Apify account cannot read, or when incrementalMode and resumeFromRunId are combined on a state key that already has tracked jobs from an earlier run. Both are deliberate: continuing from an unreadable or ambiguous baseline would otherwise look like a normal, if empty, result.

Can I use it with AI agents or MCP?

Yes. Call it from any Apify integration or MCP client, and use the connector field to push a summary of each job into Notion, Linear or Airtable.

🔗 Want more jobs data?

Pair this actor with these related scrapers from the same team:

💼 Cwjobs UK From $1/1k. Scrape tech and IT jobs from CWJobs.co.uk into clean, structured data. Search...	💼 Jora Jobs Scraper Scrape Jora.com job listings across supported countries by keyword, filters, or URL...
💼 IrishJobs.ie Scraper Scrape job listings from IrishJobs.ie by keyword, location, job type, salary, recency, or...	💼 RepVue Scraper Scrape RepVue company profiles, RepVue Score, sales-rep reviews, and compensation by role...
💼 France Travail Scraper Scrape job offers from France Travail with titles, companies, locations, salaries...	💼 RemoteOK Jobs Scraper Scrape RemoteOK jobs by keyword or job URL. Extract title, company, location, remote...

👉 Browse all abotapi scrapers

💬 Support & custom scrapers

• 🐞 Found a bug or a missing field? Open a ticket on the Issues tab. We usually reply within hours.
• 🛠️ Need another site, extra fields or a private build? Email abotapi@proton.me or message Telegram @abotapi.
• ⭐ Enjoying it? A quick review on the actor page helps other users find it.