# Hiring Tracker: Lever, Ashby, Workable, Recruitee, Personio (`frostpine456/hiring-tracker`) Actor

Track open jobs at target companies across Lever, Ashby, Workable, Recruitee and Personio. Each job is marked new, existing or removed since your last run. $1.50 per 1,000 jobs; starting is free.

- **URL**: https://apify.com/frostpine456/hiring-tracker.md
- **Developed by:** [M J](https://apify.com/frostpine456) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.50 / 1,000 job records

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

## Hiring Tracker: track job postings at companies (Lever, Ashby, Workable, Recruitee, Personio)

**Track job postings at the companies you care about and see what is new or gone since your last run.** Give the Actor a list of company domains or job board slugs and it returns one normalised record per open job, read from the public career site jobs on Lever, Ashby, Workable, Recruitee and Personio boards. Every job is marked `new`, `existing` or `removed`, so a scheduled run turns job postings into hiring signals and job change alerts. It suits sales and recruiting teams, analysts, investors and anyone running a competitor hiring monitor. Pricing is pay per result: **$1.50 per 1,000 job records**, and starting a run is free.

### What's new

Hiring Tracker now reads Workable, Recruitee and Personio job boards as well as Lever and Ashby, so one Actor covers five ATSs. If you pass domains or board slugs, a company may now resolve to extra boards that were not found before. The jobs on those newly found boards are billed once as `new` on the first run after the upgrade, then show as `existing` on later runs as usual.

### Use cases

- **Sales prospecting from hiring signals.** Watch target accounts and reach out when they open roles that point to a need, such as a first security hire or a new sales team.
- **Competitor hiring monitor.** Track which roles, teams and locations competitors are adding or closing, with the full job text if you want it.
- **Investor and market research.** Follow hiring at portfolio companies or a sector watchlist, and see where headcount is growing.
- **Job boards and alerts.** Feed a niche job board, newsletter or Slack channel with only the postings that appeared or disappeared since the last run.

### Use it from Claude, Cursor or any AI agent

Add Hiring Tracker as a tool through Apify's MCP server: connect your MCP client to https://mcp.apify.com?tools=frostpine456/hiring-tracker with your Apify API token. Then ask things like "What roles is Ramp hiring for?" or "Which of these companies posted new jobs since last week?" For quick answers, pass one or two companies and turn includeDescriptions off.

### Supported job boards

You can pass a company domain (`acme.com`) for any of these, or point at the board directly for a sure match. A bare slug (`acme`) is checked on all five systems.

#### Lever jobs scraper

Lever boards, including EU-hosted ones. Use `https://jobs.lever.co/acme`, `https://jobs.eu.lever.co/acme` or `lever:acme`.

#### Ashby jobs

Ashby boards. Use `https://jobs.ashbyhq.com/acme` or `ashby:acme`.

#### Workable jobs scraper

Workable boards. Use `https://apply.workable.com/acme/`, `https://acme.workable.com` or `workable:acme`.

#### Recruitee jobs

Recruitee boards. Use `https://acme.recruitee.com` or `recruitee:acme`.

#### Personio jobs export

Personio career pages, common among DACH companies. Use `https://acme.jobs.personio.de`, `https://acme.jobs.personio.com` or `personio:acme`.

Greenhouse, Workday, SmartRecruiters and Teamtailor are not supported.

### Input

Each item in `companies` can be:

- a company domain: `acme.com` or `https://www.acme.com/careers`
- a board URL, including a link to one job on that board: `https://jobs.lever.co/acme`, `https://jobs.eu.lever.co/acme`, `https://jobs.ashbyhq.com/acme`, `https://apply.workable.com/acme/`, `https://acme.workable.com`, `https://acme.recruitee.com`, `https://acme.jobs.personio.de` (or `.com`)
- an explicit board: `lever:acme`, `ashby:acme`, `workable:acme`, `recruitee:acme` or `personio:acme`
- a bare slug: `acme` (probed against Lever US, Lever EU, Ashby, Workable, Recruitee and Personio; every system with a board for it is tracked)

Options:

- `outputMode` — `all` (default) outputs every open job each run; `changesOnly` outputs only `new` and `removed` records.
- `includeDescriptions` — set to `false` to omit `descriptionText` for smaller output.
- `stateKey` (advanced) — separates change-tracking state when you run several independent schedules.
- `failOnEmpty` (advanced) — health-check mode: the run fails if any company is unresolved, errors, or returns zero jobs.

### Output

One dataset item per job:

```json
{
  "company": "https://jobs.lever.co/palantir",
  "ats": "lever",
  "boardSlug": "palantir",
  "jobId": "a1b2c3d4",
  "title": "Software Engineer",
  "department": "Engineering",
  "team": "Infrastructure",
  "location": "New York, NY",
  "workplaceType": "hybrid",
  "employmentType": "Full-time",
  "compensationText": "USD 150000–200000 per year",
  "descriptionText": "We build ...",
  "postedAt": "2026-09-30T12:00:00.000Z",
  "url": "https://jobs.lever.co/palantir/a1b2c3d4",
  "applyUrl": "https://jobs.lever.co/palantir/a1b2c3d4/apply",
  "changeType": "new",
  "firstSeenAt": "2026-10-11T06:00:00.000Z",
  "lastSeenAt": "2026-10-11T06:00:00.000Z",
  "scrapedAt": "2026-10-11T06:00:00.000Z"
}
```

The Actor also writes a `SUMMARY` record to the key-value store with one entry per input company: status (`ok` / `unresolved` / `error` / `skipped`, where `skipped` means your charge limit was reached before that company was checked), boards found, job counts, and duplicates.

### Pricing

You pay **per job record** (pay-per-event, one `job` event per dataset item): **$1.50 per 1,000 jobs**, with no charge for starting a run. For example, 1,000 job records cost $1.50. **Warning: the first run bills every open job; use `changesOnly` on scheduled runs** so later runs only bill jobs that appeared or disappeared since the previous run. Runs that find nothing for a company, and the `SUMMARY` record, are not billed.

### FAQ

#### Is it legal, and what data does it collect?

The Actor reads public job postings only: no login, no personal data. Each record has the job title, department, location, employment type, pay text where the employer published it, the description, dates and links back to the original posting. Recruiter fields are not included, and email addresses and phone numbers found in free text are replaced with `[redacted]`. Whether a particular use is right for you is your call; this is not legal advice. Employers can ask for exclusion (see Takedown below).

#### How does changeType work?

The Actor remembers the jobs it saw on each board. On the next run with the same `stateKey`, a job that is new is marked `new`, one still open is `existing`, and one that has disappeared is `removed`. The first run has nothing to compare against, so every open job is `new`. Removed records carry no description.

#### How do I schedule it daily?

Save your input as an Apify Task, then open Schedules in the Apify Console and add a daily cron expression for that task. Keep the same `stateKey` between runs so changes are tracked. Use a different `stateKey` for each independent company list.

#### How do I get alerts only on new jobs?

Set `outputMode` to `changesOnly`. After the first run, each run returns only `new` and `removed` records, so you are billed only for those. The Actor has no built-in alerts: run it on an Apify Schedule and connect email, Slack or a webhook to the run.

#### What if a company is not found?

Its entry in the `SUMMARY` record is marked `unresolved`, and you are not billed for it. Domain resolution is best effort, so try the board URL (`https://jobs.lever.co/acme`) or the explicit form (`ashby:acme`). The company may also use a system that is not supported.

#### Does it support Greenhouse or Workday?

No. Supported sources are Lever, Ashby, Workable, Recruitee and Personio. SmartRecruiters and Teamtailor are not supported either.

### Scheduling tips and limits

- **Domain resolution is best effort.** If you know the board, use its URL (`https://jobs.lever.co/acme` or `ashby:acme`) for certainty; bare domains may not resolve.
- **Personio boards are read from the `.de` host only.** A `.com` board URL is fetched from its `.de` twin, so a company that exists only on `jobs.personio.com` is reported as not found.
- Resolving domains takes about **1 to 3 seconds each** because of polite rate limits (at most one request per second per host), so large domain lists take minutes.
- **Removed jobs carry no description** — they are reconstructed from the stored snapshot, which omits `descriptionText` to keep state small.
- State is kept per board, so adding a company to your list does not reset tracking for the others.
- A board that errors mid-run keeps its previous state, so the next run replays its changes instead of losing them.

### Data and privacy

- Public job postings only — no login, no personal data.
- Email addresses and phone numbers found in free-text fields are replaced with `[redacted]`.
- Every record links to the original posting via `url` (and `applyUrl` where available).

### Disclaimer

Not affiliated with or endorsed by Lever, Ashby, Workable, Recruitee or Personio. Job content belongs to the posting employers.

### Takedown

Employers can request exclusion via the Issues tab; we honour all requests.

# Actor input Schema

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

The companies to track, one item per company. The easiest input is a company domain, e.g. ramp.com; board URLs (https://jobs.lever.co/acme, https://jobs.ashbyhq.com/acme, https://apply.workable.com/acme/, https://acme.recruitee.com or https://acme.jobs.personio.de) and explicit boards in the form <ats>:<slug> (lever:acme, ashby:acme, workable:acme, recruitee:acme or personio:acme) also work, and a bare slug (acme) is checked on all five systems. 1 to 500 items. Note: the first run bills every open job; use changesOnly on scheduled runs.

## `outputMode` (type: `string`):

What each run returns. 'all' lists every open job, e.g. for a one-off question; 'changesOnly' returns only new and removed jobs since the last run with the same stateKey.

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

Include the plain-text job description in each record. Turn it off to make results much smaller, which suits chat answers and summaries.

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

A label that separates change-tracking state when you run several independent schedules, e.g. sales-prospects. Leave the default unless you track different company lists on different schedules. 1 to 40 characters of lowercase a-z, 0-9 and '-'.

## `failOnEmpty` (type: `boolean`):

Health-check mode: the run fails if any company is unresolved, errors, or returns zero jobs, e.g. to catch a broken board on a canary schedule. Leave off for normal use.

## Actor input object example

```json
{
  "companies": [
    "https://jobs.lever.co/palantir",
    "ramp.com",
    "workable:huggingface"
  ],
  "outputMode": "all",
  "includeDescriptions": true,
  "stateKey": "default",
  "failOnEmpty": false
}
```

# Actor output Schema

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

One record per job, marked new, existing or removed.

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

Per-company status and counts for 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 = {
    "companies": [
        "https://jobs.lever.co/palantir",
        "ramp.com",
        "workable:huggingface"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("frostpine456/hiring-tracker").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": [
        "https://jobs.lever.co/palantir",
        "ramp.com",
        "workable:huggingface",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("frostpine456/hiring-tracker").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": [
    "https://jobs.lever.co/palantir",
    "ramp.com",
    "workable:huggingface"
  ]
}' |
apify call frostpine456/hiring-tracker --silent --output-dataset

```

## MCP server setup

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

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/nsYiE5Myb2feNEMF8/builds/s09m8Fg9JKRO4pnO9/openapi.json