# Company Jobs: Workday, Greenhouse, Lever, Ashby & more (`plainrecordlabs/company-jobs-feed`) Actor

Search open jobs by keyword across our daily index of company career sites, or list companies. Greenhouse, Lever, Ashby, Workable, Recruitee and Workday in one clean table, with new jobs only mode. Unofficial tool.

- **URL**: https://apify.com/plainrecordlabs/company-jobs-feed.md
- **Developed by:** [Plain Record Labs](https://apify.com/plainrecordlabs) (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.50 / 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.
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

## Company Jobs: Workday, Greenhouse, Lever, Ashby, Workable & Recruitee

Find open jobs straight from company career sites, in one clean table. Search by keyword across every company in our
daily index, or list the companies you care about. The data comes from the public job boards of **Greenhouse**,
**Lever**, **Ashby**, **Workable**, **Recruitee** and **Workday**, the hiring systems behind thousands of careers
pages.

Type a few title keywords and press Start. Or paste careers links. You get one row per open job, with the same fields
whatever system the company uses. Turn on **Only new jobs** and schedule it daily to get just the postings that
appeared since your last run.

> This is an unofficial tool, not affiliated with any of these companies. It reads only the public job listings
> employers publish on their career sites and job boards. No logins and no private data.

### Two ways to use it

**1. Search by keyword (no company list needed).** Leave **Companies** empty and add **Title keywords** such as
`data engineer` or `account executive`. The Actor searches our daily index of company job boards and returns matches,
newest first, with the date we first saw each job and how many days it has been open. The index is rebuilt once a
day. It covers a growing list of employers, mostly larger US companies today, so it will not have every company. For
Workday employers the index keeps each employer's 100 newest jobs. If a company you need is missing, or you need
every job at one company, list it directly (mode 2), which reads the board live and in full.

**2. List companies.** Add board URLs, `ats:slug` pairs, careers pages or plain company names to **Companies**. The
Actor reads those boards live at run time.

### What people use it for

- **Hiring signals:** see when target accounts open new roles, for sales prospecting, investing or competitor research.
- **Job boards and newsletters:** keep a niche board or a weekly jobs email filled with fresh postings.
- **Recruiting and market research:** compare titles, locations, remote policy and published salary ranges.
- **Your own job search:** follow a shortlist of companies and see only what's new.

### Input

| Field | What it does |
|---|---|
| **Title keywords** | Keep jobs whose title contains any of these words. With no companies listed, these search the whole index. |
| **Location keywords** | Keep jobs whose location contains any of these, like `Remote` or `London`. |
| **Remote jobs only** | Keep only jobs marked remote. |
| **Only jobs that publish a pay range** | Keep only postings with a salary range or pay text, which is more common where pay-transparency laws apply. |
| **Companies (optional)** | One per line. A board URL (`https://boards.greenhouse.io/airbnb`, `https://jobs.lever.co/spotify`, `https://jobs.ashbyhq.com/ramp`, `https://apply.workable.com/huggingface`, `https://bunq.recruitee.com`, `https://cisco.wd5.myworkdayjobs.com/Cisco_Careers`), an `ats:slug` pair (`greenhouse:airbnb`, `lever:plaid`, `ashby:ramp`, `workable:huggingface`, `recruitee:bunq`), a company's own careers page (the Actor looks for a board linked there), or a plain company name like `notion` (the Actor tries Greenhouse, Lever, Ashby, Workable and Recruitee). |
| **First seen within (days)** | Search mode: only jobs our index first saw in the last N days. |
| **Max results** | Search mode: a cap on how many jobs one run returns, newest first. |
| **Only jobs not seen in my earlier runs** | Returns only new postings. The first run returns everything it finds and remembers it. |
| **Include job description text** | Company list mode: adds the plain-text description. Not available for Workday. |
| **Max jobs per company** | Company list mode: a cap per company. 0 means all. |

### Output

One item per job:

```json
{
  "company": "Cisco",
  "title": "System Hardware Board Design Engineering Lead (Onsite)",
  "location": "Milpitas, California, US",
  "allLocations": ["Milpitas, California, US"],
  "remote": false,
  "employmentType": "Full time",
  "salaryMin": null,
  "salaryMax": null,
  "salaryCurrency": null,
  "publishedAt": null,
  "postedText": "Posted Today",
  "firstSeenAt": "2026-10-23",
  "daysOpen": 0,
  "url": "https://cisco.wd5.myworkdayjobs.com/Cisco_Careers/job/Milpitas-California-US/System-Hardware-Board-Design-Engineering-Lead--PCB---Onsite-_2026365",
  "ats": "workday",
  "companySlug": "cisco",
  "jobId": "Cisco_Careers:2026365",
  "jobKey": "workday:cisco:Cisco_Careers:2026365"
}
```

`firstSeenAt` and `daysOpen` come from our daily index (search mode), so they count from the day we first saw the
job, not the day it was posted. Workday does not publish a date in its job list, so Workday jobs carry its own text
(`postedText`, like "Posted 3 Days Ago") instead of `publishedAt`. Salary fields are filled when the company publishes
a range: common on Greenhouse, Ashby, Lever and Recruitee, missing on Workable and Workday lists.

Each run also saves a `SUMMARY` record in its key-value store, with how many jobs matched and, in company list mode,
which board was found for each company and why a company wasn't found.

### Daily new-job alerts

1. Turn on **Only jobs not seen in my earlier runs**.
2. Save the input as a Task and add an Apify **Schedule**, for example every morning.
3. Connect the Task to email, Slack, Google Sheets or a webhook with Apify integrations.

The list of jobs you've already seen is kept in a key-value store in **your own** Apify account
(`company-jobs-feed-state`), so nobody else's runs affect yours.

### Good to know

- Company list mode covers boards on Greenhouse, Lever, Ashby, Workable, Recruitee and Workday. Companies on iCIMS,
  SmartRecruiters and others show up as not found in the SUMMARY, and you aren't charged for them.
- Workday is read gently from each employer's public career site: one request per second, the site's robots.txt is
  followed, and if a site pushes back the Actor stops for that employer instead of retrying. Large Workday employers
  take about a minute each in company list mode.
- A company that has switched off its public job feed is skipped and noted in the SUMMARY.
- Some careers pages build their job list with scripts and don't link the board in the page itself. For those, use
  the board URL or the `ats:slug` form.

### Pricing

You pay per job returned. The price is on the Pricing tab. A company that isn't found, or a run with no new jobs,
costs only the small platform start fee. In search mode, **Max results** caps what one run can cost.

### Feedback

Is there a company it misses, or a field you need? Open an issue on the Issues tab. Replies come from our AI
assistant.

# Actor input Schema

## `titleKeywords` (type: `array`):

Keep only jobs whose title contains any of these words (case-insensitive). With no companies listed, these keywords search every company in our daily index.

## `locationKeywords` (type: `array`):

Keep only jobs whose location contains any of these (e.g. Remote, London, New York). Empty = all locations.

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

Keep only jobs the board marks remote (or whose location says Remote).

## `salaryOnly` (type: `boolean`):

Keep only jobs whose posting includes a salary range or pay text (common where pay-transparency laws apply).

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

Leave empty to search our daily index of company job boards. Or list companies, one per line: a job-board URL (boards.greenhouse.io/stripe, jobs.lever.co/spotify, jobs.ashbyhq.com/ramp, apply.workable.com/huggingface, bunq.recruitee.com, cisco.wd5.myworkdayjobs.com/Cisco_Careers), an ats:slug pair (greenhouse:airbnb, lever:plaid, ashby:ramp, workable:huggingface, recruitee:bunq), a company careers page URL (the Actor looks for a supported board linked there), or a plain company slug (the Actor tries Greenhouse, Lever, Ashby, Workable and Recruitee).

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

Search mode only: keep jobs our index first saw within this many days. 0 = any age.

## `maxResults` (type: `integer`):

Search mode only: return at most this many jobs, newest first. 0 = no limit.

## `onlyNew` (type: `boolean`):

Remembers job IDs between your runs (in your own key-value store) and returns only new postings. Pair with an Apify schedule for daily new-job alerts. The first run returns everything and records it.

## `includeDescription` (type: `boolean`):

Company list mode only: adds the plain-text job description (not available for Workday or in search mode).

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

Company list mode only: stop after this many jobs per company (0 = no limit).

## Actor input object example

```json
{
  "titleKeywords": [
    "data engineer"
  ],
  "locationKeywords": [],
  "remoteOnly": false,
  "salaryOnly": false,
  "companies": [],
  "postedWithinDays": 0,
  "maxResults": 20,
  "onlyNew": false,
  "includeDescription": false,
  "maxJobsPerCompany": 0
}
```

# Actor output Schema

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

One item per open job, in the same schema for Greenhouse, Lever, Ashby, Workable, Recruitee and Workday.

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

Per company: the board found, jobs open and returned, and why a company was not found.

# 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 = {
    "titleKeywords": [
        "data engineer"
    ],
    "maxResults": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("plainrecordlabs/company-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 = {
    "titleKeywords": ["data engineer"],
    "maxResults": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("plainrecordlabs/company-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 '{
  "titleKeywords": [
    "data engineer"
  ],
  "maxResults": 20
}' |
apify call plainrecordlabs/company-jobs-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,plainrecordlabs/company-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/1hdPPgLWlR6AB6CBd/builds/nFnflzX6NmtUS2OsQ/openapi.json