Workday Jobs Feed: every posting from any Workday career site | $1.50/1K

Quick start

• Workday jobs scraper alternative: one JSON row per open job on every Workday career site you list, with title, location, apply URL and a stable id, read from the site's own JSON instead of its HTML.
• Minimal input: {"boards": ["workday:adobe.wd5/external_experienced"]}
• Run it from the Console, the API, or the Apify MCP server; export JSON, CSV or Excel.

Pull live job openings from Workday career boards into one clean JSON dataset, read through the career site's own CXS jobs JSON (public, paginated). No HTML scraping, no login, no proxies, no API key.

Pass board slugs (workday:adobe.wd5/external_experienced) or just paste the careers URL (<tenant>.<wdN>.myworkdayjobs.com/<site>). You get one row per job: title, location, apply URL, stable id.

Raw board data, nine normalized fields, no enrichment; cheaper than multi-ATS and enrichment feeds. This Actor accepts only Workday boards (workday:<slug> or a pasted Workday URL). Entries for other platforms are returned as one error row each and skipped. For a mixed list across six ATS platforms use ats-jobs-feed ($2 per 1,000).

Why this instead of scraping or the vendor API

• Workday career sites are JavaScript apps. The job list comes from https://<tenant>.<wdN>.myworkdayjobs.com/wday/cxs/<tenant>/<site>/jobs, a POST endpoint the page itself calls. This Actor calls it directly and pages through it 20 postings at a time.
• No key, no tenant credentials. The CXS endpoint is public. Workday's REST and SOAP APIs need a customer account and are not needed here.
• Pasted URLs work, including localized ones. https://<tenant>.<wdN>.myworkdayjobs.com/<site> and https://<tenant>.<wdN>.myworkdayjobs.com/en-US/<site> are turned into workday:<tenant>.<wdN>/<site>.
• Same nine-column schema as the other CleanFeeds ATS feeds, so rows from this Actor and ats-jobs-feed fit one table.
• Postings without a title or URL are dropped before charging, so a malformed entry never costs you a row.

Input example

{"boards": ["workday:adobe.wd5/external_experienced", "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"], "maxJobsPerBoard": 0}

Field	Type	Default	Notes
boards	string list	two sample Workday boards	workday:<tenant>.<wdN>/<site> or a Workday careers URL
maxJobsPerBoard	integer	500	0 = everything the endpoint returns (Workday serves at most 2,000 postings per site query; the reader stops when a page repeats)

Filters are applied before billing

postedAfter (ISO date or 24h / 7d), titleIncludes (keep if the title contains any term) and titleExcludes (drop if it contains any term) are applied to the rows read from the ATS before the pay-per-event charge, so you never pay for jobs you filtered out. Matching is case-insensitive substring; there is no fuzzy or AI matching, so what you see is what was matched. Dates come from the ATS itself (first_published, createdAt, publishedAt, releasedDate, published_at), not from when we indexed the job; Workday only publishes "Posted N Days Ago", so its posted_at has day precision and "30+ days ago" postings have no date and are excluded when postedAfter is set.

{ "boards": ["greenhouse:stripe", "lever:spotify"], "postedAfter": "24h", "titleIncludes": ["engineer", "developer"], "titleExcludes": ["intern", "staffing"] }

Output example

{ "source": "workday", "company": "adobe.wd5/external_experienced", "title": "Software Engineer", "location": "San Jose, CA",
  "department": null, "url": "https://adobe.wd5.myworkdayjobs.com/external_experienced/job/San-Jose/Software-Engineer_R123456", "posted_at": null, "updated_at": null, "id": "R123456" }

Field	Meaning
source	always workday
company	the slug you passed
title, location	as the career site reports them (locationsText)
department	always null for Workday; the list payload does not carry it
url	public job page, built from the site origin and the posting's externalPath
posted_at, updated_at	null for Workday. The list payload only has a relative "Posted 3 days ago" text, which the Actor does not turn into a guessed date
id	requisition id from the posting's first bullet field (falls back to externalPath), stable across runs, diff it to detect new and closed roles

A board that fails (bad slug, HTTP error) yields one row with error and the other boards continue.

How much does it cost?

Pay per event: $1.50 per 1,000 job rows plus Apify's small Actor-start event. Compute is included. Set a maximum charge per run in the Console and the Actor stops at the limit. The Apify free plan is enough to try it on the sample boards.

Use cases

• Recruiting SaaS and talent CRMs: nightly sync of target accounts' Workday boards.
• Hiring-intent signals: diff today's ids against yesterday's dataset.
• AI agents and MCP: "list open roles at these companies" through the Apify MCP server.
• Market maps: location mix per company over time.

Integrations

• Apify API: POST https://api.apify.com/v2/acts/cleanfeedsapi~workday-jobs-feed/run-sync-get-dataset-items?token=<APIFY_TOKEN> with the input JSON as the body. The response is the dataset, ready to parse.
• Scheduling: open the Actor in the Apify Console, click Schedule, pick a cron (for example daily at 06:00) and the saved input runs on its own. Each run keeps its own dataset.
• n8n, Make, Zapier: use the Apify integration in each tool, choose this Actor and pass the same input JSON. No per-Actor setup, no custom code.
• Apify MCP server for AI agents: connect the Apify MCP server to Claude, Cursor or any MCP client and ask the agent to run cleanfeedsapi/workday-jobs-feed with these inputs.

Related Actors by CleanFeeds

• ats-jobs-feed: all six ATS platforms in one Actor, same schema.
• greenhouse-jobs-feed: Greenhouse boards via the official Job Board API.
• lever-jobs-feed: Lever postings via api.lever.co.
• ashby-jobs-feed: Ashby job boards via the posting API.
• remote-jobs-feed: RemoteOK and Arbeitnow remote listings in one schema.

Free sample dataset: cleanfeeds/tech-jobs-daily on Hugging Face. More feeds at cleanfeeds.dev.

FAQ

Do I need a Workday API key? No. The endpoint is public and unauthenticated.

Is this HTML scraping? No. It reads the career site's own CXS jobs JSON (public, paginated), the same data the careers page itself loads.

Where do I find the slug? Take the careers URL https://adobe.wd5.myworkdayjobs.com/external_experienced: tenant adobe, data center wd5, site external_experienced, so workday:adobe.wd5/external_experienced. Or paste the URL itself.

Can I mix ATS platforms in one run? No. This Actor accepts only Workday boards (workday:<slug> or a pasted Workday URL). Entries for other platforms are returned as one error row each and skipped. For a mixed list across six ATS platforms use ats-jobs-feed ($2 per 1,000).

Why is maxJobsPerBoard 500 by default here? Large Workday tenants publish thousands of postings and the endpoint returns 20 per request. The default keeps an empty-input run short. Set 0 to read everything the endpoint serves, which is at most 2,000 postings per site: past that offset Workday returns the last page again, so the reader stops when a page repeats. Tenants with more open roles need several runs with different career-site URLs (regional sites) or a search facet, which this Actor does not do.

How do I detect new and closed items between runs? id is the Workday requisition id (for example R123456) and does not change between runs. Keep each run's dataset and compare id sets per company: ids present today but not yesterday are new roles, ids present yesterday but not today are closed. Schedule the Actor daily and the diff is a few lines in n8n, Make or a script.

What happens when a source fails? A site that returns an HTTP error, a slug that does not match tenant.wdN/site, or an unrecognized URL does not stop the run. The Actor logs the failure, pushes one row with source, company and error (the message), and continues with the next board. Error rows are not charged. Filter on error to find them.