# Jobs Monitor: Greenhouse, Lever, Ashby, Workday + 5 more ATS (`rationalistic_canoe/ats-jobs-feed`) Actor

Watch career sites on Greenhouse, Lever, Ashby, Workday, Workable, Recruitee, Personio, Teamtailor and BambooHR via public job-board endpoints. Paste a board or careers page URL. Clean schema, salary parsing, filters, and a monitor for new, changed and closed jobs with a webhook.

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

## Pricing

from $1.00 / 1,000 job saveds

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

## Career Site Jobs Monitor: Greenhouse, Lever, Ashby, Workday, Workable, Recruitee, Personio, Teamtailor & BambooHR

![ATS Jobs Feed](https://api.apify.com/v2/key-value-stores/oVyHagRECuIrMkC2H/records/ats-banner)

Watch the career sites of any list of companies and get **only the jobs that are new or changed since your last run**, in one clean JSON schema. The actor reads each ATS's **public job-board endpoints** (the same ones the company's own careers page uses). No proxies, no logins, no browser, so runs are fast and cheap.

**Try it free:** Apify's free plan gives $5/month of usage, no card needed. That's about 5,000 jobs a month at $1.00 per 1,000.

### Supported job boards

| ATS | Short form | Board URL example | Notes |
|---|---|---|---|
| Greenhouse | `greenhouse:gitlab` | `https://job-boards.greenhouse.io/gitlab` | Structured salary when published |
| Lever | `lever:palantir` | `https://jobs.lever.co/palantir` | Spaced 1 s apart (Lever's crawl delay) |
| Ashby | `ashby:ramp` | `https://jobs.ashbyhq.com/ramp` | Structured salary |
| Workday | `workday:adobe.wd5/external_experienced` | `https://adobe.wd5.myworkdayjobs.com/external_experienced` | Up to 2,000 jobs per search (Workday's limit); see *Workday search text* |
| Workable | `workable:huggingface` | `https://apply.workable.com/huggingface/` | |
| Recruitee | `recruitee:bunq` | `https://bunq.recruitee.com/` | Structured salary when published |
| Personio | `personio:ottonova` | `https://ottonova.jobs.personio.de/` | `.de` and `.com` boards |
| Teamtailor | `teamtailor:polestar` | `https://polestar.teamtailor.com/` | `*.teamtailor.com` boards |
| BambooHR | `bamboohr:scribd` | `https://scribd.bamboohr.com/careers` | Posted date comes from a per-job call |
| SmartRecruiters | `smartrecruiters:<companyId>` | `https://jobs.smartrecruiters.com/<companyId>` | Opt-in only, see FAQ |

**Don't know the board?** Paste the company's careers page (for example `https://www.figma.com/careers/`) or just its domain. The actor reads that page, checks robots.txt first, and finds the job board it links to. Pages that load jobs only with JavaScript may not reveal their board; the run says so in `OUTPUT`.

### What you can use it for

- **Job alerts:** schedule a monitor and send only new postings to Slack, Telegram, email, a Google Sheet or your own webhook.
- **Niche job boards:** feed a board (remote AI jobs, climate jobs, fintech) from hundreds of company career sites.
- **Hiring signals for sales and recruiting:** a new "Head of RevOps" posting, a changed salary band, or a role that closed tells you what a company is doing.
- **Salary research:** pay ranges become `min`, `max`, `currency` and `period`.
- **AI agents and automations:** a small, predictable schema for n8n, Make, Zapier, LangChain or an MCP client.

### Features

- Ten ATS platforms behind one input and one output schema; mix them in one run.
- **Monitor mode:**
  - *New jobs only*: each scheduled run returns postings it has not returned before.
  - *New and changed*: also returns jobs whose title, location, department, employment type, remote status or salary changed (`changeType: "updated"`), and jobs that closed and came back (`"reopened"`). Description wording edits are ignored, so you don't get noise.
  - *List jobs that closed*: jobs that disappeared since the last run go to the `CLOSED_JOBS` record and the webhook. They are not billed.
  - State is kept per board, so adding a company to a running watchlist does not flood you (with *skip jobs already open on the first run*).
- Filters: title keywords (optionally the description too), excluded keywords, locations, remote only, departments, employment type, posted within N days, minimum yearly salary.
- **Webhook delivery:** saved jobs are POSTed as JSON in batches, with an optional secret header. No call when nothing is new.
- **History dataset:** optionally append every saved job to a named dataset that grows across runs.
- Respects **Max jobs saved** and your run's **maximum charge**. A job cut off by either limit is delivered on the next monitor run, never lost.
- One failing board never stops the run. Each board's count or error is in the `OUTPUT` record.

### Input example

```json
{
  "sources": ["greenhouse:gitlab", "workday:adobe.wd5/external_experienced", "workable:huggingface", "https://www.figma.com/careers/"],
  "keywords": ["engineer", "AI"],
  "excludeKeywords": ["intern"],
  "remoteOnly": true,
  "postedWithinDays": 14,
  "includeDescription": "none",
  "monitorMode": "newAndChanged",
  "monitorName": "remote-ai-eng",
  "reportClosedJobs": true,
  "webhookUrl": "https://example.com/my-hook",
  "maxJobs": 200
}
```

### Output example

Real item from a run on 28 Oct 2026 (monitor fields added in v2):

```json
{
  "id": "greenhouse:gitlab:8638232002",
  "ats": "greenhouse",
  "board": "gitlab",
  "company": "GitLab",
  "jobId": "8638232002",
  "title": "AI Transformation Owner, CRO",
  "department": "Enablement",
  "location": "Remote, United States",
  "country": "US",
  "isRemote": true,
  "workplaceType": "remote",
  "postedAt": "2026-07-22T17:38:40.000Z",
  "updatedAt": "2026-10-15T19:24:46.000Z",
  "url": "https://job-boards.greenhouse.io/gitlab/jobs/8638232002",
  "salary": { "min": 139200, "max": 235200, "currency": "USD", "period": "year", "source": "ats" },
  "scrapedAt": "2026-10-28T03:33:33.859Z"
}
```

In monitor mode each item also has `isNew`, `changeType` (`new`, `updated` or `reopened`) and `firstSeenAt`. Fields an ATS leaves empty come back as `null`.

#### What each ATS fills in

From our live test on 31 Oct 2026 (up to 20 jobs per board):

| Board tested | Posted date | Location | Country | Description | Salary |
|---|---|---|---|---|---|
| greenhouse:gitlab | 20/20 | 20/20 | 19/20 | 20/20 | 8/20 |
| lever:palantir | 20/20 | 20/20 | 20/20 | 20/20 | 14/20 |
| ashby:ramp | 20/20 | 20/20 | 20/20 | 20/20 | 20/20 |
| workday:adobe.wd5/external_experienced | 20/20 | 20/20 | 20/20 | 20/20 | 11/20 |
| workable:huggingface | 6/6 | 6/6 | 6/6 | 6/6 | 0/6 |
| recruitee:bunq | 20/20 | 20/20 | 20/20 | 20/20 | 0/20 |
| personio:ottonova | 9/9 | 9/9 | 0/9 | 9/9 | 0/9 |
| teamtailor:polestar | 13/13 | 13/13 | 13/13 | 13/13 | 0/13 |
| bamboohr:scribd | 2/2 | 2/2 | 2/2 | 1/2 | 0/2 |

Salary appears only when the company publishes it. Personio lists the office city without a country, so `country` is often empty there.

### Pricing

**$1.00 per 1,000 jobs saved** on every plan, plus Apify's default actor start event ($0.00005 per run). Closed-job records and webhook calls are free.

Examples: a daily monitor that finds 40 new or changed jobs costs about $1.20 a month. A one-off pull of 5,000 jobs costs $5.00. Set **Max jobs saved** or a maximum charge per run to cap any run.

### How to find a company's board

Easiest: paste the careers page URL and let the actor find it. Or look at a job link on the careers page:

- `job-boards.greenhouse.io/<board>` or `boards.greenhouse.io/<board>`: Greenhouse
- `jobs.lever.co/<board>`: Lever
- `jobs.ashbyhq.com/<board>`: Ashby
- `<tenant>.wd5.myworkdayjobs.com/<site>`: Workday (paste the whole URL)
- `apply.workable.com/<account>`: Workable
- `<board>.recruitee.com`, `<board>.jobs.personio.de`, `<board>.teamtailor.com`, `<board>.bamboohr.com`

A wrong board name is listed as `BOARD_NOT_FOUND` in the `OUTPUT` record and the other boards still run.

### Schedule a job monitor

1. Set **Monitor mode** to *New jobs only* or *New and changed*, and give the watchlist a name.
2. Turn on **skip jobs already open on the first run** to start quietly.
3. Add a **Webhook URL**, or connect an Apify integration (Slack, email, Google Sheets).
4. Create an Apify schedule, for example every 6 hours.

#### Use it from n8n, Make or Zapier

Apify's official n8n, Make and Zapier integrations can run this actor on a schedule and pass the new jobs to Telegram, Slack, email or a sheet. With **Monitor** on, each run returns only new or changed jobs, so the message holds only what is new.

### FAQ

**How fresh is the data?** Every run reads the live job board, so results match the careers page at run time.

**Does it use proxies or a browser?** No. These are the endpoints the ATS serves to career sites, so plain HTTPS requests are enough.

**Can I monitor hundreds of companies?** Yes. Boards are read 4 at a time by default (*Boards read in parallel*), with per-host delays. A failing board is skipped and reported.

**Do I pay for jobs I have already seen?** No. In monitor mode only new (or, if you choose, changed) jobs are saved, and only saved jobs are billed.

**I used version 1 with "only jobs not seen before". Do I need to change anything?** No. That setting still works and your existing watchlist carries over without re-sending old jobs.

**Why can Workday show "2,000" jobs?** Workday's job search stops at 2,000 results. For very large Workday sites, set **Workday search text** (for example `engineer`) so the list is narrowed before filters run. A large Workday site takes about a minute per 2,000 jobs, because pages are fetched politely one after another.

**What about SmartRecruiters?** SmartRecruiters publishes its Posting API for each company's own career site, and its robots.txt asks automated clients to stay out. The actor reads a SmartRecruiters board only when you turn on **SmartRecruiters boards you are authorised to read**, for example your own company's.

### Data and compliance

The actor reads public job postings through endpoints each ATS serves for job boards and career sites, and it checks robots.txt before reading a careers page you give it. It does not log in, bypass any access control or collect candidate data. Postings can include a recruiter's name in the description text; you are responsible for using the data lawfully, including GDPR, CCPA or India's DPDP Act where they apply.

### Limits

- Salary appears only when the company publishes it.
- Workday: at most 2,000 jobs per search (see FAQ). BambooHR and Workday need one extra request per job for descriptions and exact dates, so they are slower when you ask for descriptions.
- Careers-page detection finds boards linked in the page HTML. It can miss boards loaded only by JavaScript; in that case paste the board URL.
- Teamtailor boards on a custom domain: paste the `*.teamtailor.com` address.

### Support

Open an issue on the actor's Issues tab with your input and the run link. Issues are answered within one business day.

Built with the help of AI coding agents. Version 2.0 is covered by 33 unit tests, 11 live checks against real boards and a 15-check end-to-end run, all passing on 31 Oct 2026.

# Actor input Schema

## `sources` (type: `array`):

One per line. A board URL or short form for Greenhouse, Lever, Ashby, Workable, Recruitee, Personio, Teamtailor, BambooHR or Workday (greenhouse:gitlab, lever:palantir, ashby:ramp, workable:huggingface, recruitee:bunq, personio:ottonova, teamtailor:polestar, bamboohr:scribd, workday:adobe.wd5/external_experienced), or a company careers page URL such as https://www.figma.com/careers/ (the actor finds the board it links to).

## `keywords` (type: `array`):

Keep jobs whose title contains any of these (case-insensitive). Empty = all jobs.

## `searchDescription` (type: `boolean`):

Matches keywords in the job description as well as the title.

## `excludeKeywords` (type: `array`):

Drop jobs whose title contains any of these, e.g. intern, senior.

## `locations` (type: `array`):

Keep jobs whose location contains any of these, e.g. United States, London, Remote.

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

Keep only jobs marked remote or with Remote in the location.

## `departments` (type: `array`):

Keep jobs whose department or team contains any of these, e.g. Engineering, Product.

## `employmentTypes` (type: `array`):

e.g. Full-time, Contract, Intern. Uses the label each ATS provides.

## `postedWithinDays` (type: `integer`):

0 = no date filter.

## `minSalary` (type: `integer`):

Keep only jobs whose published yearly range reaches this amount (any currency). 0 = off. Jobs with no published salary are dropped when this is set.

## `includeDescription` (type: `string`):

How the job description is included in each item.

## `monitorMode` (type: `string`):

Remembers jobs between runs in a named key-value store. 'New jobs only' returns postings not seen before. 'New and changed' also returns jobs whose title, location, department, type, remote status or salary changed, and jobs that were closed and reopened. Each item gets changeType: new, updated or reopened.

## `onlyNewJobs` (type: `boolean`):

Kept for monitors created with version 1. Same as Monitor mode = New jobs only. Leave off and use Monitor mode instead.

## `monitorName` (type: `string`):

Use a different name for each separate watchlist.

## `skipExistingOnFirstRun` (type: `boolean`):

Turn on to start quietly: jobs already open the first time a board is read are remembered but not returned. Works per board, so a board added to the list later also starts quietly.

## `reportClosedJobs` (type: `boolean`):

Writes jobs that disappeared from a board since the last run to the CLOSED_JOBS record (and to the webhook). Closed jobs are not saved to the dataset and are not billed. Only boards read in full are checked.

## `webhookUrl` (type: `string`):

Optional. At the end of the run, saved jobs are POSTed here as JSON in batches ({items, closed, monitorName, batch, batches}). No call is made when nothing new was found.

## `webhookSecret` (type: `string`):

Optional. Sent as the X-Webhook-Secret header so your endpoint can check the call came from your run.

## `webhookBatchSize` (type: `integer`):

Jobs per webhook call.

## `outputDatasetName` (type: `string`):

Optional. Saved jobs are also appended to this named dataset, so a scheduled monitor builds one growing history across runs.

## `maxJobsPerSource` (type: `integer`):

0 = no limit.

## `maxJobs` (type: `integer`):

0 = no limit. Each saved job is one billable result.

## `workdaySearchText` (type: `string`):

Workday sites return at most 2,000 jobs per search. For very large Workday sites, enter a search word (e.g. engineer) to narrow the list before filters run.

## `maxConcurrency` (type: `integer`):

How many boards are read at the same time. Per-host politeness delays still apply.

## `allowSmartRecruiters` (type: `boolean`):

SmartRecruiters publishes its Posting API for each company's own career site, and its robots.txt asks automated clients to stay out. Turn this on only for boards you are authorised to read, such as your own company's. When off, smartrecruiters: sources are skipped and listed in OUTPUT.

## Actor input object example

```json
{
  "sources": [
    "greenhouse:gitlab",
    "lever:palantir",
    "ashby:ramp",
    "workable:huggingface",
    "https://www.figma.com/careers/"
  ],
  "keywords": [
    "engineer",
    "AI"
  ],
  "searchDescription": false,
  "excludeKeywords": [],
  "locations": [],
  "remoteOnly": false,
  "departments": [],
  "employmentTypes": [],
  "postedWithinDays": 0,
  "minSalary": 0,
  "includeDescription": "text",
  "monitorMode": "off",
  "onlyNewJobs": false,
  "monitorName": "default",
  "skipExistingOnFirstRun": false,
  "reportClosedJobs": false,
  "webhookBatchSize": 100,
  "maxJobsPerSource": 0,
  "maxJobs": 200,
  "workdaySearchText": "",
  "maxConcurrency": 4,
  "allowSmartRecruiters": false
}
```

# Actor output Schema

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

One item per job in the default dataset, overview table view.

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

Per-board counts (fetched, matched, saved), errors and stop reason, stored as the OUTPUT record.

## `closedJobs` (type: `string`):

Jobs that disappeared since the last monitor run (when 'list jobs that closed' is on).

# 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 = {
    "sources": [
        "greenhouse:gitlab",
        "lever:palantir",
        "ashby:ramp",
        "workable:huggingface",
        "https://www.figma.com/careers/"
    ],
    "keywords": [
        "engineer",
        "AI"
    ],
    "maxJobs": 200
};

// Run the Actor and wait for it to finish
const run = await client.actor("rationalistic_canoe/ats-jobs-feed").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 = {
    "sources": [
        "greenhouse:gitlab",
        "lever:palantir",
        "ashby:ramp",
        "workable:huggingface",
        "https://www.figma.com/careers/",
    ],
    "keywords": [
        "engineer",
        "AI",
    ],
    "maxJobs": 200,
}

# Run the Actor and wait for it to finish
run = client.actor("rationalistic_canoe/ats-jobs-feed").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 '{
  "sources": [
    "greenhouse:gitlab",
    "lever:palantir",
    "ashby:ramp",
    "workable:huggingface",
    "https://www.figma.com/careers/"
  ],
  "keywords": [
    "engineer",
    "AI"
  ],
  "maxJobs": 200
}' |
apify call rationalistic_canoe/ats-jobs-feed --silent --output-dataset

```

## MCP server setup

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

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/YMGodqMMIshSAU84L/builds/dt5aiSCih0Gr0L3eO/openapi.json
