← data exports  /  apify actor

Workday Jobs Scraper: Salary, Dates, Remote

how to get the data with our Apify actor workday-jobs-scraper

Collect every open job from any Workday careers site (myworkdayjobs.com): title, location, country, remote or on site, employment type, real posting date, pay range where the posting states it, and the description as plain text. Filter by title, location, remote and date.

on apify
v0iddo/workday-jobs-scraper
category
jobs, automation
build
0.1.5, built 2026-11-11
billing
Apify bills it per result; the price for your plan is on the actor's page.

What you get

Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API.

The main fields of each row:

  • System (ats)
  • company
  • title
  • location
  • country
  • remote
  • Workplace (workplaceType)
  • Employment (employmentType)
  • Posted (postedAt)
  • Pay from (salaryMin)
  • Pay to (salaryMax)
  • Currency (salaryCurrency)
  • Link (url)

What people use it for

  • Hiring signals: see which large employers open roles in a team, a country or remote.
  • Salary research: collect the pay ranges that US postings on Workday publish, with currency and interval.
  • Job boards and newsletters: a feed of fresh postings from Workday employers with the exact posting date.
  • Recruiting: watch the careers sites of target employers for new remote roles on a schedule.

Run it on Apify

  1. Open workday-jobs-scraper on Apify and sign in, or make an Apify account.
  2. On the Input tab, fill in the fields listed below. The form opens with example values filled in.
  3. Click Start. Rows appear on the Output tab while the run works.
  4. Export the rows as JSON, CSV, Excel, XML or HTML, or read them through the Apify API.
  5. To run it again on a schedule, save the input as a task and add a schedule in the Apify Console.

What you can set

  • Workday careers sites (companies): One careers site link per line, at most 200. Open the company's job search page and copy its address, for example https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite or https://salesforce.wd12.myworkdayjobs.com/External_Career_Site. Links to a single job, with a language part such as /en-US/, or on myworkdaysite.com work too.
  • Job title keywords (titleKeywords): Optional. Only postings whose title contains at least one of these words or phrases are returned. Capitals and accents do not matter.
  • Location contains (locationContains): Optional text such as Berlin, Remote, Canada or US. Only postings whose location, or country code, has a word starting with it are returned: US finds US and USA, not Australia.
  • Remote jobs only (remoteOnly): Return only postings that are marked remote or say remote in their location. Postings whose remote status is unknown are left out. Default: false.
  • Posted within days (postedWithinDays): Optional. Skip postings that were published longer ago than this. Postings from sources that show no publication date are kept.
  • Include description text (includeDescription): Add the job description as plain text, with the exact posting date, the country, the workplace and the pay range. Switch it off for a faster run that reads only the search pages. Default: true.
  • Maximum jobs per company (maxJobsPerCompany): Optional. Stop reading a company after this many matching postings and go on to the next one, so a large employer first in the list does not fill the whole run. Empty: every matching posting, up to Maximum results.
  • Maximum results (maxItems): The run stops after this many result rows. It also caps what one run can cost. Default: 500.
  • Proxy configuration (proxyConfiguration): Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network.

Example input

This is the input the actor is tested with every day.

example inputjson
{
  "companies": [
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite",
    "https://salesforce.wd12.myworkdayjobs.com/External_Career_Site"
  ],
  "includeDescription": true,
  "maxItems": 50,
  "maxJobsPerCompany": 25
}

Run it from Python

The official apify-client package starts the run, waits for it and reads the rows. It needs your own Apify API token.

needs your own Apify tokenpython
# pip install apify-client
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")  # your own API token, from the Apify Console
run_input = {
    "companies": [
        "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite",
        "https://salesforce.wd12.myworkdayjobs.com/External_Career_Site",
    ],
    "includeDescription": True,
    "maxItems": 50,
    "maxJobsPerCompany": 25,
}
run = client.actor("v0iddo/workday-jobs-scraper").call(run_input=run_input)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Limits

  • Paste the link of the company's Workday job search page, the address on myworkdayjobs.com or myworkdaysite.com. Up to 200 sites per run; the company field is the Workday tenant name (for example nvidia).
  • Every job of a site comes back, also past the 2,000 that one Workday list shows: a bigger site (NVIDIA has about 2,800) is read again one filter value at a time, such as a job category or a country, and each job is returned once, the site's own order first.
  • Workday's search pages say only Posted Today or Posted 3 Days Ago. With description text on, each posting is read once more and Posted is its exact start date; with it off, the relative day is turned into a date and Posted 30+ Days Ago stays empty.
  • Postings listed in several locations carry every location, joined by a semicolon, and the country of the first. Remote is true when the posting is marked remote or names a remote location.
  • Pay is read from the description where the posting states a range, as in many US postings: the first range on a line about salary or pay. Interval is year or hour when the text says so.
  • Workday postings carry no department, team or update time, so those fields stay empty. They are kept so the rows match our multi-system jobs scraper.
  • Location contains matches the start of a word in the location text, or the country code, so US finds US and USA but not Australia. Job title keywords match the title only. Both are applied before the extra read, so filtered out postings cost nothing.
  • Recruiter and other contact names are not collected. E-mail addresses, phone numbers, handles and profile links are removed from the description text.
  • A careers site that is not found, or whose robots.txt closes it, is skipped and the rest of the list is still read. For Greenhouse, Lever, Ashby, Workable, Recruitee, Personio and BambooHR boards use our multi-system jobs scraper, which returns the same fields.
  • Not affiliated with Workday.
  • Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
  • The actor reads only pages that the site's robots.txt leaves open to automated access.
  • Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
  • Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.

Questions

Do I need an account on the Workday careers sites, cookies or an API key?

No. The actor reads only what every visitor of the Workday careers sites can see, without logging in. You only need an Apify account to start it.

How many results can one run return?

Up to 20,000 rows per run. Without a limit it stops at 500. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.

Why did my run return no results?

The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

More

every fact here is read from the actor's public data on Apify, every day; it last changed on