Workday Jobs Scraper

Export public job postings from known Workday-hosted company career sites. Keep job and requisition identifiers, locations, exposed employment fields, optional descriptions and source URLs for separate hiring research. Public posting metadata is not access to applicant accounts, a complete market census or a verified hiring commitment.

Quick start

Start with one known career site, one keyword and a small shared saved-job cap. The existing NVIDIA engineering example is:

{
  "startUrls": [
    {
      "url": "https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite"
    }
  ],
  "searchText": "engineering",
  "maxItems": 25,
  "includeJobDetails": true,
  "companyName": "NVIDIA",
  "connectionMode": "Direct"
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose an example to start with a small, preconfigured input.

• NVIDIA Workday AI engineering jobs scraper — Collect a bounded engineering sample from NVIDIA's public career site with descriptions.
• Salesforce Workday remote jobs scraper — Search Salesforce's public career site for remote-related postings. Confirm location eligibility from the returned content.
• Adobe Workday product manager jobs scraper — Collect Adobe product-manager search results with available details.

What you get

One saved Workday job row with title, source and posting identifiers, company label, available locations and dates, and optional detail content. remoteType is inferred from location text, while a companyName override is your supplied label rather than an independently verified employer identity. RUN_SUMMARY and WORK_CHECKPOINT_V1 describe partial work and recovery context.

Who is it for?

• Recruiting and labor-market researchers reviewing role and location samples from named companies.
• Competitive research teams retaining source-backed hiring observations.
• Job-data developers mapping Workday identifiers and fields into their own products.
• Automation builders handing completed public job datasets to downstream reports or analysis tools.

How you can use the data

• Review NVIDIA engineering roles. Use the existing career site and engineering query, keeping jobId, workdayId, locations and sourceUrl. The keyword narrows that source, not a global Workday job search or a guarantee of every role.
• Compare disclosed job families and employment labels. Keep details enabled when you need descriptions, exact locations and category context. Missing fields remain unknown, and an inferred remote label does not establish applicant-location eligibility.
• Choose a lightweight listing observation. Turn detail enrichment off when you only need the base listing sample. Do not describe missing detail-page fields as proof that a company has no requirements, location or salary policy.
• Maintain your own source-cited weekly brief. Use the existing workflow below, retaining IDs and URLs beside any model-generated analysis. Snapshots, comparisons and notifications live in your destination rather than inside this Actor.

Existing weekly research workflow

Build a source-cited brief from named competitors that use public Workday career sites:

1. Add one or more public Workday career-site URLs, use a consistent companyName override, and schedule the input weekly in Apify.
2. Keep includeJobDetails: true when your model needs descriptions, exact locations, job families, or employment types. Use false for a faster listing-level count.
3. Send the completed dataset via the Apify API or webhook to n8n, a warehouse, or your AI workflow.
4. Compare snapshots using company, jobId, workdayId, and url, then summarize new roles, changing job families, remote signals, and location expansion.
5. Preserve url citations and the underlying rows so every AI-generated claim can be checked against its public posting.

Portfolio routing: Choose this Actor for known companies on Workday. Use LinkedIn Jobs Scraper for broad public job discovery by keyword and location, or ATS Jobs Scraper for normalized boards across Greenhouse, Lever, Ashby, Recruitee, SmartRecruiters, and Personio. The Actors return separate schemas, so map company, title, location, identifiers, and URLs in your downstream workflow.

A companyName override applies to the run. Use it consistently for a known company rather than labeling unrelated companies as one employer when combining career sites.

Input settings

Setting	JSON key	Use it for	Example
Workday career site URLs	startUrls	Required public Workday career pages to scrape.	[{"url":"https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite"}]
Keyword search	searchText	Optional keyword sent to Workday search.	engineering
Maximum jobs	maxItems	Cap saved job records across all career sites.	50
Include job descriptions	includeJobDetails	Fetch each detail page for descriptions, exact locations, and IDs.	true
Company name override	companyName	Force a clean company name in output.	NVIDIA
Connection	connectionMode	Use Direct by default. Automatic selects Apify Proxy and can incur proxy costs.	Direct
Run safety budget	maxRunSeconds	Optional 35–300 second safety limit. The last 30 seconds are reserved for saving progress.	300
Resume checkpoint	resumeCheckpoint	Optional WORK_CHECKPOINT_V1 record from an earlier controlled cutoff. Keep all other collection settings the same.	{...}

Output data

The existing illustrative row shows shape rather than a fresh NVIDIA posting lookup:

{
  "title": "Senior Software Engineer",
  "company": "NVIDIA",
  "jobId": "JR1999999",
  "workdayId": "abc123",
  "externalPath": "/en-US/NVIDIAExternalCareerSite/job/US-CA-Santa-Clara/Senior-Software-Engineer_JR1999999",
  "url": "https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite/job/US-CA-Santa-Clara/Senior-Software-Engineer_JR1999999",
  "locationsText": "US, CA, Santa Clara",
  "locations": ["US, CA, Santa Clara"],
  "postedOn": "Posted 2 Days Ago",
  "postedDate": null,
  "employmentType": "Full time",
  "jobFamily": "Engineering",
  "category": "Engineering",
  "remoteType": null,
  "descriptionText": "We are looking for a senior software engineer...",
  "sourceUrl": "https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite",
  "scrapedAt": "2026-07-03T10:00:00.000Z"
}

The actor returns one dataset row per saved Workday job posting.

Field	Description
title	Job title
company	Company name inferred from the Workday tenant or set by companyName
jobId	Public requisition or job ID when available
workdayId	Workday internal posting ID when available
externalPath	Workday job path
url	Public job posting URL
locationsText	Human-readable location text
locations	Location list from job details
postedOn	Posted label from Workday
postedDate	Detail-page start or posted date when available
employmentType	Employment or time type when available
jobFamily	Workday job family when available
category	Job family group or category when available
remoteType	Inferred Remote or Hybrid signal when present in location text
descriptionHtml	Job description HTML when detail fetching is enabled
descriptionText	Plain-text job description when detail fetching is enabled
sourceUrl	Input Workday career site URL
scrapedAt	ISO timestamp for the scrape

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The run charges a start event before collection begins. A started collection can incur that fee even when no jobs are available.

Each saved job produces a result event. Unavailable sources and unsaved records do not create job-result charges. The run stops collecting when its result-event budget is exhausted. Keep the shared cap modest and request details only when useful.

Platform compute, storage, proxies or transfer can also apply. See the live Pricing tab for current event rates and discounts.

Tips for best results

• Use the public career site URL: Start from a Workday-hosted careers page, not a private applicant portal.
• Search narrowly first: Test with one company, one keyword, and maxItems: 25.
• Keep details on for analysis: includeJobDetails gives cleaner locations, descriptions, and IDs.
• Turn details off for speed: Use includeJobDetails: false for quick list-level monitoring.
• Use company overrides: Set companyName for cleaner dashboards when Workday tenant names are abbreviated.
• Use the run safety budget for controlled runs: Leave maxRunSeconds at 300 for normal exports. If a platform migration or short controlled run interrupts collection, the Actor writes WORK_CHECKPOINT_V1. It resumes automatically after an in-run migration. For a separate run, copy that record into resumeCheckpoint with the same collection settings.

Limits and caveats

• The actor extracts public Workday-hosted job postings only.
• It does not access private applicant accounts, candidate data, saved applications, or login-gated pages.
• Some Workday tenants use custom site names, regions, or posting fields, so a few fields can be empty.
• remoteType is inferred from location text and may be empty when Workday does not label a role as remote or hybrid.
• Source career pages can change structure or availability over time.

The shared cap bounds saved rows across up to 100 supplied career sites. Source fields and availability can change between observations, so a small or partial export is not a complete account of hiring activity. Exceptionally large source responses can exceed the safety limit and leave list-level data or partial results instead of full descriptions.

The existing controlled-cutoff checkpoint supports same-run migration recovery, or an explicit separate run using resumeCheckpoint with unchanged collection settings. Keep the checkpoint and diagnostics rather than treating partial output as an automatic recurring-monitoring feature. The separate run has its normal start event and saved-result charges.

This actor extracts publicly available job postings from Workday-hosted career sites.

Use the data responsibly, follow Workday site terms, Apify's terms, and applicable employment, privacy, and anti-spam laws.

Do not use the actor to access private candidate data, applicant accounts, or login-protected workflows.

Privacy and data handling

This Actor only requests the permissions needed to run the input you provide. It uses your input (such as URLs, search terms, identifiers, filters, and limits) only to fetch the requested public data from the relevant source site or API for this Actor, then writes results to your Apify dataset/key-value store.

Data may pass through Apify platform services and Apify Proxy during the run, and requests are sent only to the target site or public data provider required for this Actor's results. FetchCat does not send your inputs or outputs to advertising networks, data brokers, or model-training services, and does not retain run data outside Apify storage after the run except when you explicitly share run details for transient support debugging.

You are responsible for using this Actor lawfully, respecting the target site's terms, and avoiding unnecessary personal or sensitive data in inputs. Review the output before storing, sharing, or combining it with other data.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~workday-jobs-scraper/runs?token=YOUR_APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"startUrls":[{"url":"https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite"}],"searchText":"engineering","maxItems":25}'

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/workday-jobs-scraper').call({
  startUrls: [{ url: 'https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite' }],
  searchText: 'engineering',
  maxItems: 25,
  includeJobDetails: true
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("fetch_cat/workday-jobs-scraper").call(run_input={
    "startUrls": [{"url": "https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite"}],
    "searchText": "engineering",
    "maxItems": 25,
    "includeJobDetails": True,
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

MCP and AI agents

You can ask your AI assistant to collect data with Workday Jobs Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Workday Jobs Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/workday-jobs-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Workday Jobs Scraper by Fetch Cat, or give it the identifier fetch_cat/workday-jobs-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Workday Jobs Scraper to collect up to 5 engineering jobs from https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite with details enabled and the NVIDIA company label. Keep source IDs and location context without inferring applicant eligibility.”
• “Collect up to 5 public postings from that NVIDIA Workday career site for engineering with details off. Keep the source URL and base listing fields without inventing missing descriptions or locations.”
• “Retrieve up to 5 engineering postings from the same NVIDIA career site with details enabled. Preserve source-level errors, partial-work diagnostics and unknown remote labels before I prepare my own source-cited report, without scheduling another run.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Does it need a Workday login or cookie?

No. Provide a public Workday career-site URL. The Actor does not access applicant accounts or login-protected pages.

Can I export the results to CSV, JSON, Excel, or an API workflow?

Yes. Every saved job is a dataset row that you can export from Apify or retrieve through the Apify API.

Why are some fields empty?

Workday tenants decide which posting fields they publish. Description, exact locations, job family, date, and remote labels can be unavailable on a particular public posting.

What happens if one company career site is unavailable?

Workday hostnames can change when a company moves regions. If both the jobs API and the tenant's robots.txt confirm that the tenant is absent on the supplied host, the run succeeds with no rows for that URL and a visible warning in the log and RUN_SUMMARY (tenant_unavailable_on_supplied_host). Copy the current Workday career-site URL from the company's official careers page and retry. For example, Comcast's current page links to https://comcast.wd115.myworkdayjobs.com/en-US/Comcast_Careers, rather than its old wd5 host. The Actor does not guess replacement hosts. An unconfirmed HTTP 422, blocking, or a failed availability check remains an extraction error, not an empty-result claim.

Expected unavailable targets and valid searches with no usable jobs complete successfully with an empty dataset and a truthful reason in RUN_SUMMARY. Unavailability alone does not establish privacy or deletion. Mixed runs keep useful rows from other sites. Unexpected extraction failures remain visible in the summary, while essential storage and billing errors fail the run. A deadline or result-budget cutoff preserves unfinished work as WORK_CHECKPOINT_V1.

Related Actors

Explore related actors from the same Apify account:

• LinkedIn Jobs Scraper — Collect public LinkedIn job listings and available job details.
• RemoteOK Jobs Scraper — Collect public RemoteOK remote job listings and available job details.
• Lever Jobs Scraper — Collect public Lever job-board openings and available job details.
• SmartRecruiters Jobs Scraper — Collect public SmartRecruiters job listings and available job details.
• GitHub Repositories Search Scraper — Collect public GitHub repository-search records and available repository metadata.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥