# Workday Jobs Scraper + Personio & Recruitee (`beike_r/ats-jobs`) Actor

Get every open job from company career sites on Workday, Personio and Recruitee in one clean format: title, company, location, employment type, date, full description and link. Paste career site URLs, get JSON, CSV or Excel. Contact e-mails and phone numbers are removed. $1 per 1,000 jobs.

- **URL**: https://apify.com/beike_r/ats-jobs.md
- **Developed by:** [Beike](https://apify.com/beike_r) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 jobs

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?

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

### What does Workday Jobs Scraper + Personio & Recruitee do?

This actor collects the open jobs from company career sites that run on **Workday**, **Personio** or **Recruitee**, and returns them all in **one clean format**. Paste one or more career site URLs, and you get a dataset with, per job:

- the job title and the company,
- the location (as text, and for Recruitee also city, postal code, region and country),
- the employment type and the publication date,
- the full job description as **plain text** (no HTML),
- a link to the public job page,
- the URL you started from and the time the job was fetched.

The three systems each have their own API and field names. This actor maps them to the same fields, so you can put jobs from many employers in one spreadsheet, database or job board without writing three parsers. It needs no login, no API key and no proxy.

### How much does it cost?

You pay per job in your dataset: **$1.00 per 1,000 jobs**.

- 100 jobs = $0.10
- 1,000 jobs = $1.00
- 10,000 jobs = $10.00

Set **Maximum number of jobs** (`maxItems`) to cap a run. If you set a maximum cost per run in Apify Console, the actor stops cleanly when that budget is reached and keeps every job it already saved.

### How to use it

1. Open the career site of a company and copy its address. It should contain `myworkdayjobs.com`, `recruitee.com` or `jobs.personio.de` / `jobs.personio.com`. A link to a single job on that site works too: the actor then fetches all jobs of the site.
2. Paste one URL per line into **Career site URLs**.
3. Optional, for Workday: type a **Search text** (for example `engineer` or `Berlin`) to fetch only matching jobs. You can also paste the address of a search you did on the Workday site itself, such as `https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite?q=Tokyo`: when **Search text** is empty, the actor uses the `q=` part of that URL as the search text. Other filters in the URL (location, job family and so on) are not used; the log then shows a warning.
4. Set **Maximum number of jobs** and click **Start**.
5. Download the results as JSON, CSV or Excel, or read them through the Apify API.

To follow employers over time, save your input as a task and schedule it, for example once a day.

### Input and output example

Input:

```json
{
    "startUrls": [
        "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite",
        "https://everphone.jobs.personio.de",
        "https://logex.recruitee.com"
    ],
    "searchText": "",
    "maxItems": 100
}
```

One item of the output (description shortened):

```json
{
    "source": "workday",
    "sourceJobId": "JR2021512",
    "title": "Senior Network Security Engineer - DGX Cloud",
    "company": "2100 NVIDIA USA",
    "locationText": "US, CA, Santa Clara",
    "city": null,
    "postalCode": null,
    "region": null,
    "country": "US",
    "employmentType": "Full time",
    "postedAt": "2026-10-05",
    "description": "NVIDIA is seeking a Sr Network Security Engineer to implement and maintain robust security ...",
    "url": "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite/job/US-CA-Santa-Clara/Senior-Network-Security-Engineer---DGX-Cloud_JR2021512",
    "inputUrl": "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite",
    "scrapedAt": "2026-10-05T12:20:48+00:00"
}
```

Fields the source does not provide are `null`, so every item has the same keys.

### Supported systems

| System | URL looks like | What you get |
|---|---|---|
| Workday | `https://company.wd5.myworkdayjobs.com/SiteName` (with or without a language code such as `/en-US/`) | all fields except city, postal code and region; `company` is the legal entity of the job |
| Recruitee | `https://company.recruitee.com` | all fields; `description` is the description plus the requirements |
| Personio | `https://company.jobs.personio.de` or `.com` | title, company, office, employment type and schedule, date, description sections |

Other systems (Teamtailor, Greenhouse, Lever, SmartRecruiters) and career sites on a company's own domain are not supported yet. Such a URL gives a clear error in the log, and the other URLs still run.

### Limitations

- **At most 2000 jobs per Workday site.** Workday itself stops listing after 2000 results. For bigger employers, run several searches with **Search text** (for example per country or job family).
- **Workday URL filters:** only the search (`q=` in the URL, or **Search text**) is used. Filters such as location or job family in a Workday URL are ignored, with a warning in the log. If both are given, **Search text** wins over `q=`.
- **Contact details:** e-mail addresses (also written as `jane(at)company.com`) and phone numbers in the usual formats (such as `+49 30 1234567`, `0049 30 1234567` and `030 1234567`) are removed from the description text. The filter is not perfect: unusual spellings, such as a local number without any spaces (`0301234567`), `(dot)` instead of a dot, or a short prefix like `06-12345678`, can remain, and so can a name in the text (for example "contact Jane Doe"). Recruiter and contact fields of the sources are never included.
- **No proxy.** The actor calls the public career site APIs directly. If a site blocks these requests, that URL fails with an error and the rest of the run continues.
- **Dates and types are not normalised.** `employmentType` is the source's own wording (`Full time`, `fulltime_fixed_term`, `permanent, full-time`). For Personio, `postedAt` is the date the job was created, which can be years ago.
- **Workday is fetched one job at a time,** because the description is only in the job detail. In a test this took about one second per job, so a full site of 2000 jobs takes around half an hour.

### FAQ

#### Why did I get fewer jobs than the career site shows?

Check three things: **Maximum number of jobs**, your maximum cost per run, and the Workday limit of 2000 jobs per site. The log ends with a summary such as `Done: 120 jobs from 3 sources, 1 failed: <url> (<reason>)`. On Workday a job can also close while the actor is fetching; its page then fails, the actor skips that one job with a warning and goes on, and the summary says for example `2 jobs skipped (detail page failed)`.

#### What happens if one URL is wrong?

That URL gets one ERROR line in the log with what went wrong and what to check, and the actor continues with the next URL. The run only ends as failed when it found no jobs at all and at least one URL failed, so a scheduled run alerts you. A search without matches is not a failure: the run succeeds with a warning.

#### Does a job appear twice if I give the same site twice?

No. A site given twice (also as `.de` and `.com` for Personio) is fetched once, and within one run each job appears once, also if a new job is posted while the actor is paging through a Workday site.

#### Can I get only the jobs that are new since my last run?

Not yet. Use `source` plus `sourceJobId` to compare runs on your side.

#### Is the data personal?

The output contains job ads, not people. See the contact details point under Limitations.

# Actor input Schema

## `startUrls` (type: `array`):

One URL per career site. Supported: Workday (https://company.wd5.myworkdayjobs.com/SiteName), Recruitee (https://company.recruitee.com) and Personio (https://company.jobs.personio.de or .com). A link to a single job on such a site also works: the actor then fetches all jobs of that site.

## `searchText` (type: `string`):

Only fetch Workday jobs that match this text, the same as the search box on the career site. Useful because Workday lists at most 2000 jobs per site. Recruitee and Personio always return all jobs.

## `maxItems` (type: `integer`):

The actor stops after this many jobs in total, over all career sites. You pay per job, so this also caps the cost.

## Actor input object example

```json
{
  "startUrls": [
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ],
  "searchText": "",
  "maxItems": 10
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 = {
    "startUrls": [
        "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
    ],
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("beike_r/ats-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 = {
    "startUrls": ["https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"],
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("beike_r/ats-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 '{
  "startUrls": [
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ],
  "maxItems": 10
}' |
apify call beike_r/ats-jobs --silent --output-dataset

```

## MCP server setup

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