Workday Jobs Scraper — Public Career Boards
Pricing
from $5.00 / 1,000 workday job record scrapeds
Workday Jobs Scraper — Public Career Boards
Extract public Workday jobs, descriptions, locations, and apply URLs from company career boards for recruiting and hiring research.
Pricing
from $5.00 / 1,000 workday job record scrapeds
Rating
0.0
(0)
Developer
Khadin Akbar
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
14 days ago
Last modified
Categories
Features
Share
Workday Jobs Scraper
Collect public Workday job postings from company career boards as structured JSON. Supply a public myworkdayjobs.com board URL, choose a result limit and optionally include full public descriptions. Use the Apify API to feed recruiting research, hiring dashboards or job datasets.
What it extracts
Each saved record contains jobId, title, companyTenant, companyName, location, additionalLocations, timeType, workerType, remoteType, jobFamilyGroup, jobProfile, description, postedAt, postedText, jobUrl, applyUrl, sourceUrl and scrapedAt. Fields absent from the public source are null or an empty array. Posting dates derived from relative text are approximate; ambiguous ages such as “30+ days” remain in postedText without an invented date.
How to use it
- Paste one or more public Workday career-board URLs into Workday career-site URLs.
- Enter optional job keywords. Leave search text blank to list available roles.
- Set a result limit, from 1 to 500 jobs per board.
- Enable public job details for descriptions and employment metadata.
- Start the Actor and inspect the dataset and run summary.
{"careerSiteUrls": ["https://baincapital.wd1.myworkdayjobs.com/External_Public"],"searchText": "analyst","maxResultsPerSite": 25,"includeJobDetails": true,"useApifyProxy": true}
Up to 25 distinct boards are accepted. The input can be a board URL, a locale-prefixed public URL, a job-page URL on that board, or its matching CXS base. It must include the site name. Use canonical public board addresses without query strings, embedded credentials or custom ports. Company-name discovery and myworkdaysite.com/recruiting/... are outside this Actor's input contract.
Output and exports
Illustrative complete record shape; optional fields vary by posting:
{"jobId": "REQ_108236","title": "Senior Application Support Engineer","companyName": null,"companyTenant": "baincapital","location": "Boston","additionalLocations": [],"timeType": null,"workerType": null,"remoteType": null,"jobFamilyGroup": null,"jobProfile": null,"postedAt": null,"postedText": null,"description": "Public job description text appears here.","jobUrl": "https://baincapital.wd1.myworkdayjobs.com/External_Public/job/Boston/Senior-Application-Support-Engineer_REQ_108236-11","applyUrl": null,"sourceUrl": "https://baincapital.wd1.myworkdayjobs.com/wday/cxs/baincapital/External_Public/job/Boston/Senior-Application-Support-Engineer_REQ_108236-11","scrapedAt": "2026-11-02T00:00:00.000Z"}
The example shows every output field. Description text and collection time are illustrative. Download the dataset as JSON, CSV, Excel or other supported Apify export formats. OUTPUT contains the terminal outcome and acknowledged result/event counts. RUN_SUMMARY adds source-completion proof, board diagnostics, detail diagnostics and transport diagnostics.
A successfully completed search with no matching roles returns VALID_EMPTY. If every required board route is unavailable, the execution ends with UPSTREAM_FAILED. Valid jobs collected before a later board or pagination interruption remain available with PARTIAL. An unavailable optional detail response preserves the listing fields and reports PARTIAL rather than claiming a complete description.
API access
Send this input as JSON to POST /v2/actors/khadinakbar~workday-jobs-scraper/run-sync-get-dataset-items with your Apify bearer token in the Authorization header. Set the run's maxTotalChargeUsd and timeout explicitly. The response contains dataset rows. For longer work, start an asynchronous run, retain its run ID, check its status, then paginate its default dataset.
A network timeout may leave a run active. Check the original run before starting another one. Reconcile the original execution after an ambiguous HTTP response.
Pricing
This Actor uses Pay per event pricing for each acknowledged saved job, plus caller-paid Apify platform usage. Check the live Pricing tab for effective event prices, plan tiers and start fees. Apify charges the synthetic start event according to run memory, with a minimum of one unit. Compute, storage, transfer and optional residential proxy traffic add platform usage. Set an explicit run charge limit before starting collection.
Job events apply to acknowledged saved records. Rejected records and genuinely empty results generate zero job events. The start event and platform usage may still apply to empty, invalid or unsuccessful runs. The Actor reads Apify's effective event prices and accepted named-event counters; it stops collecting new work when the remaining charge limit is below one job event. The result limit is applied separately to each board.
Limits and request handling
Requests use direct public HTTP first. useApifyProxy: true permits an optional residential fallback after a transport interruption; a working direct route keeps proxy traffic at zero. false keeps direct access only. Explicit access denials end the affected request. Rate-limit retries honor Retry-After and stop if it exceeds the execution deadline.
The scraper bounds response bytes, request attempts, proxy attempts and extraction time. It stops source work after four minutes, or earlier to reserve time for finalization before the configured run timeout. Larger multi-board jobs can return partial results; narrow the board list or keyword query and inspect RUN_SUMMARY. The maximum of 500 requested records is a cap, not a completeness guarantee for large or changing boards. Repeated pages stop pagination instead of generating duplicates.
Dataset writes and charges are not an atomic transaction. A durable pending-effect record prevents automatic replay after an uncertain write or charge. Interrupted executions requiring reconciliation return a terminal diagnostic before another collection or charge attempt. Completed execution checkpoints return the recorded result without repeating collection. Start/platform charges imposed by Apify on a new start or resurrection are separate.
Data use, support and independence
This Actor reads public job postings only. It does not sign in, access applicant or employee records, or submit applications. Job descriptions can contain public contact details; only collect and retain data you are authorized to use and follow the target employer's site terms and applicable laws. Your run stores output in its Apify dataset and key-value store; manage retention and access using your Apify account settings. Supply public, credential-free career-site URLs and ordinary job keywords.
For issues, provide the run ID and a public board URL through this Actor's Apify Issues tab; never share passwords or tokens.
Workday is a trademark of its owner. This independent Actor is not affiliated with, associated with, or endorsed by Workday.
From employer boards to a hiring decision
A recruiter starts with an employer's Workday board and a role keyword. The Actor returns titles, locations, job descriptions and public source URLs. The recruiter then exports the dataset, compares the hiring mix by location and follows the posting URL for the latest employer details. An analyst can feed the same structured fields into a recruiting dashboard and retain scrapedAt for freshness comparisons.
| Field group | How to use it |
|---|---|
jobId, title | Identify a vacancy and its role |
companyTenant, companyName | Group results by employer |
location, additionalLocations | Compare hiring locations |
description, timeType, remoteType | Review duties and working arrangements |
postedAt, postedText | Interpret posting age without assuming exact dates |
jobUrl, applyUrl | Continue to the employer's public posting |
sourceUrl, scrapedAt | Retain provenance and collection time |
Best results and scope
Use this Actor when you already have a public employer board on myworkdayjobs.com. Start with a focused keyword query and a small result cap, then expand after reviewing the dataset. Public job-page and locale-prefixed links resolve to their containing board; the output follows the board search and keyword filters. Use a matching CXS tenant and site when supplying an API-base address.
For a large board, split collection into focused queries and inspect RUN_SUMMARY before combining outputs. Pagination proceeds by the number of listings actually received and stops when the source repeats a page. Each record carries its public source URL and collection time. Board changes during collection can affect the resulting snapshot.
Focused standalone workflow
This Actor works as a focused standalone workflow for collecting jobs from known Workday employer boards. Continue with an Apify dataset export or your own recruiting dashboard once you have reviewed the source URLs and collection times.
Copy-paste API example
Set your own APIFY_TOKEN environment variable before sending this request:
curl --fail-with-body --max-time 200 \--request POST \'https://api.apify.com/v2/actors/khadinakbar~workday-jobs-scraper/run-sync-get-dataset-items?timeout=180&maxTotalChargeUsd=0.20' \--header "Authorization: Bearer ${APIFY_TOKEN}" \--header 'Content-Type: application/json' \--data '{"careerSiteUrls":["https://baincapital.wd1.myworkdayjobs.com/External_Public"],"searchText":"analyst","maxResultsPerSite":5,"includeJobDetails":true,"useApifyProxy":true}'
The request starts a paid execution when sent. The charge cap controls event exposure; inspect the live Pricing tab and platform usage for the actual cost of your selected workflow.
AI agent workflow
An AI agent with authorized Apify API access can use this request contract:
Collect analyst roles from the supplied public Workday board with a small result cap and full job details. Inspect the terminal outcome and complete dataset, then return titles, locations, public posting URLs and collection times. Report partial or empty results accurately and check the original execution before retrying an ambiguous timeout.
Builder's note
In my testing, Workday's search response exposed location text separately from requisition identifiers. I designed the listing parser to retain that location text and the detail parser to add descriptions when available. Page-by-page persistence also keeps accepted earlier records useful when a later request is interrupted. The run summary exposes both useful data and source completeness so downstream workflows can decide whether to continue collection.
Guarded Workday MCP connector
Use the guarded connector when you need malformed inputs refused before a paid cloud run starts. It preserves the documented URL, 1–500 result, 25-board and 160-character search limits and checks original JSON types without coercion. The connector adds no event fee; normal Actor startup, job and platform charges apply.
- Download workday-mcp.mjs and verify its SHA-256 before running it:
76ac9fa1aeefa01125a6070e98071bcb7b428999d7418bbc9ab1b69d519a6f91
- Use Node.js 22 or later. Add this stdio server to your MCP client, replacing the file path and supplying your own Apify token through its secure environment configuration:
{"mcpServers": {"workday-jobs": {"command": "node","args": ["/absolute/path/workday-mcp.mjs"],"env": { "APIFY_TOKEN": "YOUR_APIFY_TOKEN" }}}}
- Call
workday_jobswith a stable request ID and explicit limits for your work:
{"requestId": "nvidia-job-check-001","input": {"careerSiteUrls": ["https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"],"maxResultsPerSite": 1,"includeJobDetails": true,"useApifyProxy": false},"runOptions": { "memory": 512, "timeout": 90, "maxTotalChargeUsd": 0.00505 }}
- Read the returned run with
workday_run, then useworkday_resultswith its run ID. Results supportoffsetandlimit(1–100 per read). Inspect the terminal OUTPUT outcome: COMPLETE, PARTIAL, VALID_EMPTY, INVALID_INPUT or a failed source/configuration outcome. Null source fields are preserved.
The default connector event cap is $0.13, memory is 512 MB and timeout is 280 seconds. Event caps exclude platform usage. Explicitly raise the event cap when your requested work needs more. A cap that cannot buy startup plus one job is refused before a start.
Keep the same request ID when recovering a connection interruption. Durable receipts under ~/.apify/workday-mcp return the original run instead of starting another one. Use a new ID for intentionally changed work. If the start outcome or a lock is uncertain, reconcile the existing request in Apify before starting more work; do not delete its receipt and replay it. This is a local, per-account guard, not distributed exactly-once delivery. The connector reads only this account's Workday runs. It stores no token or raw job input in its receipts.
The connector supports stdio MCP revision 2025-11-25 and is tested with the official MCP JavaScript SDK. Individual Codex/Claude desktop application configurations require their own installation check.
Hosted Apify MCP alternative
The hosted call-actor workflow remains available for clients that already enforce input validity. Pass Actor khadinakbar/workday-jobs-scraper, complete input and separate callOptions for fee, memory and timeout caps. Read the returned run and Dataset with get-actor-run and get-dataset-items; read OUTPUT using get-key-value-store-record.
The shared hosted service currently drops some numeric/array bounds and may coerce types. The Actor's explicit URL-item pattern protects malformed URLs, while the guarded connector enforces the full contract before starting work. A plain hosted direct Actor call does not provide that complete preflight guarantee. Startup/platform charges can apply to invalid requests that reach a container. Repeating an ordinary hosted call-actor can start and bill another run.
Free Apify plan
The Actor uses the same public-job fields, details, pagination and runtime limits across account plans. Apify determines account eligibility, available credits and applicable fees. Independent non-owner FREE-account execution has not yet been verified; owner tests do not establish FREE-account acceptance.