# Job Scraper for Workday: Career Sites & New Job Alerts (`lepidata/workday-jobs`) Actor

Open jobs from any company's public Workday career site (myworkdayjobs.com), as clean JSON. Run on a schedule to get only jobs that are new, changed or closed since your last run. Title, location, link, and optional full descriptions. $0.90 per 1,000 jobs.

- **URL**: https://apify.com/lepidata/workday-jobs.md
- **Developed by:** [Lepi Data](https://apify.com/lepidata) (community)
- **Categories:** Jobs
- **Stats:** 3 total users, 2 monthly users, 66.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.90 / 1,000 job results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Job Scraper for Workday: Career Sites & New Job Alerts

### What it does

Give it one or more public Workday career site URLs, and it returns each open job with title, location, and posting URL. Turn on descriptions to also get the full job description and posted date (slower, because each job is fetched separately).

### Two modes

- **Full pull (default):** every open job on each career site.
- **New since last run** (`onlyNewSinceLastRun`): only jobs added, removed, or updated since your previous run. A job counts as changed when its title or location changes, or its description text when descriptions are on. A new date on the posting alone doesn't count. Built for hiring-signal monitoring, so you aren't paying to re-download the same jobs every day.

### Input

- `boards`: list of public Workday career site URLs on myworkdayjobs.com (other hosts are rejected)
- `onlyNewSinceLastRun`: return only jobs that are new or updated since your previous run (default off)
- `includeRemoved`: also return free rows for jobs removed since your previous run (default off)
- `startFromNow`: the first run records the jobs open now without returning or charging for them (one free `baseline-saved` row per company); later runs return only new or changed jobs. Ignored for companies already tracked under the same `stateKey` (default off)
- `stateKey`: name for the saved state, so separate monitors don't overwrite each other (default `default`)
- `titleKeyword` / `locationKeyword`: optional filters on title and location
- `includeDescriptions`: include full job descriptions (default off)
- `maxJobsPerBoard`: cap per board (default 5,000)
- `emailPolicy`: `keep-role` (default) keeps company role addresses like accommodations inboxes; `strip-all` removes every email

### Output (one item per job)

source, board, jobId, title, location, url, changeType (`new` / `updated` / `unchanged` / `removed`), plus a free `board-incomplete` row for any site that couldn't be fully covered. With descriptions on: description, posted date. Department and office are not available from Workday and come back empty. Removed rows carry only the ID and change type.

### Why use this one

- **Health-checked daily** against real company boards. If something breaks, the listing is flagged within a day.
- **Failures are free and visible.** Anything we can't fetch comes back as a free `board-error` row with the reason, never a silent gap.
- **Exact price, no surprises.** You pay only for the jobs delivered, at the price shown below.

### Pricing

$0.90 per 1,000 jobs in every mode, with no start fee. Removed-job alerts are free.

Free-plan accounts get up to 25 results per run to try it out; the run ends with one free row explaining the limit. Paid Apify plans get full results.

If you set a maximum charge per run, the run stops cleanly when it's reached and you're never billed past it. The last row is a free `charge-limit-reached` row showing how many jobs were delivered, and jobs you didn't receive are still marked new on your next run.

### Scope and limits

- Reads public external career sites only. No logins, no talent-community or candidate pages.
- Respects each employer's robots.txt on every run and skips any path it disallows.
- Runs at a deliberately gentle request rate, so large sites take longer than other job sources, especially with descriptions on.
- Workday search results cap at 2,000 jobs per search. Large sites are split into smaller searches to get past that cap. If a site still can't be fully covered, the run returns every job it did get and adds a free `board-incomplete` row showing how many jobs were listed and the site's estimated total. You pay only for jobs delivered, and a partial run never reports missing jobs as removed.
- Postings with no title or link are skipped and counted, not returned.
- A wrong site name comes back as a free `board-error` row with the reason in the `error` field, not a crash.
- Workday's site format is not a documented public API and can change; we run a daily health check and pause or flag the Actor if it breaks.

### Not affiliated

This Actor is an independent, unofficial tool. It is not made, endorsed, or supported by Workday or by any employer whose career site it reads. "Workday" is used only to describe the public career sites this tool reads. Phone numbers and personal email addresses are removed. Company role addresses, like accommodations or recruiting inboxes, are kept so applicants can reach them.

# Actor input Schema

## `boards` (type: `array`):

Public career site URLs, e.g. https://company.wd5.myworkdayjobs.com/SiteName. External career sites only, no login pages. Up to 25 per run. Each site's robots.txt is checked on every run and disallowed sites are skipped.

## `onlyNewSinceLastRun` (type: `boolean`):

Returns only jobs added or changed since your previous run with the same state key. A job counts as changed when its title or location changes, or its description text when descriptions are on. A new date on the posting alone doesn't count. The first run returns everything.

## `startFromNow` (type: `boolean`):

First run records currently open jobs without charging for them; later runs return only new/changed jobs. Ignored for companies already tracked under this stateKey.

## `includeRemoved` (type: `boolean`):

Adds one item per job that disappeared since the last run (changeType = removed).

## `stateKey` (type: `string`):

Name for this monitor. Use different keys to track different board lists separately.

## `titleKeyword` (type: `string`):

Only return jobs whose title contains this text (case-insensitive).

## `locationKeyword` (type: `string`):

Only return jobs whose location contains this text (case-insensitive).

## `includeDescriptions` (type: `boolean`):

Fetch each job's description and posting start date. Off by default: it needs one extra request per job, and requests are deliberately rate limited, so runs take much longer. Switching it on or off between runs marks tracked jobs as updated once.

## `maxJobsPerBoard` (type: `integer`):

Upper limit on jobs returned per board.

## `emailPolicy` (type: `string`):

Phone numbers and personal-looking emails are always removed. Choose whether company role addresses such as accommodations@ stay in.

## Actor input object example

```json
{
  "boards": [
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ],
  "onlyNewSinceLastRun": false,
  "startFromNow": false,
  "includeRemoved": false,
  "stateKey": "default",
  "includeDescriptions": false,
  "maxJobsPerBoard": 5000,
  "emailPolicy": "keep-role"
}
```

# Actor output Schema

## `jobs` (type: `string`):

All job and status rows from this run.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "boards": [
        "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("lepidata/workday-jobs").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "boards": ["https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"] }

# Run the Actor and wait for it to finish
run = client.actor("lepidata/workday-jobs").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "boards": [
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ]
}' |
apify call lepidata/workday-jobs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lepidata/workday-jobs"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/1IqYDyfrdr3JsLFGU/builds/legTRqj4OiDO6S7nS/openapi.json