# Workday Jobs Scraper - Company Careers Site API (`appdata-labs/workday-jobs`) Actor

Get every open role from any company careers site on Workday, starting from the company name alone — the tenant, the pod it lives on and the career-site name are all found for you. Full job descriptions, real posting dates, locations and direct apply links, in one clean table.

- **URL**: https://apify.com/appdata-labs/workday-jobs.md
- **Developed by:** [Kobkoon Janngam](https://apify.com/appdata-labs) (community)
- **Categories:** Agents, MCP servers, Jobs
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 job scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Workday Jobs Scraper — Company Job Board API

**Get every open job from any company hiring on Workday.** Built on the public careers-site API (`/wday/cxs/`) — the same endpoint the company's own careers page calls — so there is no HTML to break and no login to keep alive.

**Quick start:** press **Start** with no configuration at all. It ships with NVIDIA and Adobe and returns their open roles immediately. Then paste in the companies you care about.

### Sample output

| company | title | location | department | publishedAt |
|---|---|---|---|---|
| NVIDIA | Senior Software Engineer - DGX Cloud | US, CA, Remote | Full time | 2026-09-03 |
| Adobe | Photoshop Software Development Engineer | San Jose | Full time | 2026-09-03 |

Every row also carries `jobId`, `url`, `applyUrl`, `provider`, `boardSlug`, `boardSite`, `team`, `employmentType`, `isRemote`, `workplaceType`, `additionalLocations`, `compensation`, `updatedAt`, `descriptionPreview`, `descriptionTruncated` and `descriptionChars`.

### Why this one

**You do not need the careers URL.** Most Workday scrapers want the full myworkdayjobs.com link — something a buyer has to go and find first. This one also accepts a plain company name, and records in the run summary exactly what it resolved to, so your first run hands you the right identifiers for every later one.

**Three identifiers found for you.** Workday is the hardest of the ATS platforms to scrape, and the reason is identity: a feed needs the tenant (`nvidia`), the pod it happens to live on (`wd5`), and the career-site name (`NVIDIAExternalCareerSite`). Every competitor makes you supply the full URL. This Actor takes **`nvidia`** and finds all three — the pod by asking each in turn, and the site names from the tenant’s own `robots.txt`, which publishes one Sitemap line per career site.

**Real dates, not "Posted Today".** Workday’s job list returns the words *Posted Today* rather than a date, which is useless for a scheduled run. This Actor reads each job’s detail record and returns the true `startDate` as an ISO timestamp, so `postedAfter` actually works.

**Full descriptions.** The list endpoint carries a title and nothing else. Every row here is enriched from the job’s own record, so you get the description, the real location, the other locations, the employment type and the requisition ID.

**Descriptions sized for an agent.** The full posting text is cut to an 800-character preview with the true length reported in `descriptionChars`, keeping a row under 2 KB so an AI caller can hold a whole board in context. Set `includeFullDescription` when you want everything.

### What you can do with it

- **Track a competitor's hiring.** Schedule it with `postedAfter` set to yesterday and you get only the new openings — the cleanest public signal of where a company is investing.
- **Build a job board.** Point it at a list of companies and you have a live, structured feed with direct apply links.
- **Source by market.** `remoteOnly` plus `locationContains` narrows hundreds of roles to your patch.
- **Feed an AI agent.** Rows are small, identically shaped, and carry a direct apply URL.

### Input

| Field | Default | Notes |
|---|---|---|
| `companies` | NVIDIA and Adobe | A company name (`nvidia`) or a full myworkdayjobs.com careers URL. Mix freely. |
| `titleContains` | empty | Case-insensitive partial match on the job title. |
| `locationContains` | empty | Matches secondary locations too. |
| `department` | empty | Matches department or team. |
| `remoteOnly` | `false` | Keep only remote roles. |
| `postedAfter` | empty | `YYYY-MM-DD`. The most useful filter for a scheduled run. |
| `includeFullDescription` | `false` | Full posting text instead of a preview. |
| `maxJobsPerCompany` | `100` | Applied after filtering. |

Passing a board URL from a *different* ATS is refused by name rather than quietly read as some other company that happens to share a slug. If you want that flexibility, use the **ATS Jobs Scraper**, which detects the provider for you.

### How it works, and why it keeps working

This Actor reads the public careers-site API (`/wday/cxs/`): public, keyless, and returning JSON. No HTML parsing, no login, no proxy. Workday can redesign every careers page it hosts and this Actor keeps returning the same fields — which is why it is not on the maintenance treadmill that breaks most job scrapers.

### Limits worth knowing before you buy

Enrichment costs one extra request per job, so a large `maxJobsPerCompany` makes for a longer run — roughly three seconds per twenty jobs. Some tenants publish several career sites (Salesforce has nine); this Actor reads the first one listed, so pass the full careers URL when you want a specific site. A job whose detail record cannot be fetched is still returned with its title and a working link rather than being silently dropped.

The tenant is derived from the name you give, which is right far more often than not but not always. A company whose Workday tenant differs from its brand name needs its careers URL, and the run says plainly which entries did not resolve rather than returning a quiet empty result.

### Pricing

Pay per job delivered, after filtering. A company with no matching openings charges you nothing.

### Disclaimer

This is an **unofficial** tool. It is not affiliated with, authorised by, endorsed by, or in
any way officially connected to Workday, Inc. or any company whose job board it reads.
"Workday" is a trademark of its respective owner.

It reads only the **public, unauthenticated** job-board API — the same endpoint a company's
own careers page calls to render publicly advertised vacancies. It signs into nothing,
stores no credentials, and returns nothing behind a login or a paywall. No candidate or
applicant data is accessed; job postings are, by definition, published to be read.

Workday can change or withdraw this endpoint at any time. When a board cannot be read,
this Actor says which company and why rather than handing you an empty result that looks
like an answer.

# Actor input Schema

## `companies` (type: `array`):

Companies whose Workday careers site should be read. A bare company name (nvidia) is enough: the tenant, the pod it lives on and the career site are all found for you. A full myworkdayjobs.com careers URL is also accepted and skips the search.

## `titleContains` (type: `string`):

Keep only jobs whose title contains this text, case-insensitive. Leave empty for every open role. Example: "engineer" matches "Senior Engineer" and "Engineering Manager".

## `locationContains` (type: `string`):

Keep only jobs whose location contains this text, case-insensitive. Secondary locations count too, so "London" still matches a role listed in both Stockholm and London.

## `department` (type: `string`):

Keep only jobs in a matching department or team, case-insensitive and partial. Departments are the company’s own labels, so "engineering" is a safer filter than an exact team name.

## `remoteOnly` (type: `boolean`):

Keep only remote roles. The three providers express this differently — Ashby has a flag, Lever has a workplace type, Greenhouse has only the location text — so all three signals are checked.

## `postedAfter` (type: `string`):

Keep only jobs published on or after this date, as YYYY-MM-DD. The single most useful filter for a scheduled run: set it to yesterday and you get just the new openings.

## `includeFullDescription` (type: `boolean`):

Off by default. Descriptions run to several thousand characters, which makes a row too big for an AI agent to read comfortably. Off, you get an 800-character preview plus the true length; on, you get the whole thing.

## `maxJobsPerCompany` (type: `integer`):

How many jobs to return for each company, after filtering. Boards can be large — Stripe had 592 open roles when this Actor was written — so this keeps a default run fast and cheap.

## Actor input object example

```json
{
  "companies": [
    "nvidia",
    "https://adobe.wd5.myworkdayjobs.com/external_experienced"
  ],
  "titleContains": "engineer",
  "locationContains": "London",
  "department": "engineering",
  "remoteOnly": false,
  "postedAfter": "2026-08-01",
  "includeFullDescription": false,
  "maxJobsPerCompany": 100
}
```

# Actor output Schema

## `rows` (type: `string`):

One row per open job: title, company, location, department, employment type, remote flag, posting date, a direct apply link and the description.

## `summary` (type: `string`):

Which companies resolved to which ATS, how many jobs each returned, and what the filters removed.

# 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 = {
    "companies": [
        "nvidia",
        "adobe"
    ],
    "titleContains": "",
    "locationContains": "",
    "department": "",
    "remoteOnly": false,
    "postedAfter": "",
    "includeFullDescription": false,
    "maxJobsPerCompany": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("appdata-labs/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 = {
    "companies": [
        "nvidia",
        "adobe",
    ],
    "titleContains": "",
    "locationContains": "",
    "department": "",
    "remoteOnly": False,
    "postedAfter": "",
    "includeFullDescription": False,
    "maxJobsPerCompany": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("appdata-labs/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 '{
  "companies": [
    "nvidia",
    "adobe"
  ],
  "titleContains": "",
  "locationContains": "",
  "department": "",
  "remoteOnly": false,
  "postedAfter": "",
  "includeFullDescription": false,
  "maxJobsPerCompany": 50
}' |
apify call appdata-labs/workday-jobs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,appdata-labs/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/MNCbpkd5RmUh6p7bN/builds/rkPCTFKk1eunvsVvZ/openapi.json