Workday Jobs Scraper: Any myworkdayjobs.com Career Site avatar

Workday Jobs Scraper: Any myworkdayjobs.com Career Site

Pricing

$2.00 / 1,000 jobs

Go to Apify Store
Workday Jobs Scraper: Any myworkdayjobs.com Career Site

Workday Jobs Scraper: Any myworkdayjobs.com Career Site

Workday jobs scraper and API for any Workday career site (myworkdayjobs.com, myworkdaysite.com): job postings as JSON or CSV with locations, requisition ID, hiring entity, salary and full description. Only-new-jobs mode. No login. $2 per 1,000 jobs. Not affiliated with Workday.

Pricing

$2.00 / 1,000 jobs

Rating

0.0

(0)

Developer

fecklesspleb

fecklesspleb

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

12 hours ago

Last modified

Features

Limited permissions

Share

Scrape Workday jobs from any Workday career site (myworkdayjobs.com or myworkdaysite.com): $2 per 1,000 jobs

This Workday jobs scraper reads the public career site of any company that hires through Workday (<company>.wdN.myworkdayjobs.com or wdN.myworkdaysite.com/recruiting/<company>/...) and outputs every open job as structured JSON: title, companyName, locations, remote type, posting date, time type, requisition ID, hiring entity, apply link and full description. It costs $0.002 per job written to the dataset ($2 per 1,000 jobs), with no start fee, and nothing for jobs that are filtered out. It is an independent scraper, not a Workday product, and is not affiliated with or endorsed by Workday.

Sample output: the first item from a local run of the prefilled example input ({"companies": ["https://utaustin.wd1.myworkdayjobs.com/UTstaff"], "maxTotalJobs": 4}) on 10 November 2026, shortened to 12 of its 34 fields (descriptionText and the rest are in the full item):

{
"id": "R_00049214",
"ats": "workday",
"companySlug": "utaustin/UTstaff",
"companyName": "The University of Texas at Austin",
"title": "Manager, Clinical Research Operations",
"location": "AUSTIN, TX",
"country": "United States of America",
"employmentType": "FULL_TIME",
"postedAt": "2026-11-10",
"hiringEntity": "The University of Texas at Austin",
"requisitionId": "R_00049214",
"uid": "workday:utaustin:R_00049214"
}

Paste one or more Workday career site URLs, filter by keyword, location and date, and turn on only-new mode (onlyNewJobs) on scheduled runs for a clean feed of new jobs. No Workday login is needed.

At a glance

  • One row per open Workday job: title, company, location (plus the full location list), remote flag, posting date, job URL and apply link.
  • Also: requisition ID, hiring entity, country, employment type, salary range when the description states one, and the full description (text, HTML or both).
  • A Jobs table in the Output tab with company, title, location, posting date and URL, and export to JSON, CSV or Excel.
  • A stable uid per job for upserts, and only-new mode (onlyNewJobs) that returns only jobs you haven't seen before.
  • $0.002 per job, nothing for jobs your filters remove. The input form opens with a sample input (UT Austin's Workday staff jobs site, 4 jobs, $0.008), so you can press Start and see real rows before adding your own sites.

Who it's for

  • Job seekers and job-feed builders following large employers, many of which use Workday.
  • Recruiters and talent intelligence teams tracking requisitions at competitors or target accounts.
  • Sales and ABM teams turning new Workday requisitions into hiring signals.
  • Analysts studying hiring by location, team or legal entity at enterprise companies.

What data you get

One dataset item per job. The fields match our Greenhouse, Lever, Ashby and multi-ATS Actors, so their output can be combined.

FieldWhat it holds
idThe job's ID, normally the requisition ID, e.g. R_00049653.
atsAlways workday.
companySlugThe board slug as tenant/site, e.g. utaustin/UTstaff.
companyNameThe hiring entity without its leading company code, e.g. Example Corp for 2100 Example Corp; on UT Austin's site it is The University of Texas at Austin. Workday does not expose a display name. Null if the detail page could not be read. It is never the tenant slug.
titleJob title.
department, teamAlways null on Workday, whose public job API doesn't include them.
location, locations, countryMain location, all listed locations, and country when the ATS gives one.
isRemote, workplaceType, workplaceTypeRawRemote flag; Workday's remote type normalized to remote, hybrid, onsite or null (null for values such as Flexible); and Workday's own text.
employmentType, employmentTypeRawWorkday's time type normalized to FULL_TIME, PART_TIME, CONTRACTOR, TEMPORARY, INTERN, VOLUNTEER, PER_DIEM, OTHER (a value that fits none of them, such as Permanent) or null; and Workday's own text, e.g. Full time (detail page).
postedAt, updatedAtPosting date as YYYY-MM-DD (a calendar date, no time). updatedAt is always null on Workday.
url, applyUrlJob page and application link.
salaryMin, salaryMax, salaryCurrency, salaryPeriod, salaryTextPay range when present.
salaryAnnualMin, salaryAnnualMaxThe pay range as a yearly amount in the posting's own currency: hour × 2,080, day × 260, week × 52, month × 12. Null when there is no range or no pay period.
salaryAnnualUsdMin, salaryAnnualUsdMaxThe annual range in whole US dollars, converted with a fixed table of rough reference rates bundled with the Actor (not live rates). Null when there is no salary, no pay period, or the currency is not in the table.
salarySourceats when the ATS has a pay field, description when the range was parsed from the description text, otherwise null.
hiringEntity, requisitionIdLegal hiring entity (e.g. The University of Texas at Austin) and requisition ID, both from the detail page.
descriptionText / descriptionHtmlFull description in the format you choose.
uidStable key ats:slug:id, handy for upserts.
dedupeKeyHash of company, title and first location after removing case, accents and gender suffixes such as (m/f/d). Same recipe and values as the ATS Jobs Scraper's dedupeKey.
crossSourceKeyHash of company (legal form such as Inc or GmbH removed) and title, with no location. The same job found by the ATS Jobs Scraper or Remote Jobs Aggregator gets the same key. null when the company or title is missing.
scrapedAtWhen the run read the job.

Workday has no structured salary field, so pay comes only from ranges written in the description (salarySource: "description").

Sample item (real output; descriptionText removed to keep the page short):

{
"id": "R_00049653",
"ats": "workday",
"companySlug": "utaustin/UTstaff",
"companyName": "The University of Texas at Austin",
"title": "Senior Web Developer, Texas McCombs",
"department": null,
"team": null,
"location": "UT MAIN CAMPUS",
"locations": [
"UT MAIN CAMPUS"
],
"country": "United States of America",
"isRemote": false,
"workplaceType": null,
"employmentType": "FULL_TIME",
"postedAt": "2026-11-10",
"updatedAt": null,
"url": "https://utaustin.wd1.myworkdayjobs.com/UTstaff/job/UT-MAIN-CAMPUS/Senior-Web-Developer--Texas-McCombs_R_00049653",
"applyUrl": "https://utaustin.wd1.myworkdayjobs.com/UTstaff/job/UT-MAIN-CAMPUS/Senior-Web-Developer--Texas-McCombs_R_00049653/apply",
"salaryMin": null,
"salaryMax": null,
"salaryCurrency": null,
"salaryPeriod": null,
"salaryText": null,
"salarySource": null,
"hiringEntity": "The University of Texas at Austin",
"requisitionId": "R_00049653",
"workplaceTypeRaw": null,
"employmentTypeRaw": "Full time",
"uid": "workday:utaustin:R_00049653",
"salaryAnnualMin": null,
"salaryAnnualMax": null,
"salaryAnnualUsdMin": null,
"salaryAnnualUsdMax": null,
"scrapedAt": "2026-11-10T19:21:39.871855+00:00"
}

How far to trust the derived fields

  • salaryAnnualMin / salaryAnnualMax are the posted range turned into a yearly amount in the posting's own currency (hour x 2,080, day x 260, week x 52, month x 12). They are null when the posting gives no pay period.
  • USD conversion is approximate. salaryAnnualUsdMin / salaryAnnualUsdMax use fixed exchange rates bundled with the Actor, set in October 2026 (RATES_AS_OF in my_actor/fx.py). They are rough reference values, not live exchange rates, and they are not refreshed at run time, so treat the USD figures as salary bands, not exact amounts.
  • visaSponsorship, yearsExperienceMin / yearsExperienceMax, workArrangement and seniority (added while their filters are on) are heuristics read from the title and description with fixed patterns, not statements by the employer. Check the posting before relying on them.
  • The visa and years filters are off by default and slow runs down. visaSponsorship (default any) and maxYearsExperience (default empty) read each job's description, so while either is on the Actor fetches job details for every job, even with includeDescription off. Expect more requests and longer runs.
  • Invalid input fails at the start. A negative number, a minimum salary above the maximum, or an unknown option value stops the run before any request with a status message that lists every problem. Nothing is fetched or charged.

How to use it

  1. Open the company's careers site in a browser and copy the URL up to the site name, e.g. https://utaustin.wd1.myworkdayjobs.com/UTstaff. The tenant (utaustin), data center (wd1) and site name are read from it. Locale segments like /en-US are fine.
  2. Paste one URL per line in Workday career site URLs (up to 2,000 per run). Workday's other address form, https://wd5.myworkdaysite.com/recruiting/qvc/QRG, works too. A company careers page that links to its Workday site, or shows the Workday job search inside the page, also works; the Actor finds the Workday site on the page.
  3. Add filters. Title keywords are applied before the job detail pages are fetched, which saves requests on big sites.
  4. Click Start and export from the Output tab.

Only Workday sites are recognized: myworkdayjobs.com and myworkdaysite.com URLs, or a careers page that links to or embeds one. Workday does not offer custom domains for career sites. Every entry is read through the company's <company>.wdN.myworkdayjobs.com address, so job URLs in the output use that form and the company's robots.txt there decides which sites may be read. Other URLs, and bare company names such as utaustin, are skipped with a log message. If no entry can be read, the run fails with an error message that names each bad entry, instead of finishing with 0 jobs.

With no sites at all (for example an empty {} input), the run is a demo: it returns up to 4 sample jobs from https://utaustin.wd1.myworkdayjobs.com/UTstaff, charged at the normal per-job price (at most 4 job events), and stops after 50 seconds at the latest. The log says Demo mode: no boards/companies given, returning up to 4 sample jobs from https://utaustin.wd1.myworkdayjobs.com/UTstaff. The input form is prefilled with that site and Max jobs in total = 4. That sample input (only the demo site, with a job cap of 1 to 4 in Max jobs in total or Max jobs per company) runs as the same demo, so it also costs at most $0.008; the log then says Demo mode: prefilled sample input, returning up to 4 sample jobs from https://utaustin.wd1.myworkdayjobs.com/UTstaff. Replace the site, or clear or raise the cap, for a normal run.

If the demo site gives no job (Workday sometimes takes a single site offline for maintenance, answering HTTP 503), the demo tries other public sample sites in this order: https://ubc.wd10.myworkdayjobs.com/ubcstaffjobs, https://salesforce.wd12.myworkdayjobs.com/External_Career_Site, https://td.wd3.myworkdayjobs.com/TD_Bank_Careers. They share the same 4-job cap, price and 50-second limit. The status message and RUN_SUMMARY (demoBoard, demoFallbackUsed, demoFallbackReason, demoBoardsTried) say which site was used and why. These are only public sample sites; this Actor is not affiliated with Workday or with any of these employers. A run on your own sites never switches to a sample site.

Input fieldLabelNotes
companiesWorkday career site URLsOne site per line. Leave empty for the 4-job demo described above; the form is prefilled with the demo site.
keywordsTitle keywords (any)Keep jobs whose title contains at least one word (case-insensitive).
excludeKeywordsExclude title keywordsDrop jobs whose title contains any of these words, e.g. intern.
searchInDescriptionMatch keywords in description tooAlso match keywords against the description. Works with includeDescription on or off, because the detail page is always read.
locationsLocations (any)Keep jobs whose location contains one of these strings, e.g. London, United States, Remote.
remoteOnlyRemote jobs onlyKeep jobs marked remote by the ATS or with "remote" in the location.
postedWithinDaysPosted within last N days1–3650. Empty keeps all.
includeUndatedJobsKeep jobs without a posting dateDefault true. Applies when postedWithinDays is set.
hasSalaryOnly jobs with a salaryDefault false. Keeps only jobs that state a salary (any currency or period).
minAnnualSalaryUsdMinimum annual salary (USD)Keeps jobs whose salaryAnnualUsdMax (or only figure) is at least this. Jobs without a convertible salary are dropped unless includeJobsWithoutSalary is on.
maxAnnualSalaryUsdMaximum annual salary (USD)Keeps jobs whose salaryAnnualUsdMin (or only figure) is at most this.
includeJobsWithoutSalaryKeep jobs without a salaryDefault false. Under a USD bound, also keeps jobs whose salary is missing or cannot be converted. Dropped jobs are never charged; RUN_SUMMARY gets salaryJobsExcluded.
timeRangePosted within (fixed window)Optional: 1h, 24h, 7d, 30d or all. Replaces postedWithinDays when set; all turns the date limit off.
workArrangementWork arrangementremote / hybrid / onsite, derived from the ATS field, location and title. Jobs with no detectable arrangement are left out when set.
employmentTypesEmployment typeFULL_TIME, PART_TIME, CONTRACTOR, TEMPORARY, INTERN, PER_DIEM, VOLUNTEER, OTHER. Jobs with no type are left out when set.
senioritySeniorityintern … executive, derived from the title. Jobs whose title shows no level are left out when set.
visaSponsorshipVisa sponsorshipany (default, off), yes (description says sponsorship is offered) or not_no (drop jobs that say no sponsorship). Pattern-based, not a legal statement. Adds visaSponsorship / visaSponsorshipEvidence; fetches job details.
maxYearsExperienceMax years of experienceDrops jobs whose description asks for more years; jobs stating no number are kept. Adds yearsExperienceMin / yearsExperienceMax; fetches job details.
dedupeByRemove duplicate jobsDefault none. job drops a job with the same company, title and first location as one already output in this run. companyTitle merges a company's jobs with the same title into one record (locations holds all their locations; duplicateCount and mergedUids are added). Duplicates are removed before the dataset push, so they are never charged; RUN_SUMMARY gets duplicatesDropped. Only duplicates within one run are handled.
onlyNewJobsOnly new jobsReturn only jobs not returned by an earlier run with this option on. Default false. Needs a usable state store (stateStoreName); if it cannot be opened, every matching job is returned and charged on each run.
stateStoreNameState store nameNamed key-value store for only-new state. Use one name per scheduled feed. Default workday-jobs-scraper-state.
includeExpiredReport expired jobsDefault false. On scheduled runs, adds a free record with status: "expired" for each job an earlier run returned that its career site no longer lists. Only sites read completely in this run are checked. While on, job records get status: "active". Uses the state store.
includeDescriptionInclude descriptionDefault true. Workday detail pages are always read, so locations, requisition ID and company come back filled in. This setting only controls whether the description text is included.
descriptionFormatDescription formattext (default), html or both.
redactContactsRemove contact details from descriptionsOn by default. Personal e-mail addresses (shared mailboxes such as jobs@ or careers@ stay), phone numbers with 8 or more digits and 'Recruiter:
maxJobsPerCompanyMax jobs per company0 = no limit (default).
maxTotalJobsMax jobs in total0 = no limit (default). The run also stops at your maximum cost per run. The form is prefilled with 4 for the sample run.
maxConcurrencyCompanies in parallel1–20, default 5. Requests to each host are rate limited regardless.

Example input:

{
"companies": [
"https://utaustin.wd1.myworkdayjobs.com/UTstaff"
],
"keywords": [
"software",
"engineer"
],
"locations": [
"United States",
"Remote"
],
"onlyNewJobs": true
}

Input examples

Each of these was run locally on November 10, 2026; the job counts are what those runs returned.

Example 1: One company. This is the prefilled sample input, so it runs as the demo described above: at most 4 jobs, $0.008. It returned 4 jobs.

{
"companies": [
"https://utaustin.wd1.myworkdayjobs.com/UTstaff"
],
"maxTotalJobs": 4
}

Example 2: Several career sites, up to 3 jobs from each. It returned 6 jobs ($0.012).

{
"companies": [
"https://utaustin.wd1.myworkdayjobs.com/UTstaff",
"https://wd5.myworkdaysite.com/recruiting/qvc/QRG"
],
"maxJobsPerCompany": 3
}

Example 3: Filter by title keyword and location (software or engineer jobs in the United States or remote, at most 5 in total). It returned 5 jobs ($0.010).

{
"companies": [
"https://utaustin.wd1.myworkdayjobs.com/UTstaff"
],
"keywords": [
"software",
"engineer"
],
"locations": [
"United States",
"Remote"
],
"maxTotalJobs": 5
}

Set maxTotalJobs and maxJobsPerCompany to 0 (no limit) to get every matching job.

Output of example 1: the first item from that run, with descriptionText shortened for this page.

{
"id": "R_00049214",
"ats": "workday",
"companySlug": "utaustin/UTstaff",
"companyName": "The University of Texas at Austin",
"title": "Manager, Clinical Research Operations",
"department": null,
"team": null,
"location": "AUSTIN, TX",
"locations": [
"AUSTIN, TX"
],
"country": "United States of America",
"isRemote": false,
"workplaceType": null,
"employmentType": "FULL_TIME",
"postedAt": "2026-11-10",
"updatedAt": null,
"url": "https://utaustin.wd1.myworkdayjobs.com/UTstaff/job/AUSTIN-TX/Manager--Clinical-Research-Financial-Operations_R_00049214",
"applyUrl": "https://utaustin.wd1.myworkdayjobs.com/UTstaff/job/AUSTIN-TX/Manager--Clinical-Research-Financial-Operations_R_00049214/apply",
"salaryMin": null,
"salaryMax": null,
"salaryCurrency": null,
"salaryPeriod": null,
"salaryText": null,
"salarySource": null,
"hiringEntity": "The University of Texas at Austin",
"requisitionId": "R_00049214",
"descriptionText": "Job Posting Title:\nManager, Clinical Research Operations----\nHiring Department:\nDell Medical School---- …",
"workplaceTypeRaw": null,
"employmentTypeRaw": "Full time",
"uid": "workday:utaustin:R_00049214",
"salaryAnnualMin": null,
"salaryAnnualMax": null,
"salaryAnnualUsdMin": null,
"salaryAnnualUsdMax": null,
"scrapedAt": "2026-11-10T19:21:39.871855+00:00"
}

After each run, the default key-value store holds RUN_SUMMARY: jobs pushed, HTTP requests, stoppedByCostLimit, and one entry per board with found, matched, pushed, skippedSeen and status. status is ok, partial (a Workday site where some jobs past the 2,000-row cap could not be reached; partialReason says why), skipped or error. A Workday entry also gets pathlessSkipped when the site listed jobs with no job page; those are skipped and not charged.

Expired jobs (includeExpired): each run remembers the jobs it returned per site (key <site>-live in the state store). When a later run reads the whole site and a remembered job is no longer listed, it adds one record with status: "expired", uid, id, title, url, companyName, lastSeenAt and expiredDetectedAt. These records are not charged (no job event), and the Expired jobs dataset view lists them. A site counts as read completely only when nothing cut the read short: not maxJobsPerCompany, maxTotalJobs, the maximum cost per run or an abort, and not rows past the 2,000-row cap that facet splits could not reach. Jobs hidden by your filters still count as listed, so changing filters never reports jobs as expired. A job that comes back after it expired is returned as new. RUN_SUMMARY gets expiredRecords, and each site entry gets expired and complete.

Posting dates: postedAt is a date (YYYY-MM-DD). When Workday shows an exact label such as "Posted Today" or "Posted 3 Days Ago", the date is counted on the US Eastern calendar. For "Posted 30+ Days Ago" the posting start date from the detail page is used. The detail page is read for every job whatever includeDescription is set to, so employmentType, country, requisitionId, hiringEntity and the full location list are filled in either way.

Run it on a schedule

Workday career sites add and close postings every day. Run this Actor on a schedule with Only new jobs on and each run returns only postings you haven't had yet, so you pay once per job.

  1. Save your input as a task, or duplicate one of the ready-made tasks on this Actor's Example tasks tab.
  2. In Apify Console, open Schedules, create a schedule, add the task and set the cron and your time zone.
  3. Turn on Only new jobs (onlyNewJobs) and set Posted within last N days a little wider than the gap between runs, for example 2 for a daily run.
  4. State is kept in the named key-value store in stateStoreName (default workday-jobs-scraper-state). Use a different name for each independent feed, for example one-employer-daily and university-it-weekdays.
  5. Replace the prefilled sample board and raise Max jobs in total (maxTotalJobs): the prefilled value of 4 is a demo cap. Set a Maximum cost per run in the task's run options. Each job costs $0.002, so maxTotalJobs: 50 keeps a run at $0.10 or less.
Use caseKey inputSuggested cron
New jobs at one Workday employercompanies: [one career-site address], postedWithinDays: 2, maxTotalJobs: 500 7 * * * (daily, 7 AM)
New jobs by keyword across several Workday sitescompanies: [2 career-site addresses], keywords: ["software", "data", "cyber"], postedWithinDays: 7, maxTotalJobs: 500 7 * * 1-5 (weekdays, 7 AM)
New remote jobs at a list of employerscompanies: [...], remoteOnly: true0 7 * * *

The first run returns every matching job in the window. Later runs return only new ones.

Send the results on. Works with Apify's native n8n, Make and Zapier integrations: start the task from your automation tool or let the Apify schedule run it, then read the run's default dataset in the next step. A webhook on "run succeeded" can also call your own endpoint with the run ID, and the Apify API returns the items as JSON, CSV or Excel.

Chain with other jobs Actors

This Actor is one of four jobs Actors that share one job format and one set of keys (ATS Jobs Scraper, Career Site Jobs Feed, Remote Jobs Aggregator). You can pass the dataset of a run of any of them in datasetId; this run then skips the jobs that are already there. All four inputs below are optional and off by default: without them a run behaves exactly as before.

InputDefaultWhat it does
datasetIdemptyID of a dataset from an earlier run (this Actor or another jobs Actor). Its job items are read before any board. For an Apify integration, put {{resource.defaultDatasetId}} here. When empty and the run was started by an Apify integration, the integration payload's resource.defaultDatasetId is tried.
datasetModemergemerge: the earlier jobs are copied into this run's dataset first (free, no job event), then the new jobs follow, so the dataset is the combined, deduplicated list. exclude: nothing is copied; the dataset has only the new jobs.
datasetMatchByuiduid: a job counts as already there when the same posting (same uid) is in the earlier dataset. uidOrCrossKey: also when the same company and title (crossSourceKey) is there from any source; this can merge one title posted in several cities.
suiteOutputfalsetrue: every job item has all fields of the shared format in the shared order (missing ones null or []). Values are not changed. Jobs copied from datasetId are kept as they were.
  • A job that is already in the earlier dataset is dropped before it is pushed, so it is never charged. Only new jobs are charged (one job event each, same price as today) and only new jobs count toward maxTotalJobs.
  • Status items and expired or unresolved records in the earlier dataset are not copied. At most 100,000 items are read.
  • datasetId asks Apify for read-only access to that one dataset, so chaining works with this Actor's limited permissions; the run gets no access to your other storages. Only a dataset given in datasetId is granted this way, so the payload fallback may not be readable; give the dataset in datasetId.
  • If the dataset cannot be read, or datasetMode or datasetMatchBy has an unknown value, the run fails with an input error before any board is read (as for other invalid input).
  • onlyNewJobs and its state (workday-jobs-scraper-state) work as before and are applied too.
  • The run summary (RUN_SUMMARY in the key-value store) gets a previousDataset block with the counts read, copied and skipped.

Pricing

This Actor uses pay-per-event pricing: $0.002 per job written to the dataset. That is $2.00 per 1,000 jobs. There is no separate start fee in this Actor's pricing (as listed on October 28, 2026; the Pricing tab on the Store page is the source of truth).

You are charged only for jobs that end up in your dataset. Jobs removed by your filters, jobs skipped in only-new mode and duplicates are not charged.

ExampleJobsCost
One employer, filtered to a team200$0.40
One large employer, no filters (illustration)2,000$4.00
Ten employers, filtered1,000$2.00

Rows are illustrations, not measured site sizes. Use maxTotalJobs or a maximum cost per run for a hard ceiling.

Worked example: 1,000 jobs × $0.002 = $2.00.

Sample run: the prefilled input and an empty {} input both return at most 4 jobs, so they cost at most 4 × $0.002 = $0.008.

To cap spend, set Maximum cost per run in the run options (or maxTotalChargeUsd via the API). The Actor stops cleanly when the next job would go over the limit and records stoppedByCostLimit: true in the run summary.

How it compares

What this Actor is built for:

  • Any Workday career site by URL (myworkdayjobs.com, myworkdaysite.com or a careers page that embeds one).
  • Title filters applied before detail requests, so filtered-out jobs cost nothing.
  • Only-new-jobs mode for scheduled runs.
  • The same schema as our other ATS Actors.

If your target list mixes Workday with Greenhouse, Lever, Ashby, Workable or Recruitee, our ATS Jobs Scraper covers all of them in one run at the same price per job.

Integrations and API

The actor ID is fecklesspleb/workday-jobs-scraper (in API URLs: fecklesspleb~workday-jobs-scraper).

n8n, Make and Zapier. Each has an Apify integration with a "run Actor" action. Pick fecklesspleb/workday-jobs-scraper, paste the input JSON shown below, then read the results from the run's default dataset in the next step. To process only new jobs on a schedule, turn on Only new jobs and run it from a schedule (Apify Schedules or a trigger in your automation tool).

Example flow. Works with Apify's native n8n, Make and Zapier integrations. A common setup: run the Actor on a daily schedule with only-new-jobs on, add each new job as a row in Google Sheets, and post one Slack message listing them.

Webhooks and schedules. Apify Schedules can run the Actor on a cron, and a webhook on "run succeeded" can call your own endpoint with the run ID.

HTTP API. Run the Actor and get the items back in one call. This waits for the run to finish, so use it for small runs:

APIFY_API="https://api.apify.com/v2/actors"
curl -X POST "$APIFY_API/fecklesspleb~workday-jobs-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"companies": ["https://utaustin.wd1.myworkdayjobs.com/UTstaff"], "keywords": ["software", "engineer"], "locations": ["United States", "Remote"], "onlyNewJobs": true}'

Python (pip install apify-client):

from decimal import Decimal
from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("fecklesspleb/workday-jobs-scraper").call(
run_input={
"companies": [
"https://utaustin.wd1.myworkdayjobs.com/UTstaff"
],
"keywords": [
"software",
"engineer"
],
"locations": [
"United States",
"Remote"
],
"onlyNewJobs": True
},
max_total_charge_usd=Decimal("5"), # optional spend cap
)
# apify-client 3.x returns a Run object; on 1.x/2.x use run["defaultDatasetId"]
for item in client.dataset(run.default_dataset_id).iterate_items():
print(item)

JavaScript / Node.js (npm install apify-client):

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fecklesspleb/workday-jobs-scraper').call(
{
"companies": [
"https://utaustin.wd1.myworkdayjobs.com/UTstaff"
],
"keywords": [
"software",
"engineer"
],
"locations": [
"United States",
"Remote"
],
"onlyNewJobs": true
},
{ maxTotalChargeUsd: 5 }, // optional spend cap
);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Results can also be exported from the dataset as JSON, CSV, Excel, XML or RSS from the Apify Console or the dataset API.

Responsible use

The Actor reads only public career pages and job endpoints, logged out, and only where the site's robots.txt allows it. Entries that robots.txt blocks are skipped and noted in the log. Some employers' own website terms restrict automated access, so you are responsible for checking the terms of the sites you target and for how you use the data.

If a site's robots.txt can't be read, that site is skipped with a warning in the log.

FAQ

Which dataset rows are free? Every job row costs $0.002. Other rows are free (no job event is charged): the one {"type": "status", "status": "warning", ...} row written when the demo, or a run stopped by its time limit, ends without any job row, and the status: "expired" rows that includeExpired adds. Job rows have no type field and no status field (with includeExpired on, they get status: "active"), so keep rows without status, or with status: "active", if you only want jobs.

What happens if the sample site in the demo is down or slow? The run still ends SUCCEEDED. Each request has a 10 s timeout in the demo (40 s otherwise) and only a couple of retries, and no new request is started about 40 s into the demo or 20 s before the run's timeout. If the sample site gives no job, the other sample sites are tried in turn (see Demo mode above). If none of them gives a job, the dataset gets one free record such as {"type": "status", "status": "warning", "message": "...", "source": "..."} with the reason, and the details are in RUN_SUMMARY. This record is not charged; filter on type if you only want data rows. A run on your own sites where every site fails still ends FAILED, so a wrong URL is easy to spot.

How do I find a company's Workday URL? Go to the company's careers page and click through to the job search. If the address looks like https://<company>.wd1.myworkdayjobs.com/<SiteName> or https://wd1.myworkdaysite.com/recruiting/<company>/<SiteName>, copy it up to the site name. Some companies have more than one site (for example internal and external); use the external one.

Can I just type the company name? No. This Actor needs the career site URL, because the tenant, data center and site name are all part of it. A bare name is skipped with a message.

Why are Workday runs slower than other job boards? Workday's job list leaves out the description, hiring entity, country, employment type and full location list, so the Actor reads each job's detail page as well. This happens whether includeDescription is on or off, so turning it off makes the output smaller but not the run faster. To cut the number of detail requests, use title keywords or excludeKeywords, which are applied before the detail pages are read.

Does Workday show salary? Not as a structured field. When a description contains a pay range, it is parsed into salaryMin/salaryMax with salarySource: "description".

Do I need a login, cookies or an API key from the ATS? No. The Actor reads the public job board endpoints that the career pages themselves use. You only need an Apify account to run it. It obeys robots.txt and rate-limits requests per host.

How do I get only new jobs every day? Turn on onlyNewJobs and schedule the Actor. The first run returns everything that matches and remembers it. Later runs return only jobs that were not returned before, and you are charged only for those. Each run refreshes the jobs it still finds, so a job that stays listed is never returned twice; a job is forgotten after 120 days in which no run saw it. The state is kept in the named key-value store set by stateStoreName. Use a different store name for each independent scheduled feed. If the state store cannot be opened (for example an invalid stateStoreName, another account's store or missing permissions), the run still finishes but logs a warning, sets stateStoreUnavailable: true in RUN_SUMMARY and saves nothing. onlyNewJobs then cannot remember earlier jobs, so every matching job is returned and charged again on each run until the store works.

Why does a job have no salary? Many companies don't publish pay. When the ATS has a pay field the Actor uses it (salarySource: "ats"). Otherwise it looks for a range in the description text (salarySource: "description"). This works even with includeDescription off, because the description is always read from the detail page. Check salaryPeriod before comparing numbers, because some ranges are hourly or monthly.

What happens if a company slug is wrong or a board is closed? That entry is skipped with a warning in the log, and the rest of the run continues. You are not charged for it. If every entry fails (for example, you entered only bare company names), the run fails with an error that lists them.

Can I export to CSV or Google Sheets? Yes. Every run's dataset can be downloaded as CSV, Excel or JSON, and the Apify integrations for n8n, Make and Zapier can push rows to Google Sheets, Airtable, Slack and others.

Is this an API from the ATS vendor? No. It is an independent Actor that reads public job postings. It is not affiliated with or endorsed by the ATS vendors.