# Workable Jobs Scraper — Any Workable Careers Page | $1/1K (`steadyrow/workable-jobs`) Actor

Scrape every open job from any Workable careers page: paste an apply.workable.com URL or the account name. Official public widget API, no proxy. Employment type, remote flag, filters by keyword, location, department, and a monitor mode that returns only new jobs.

- **URL**: https://apify.com/steadyrow/workable-jobs.md
- **Developed by:** [Steadyrow](https://apify.com/steadyrow) (community)
- **Categories:** Jobs, 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 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

## Workable Jobs Scraper — Any Workable Careers Page | $1/1K

**Paste a Workable careers page, get every open job as clean JSON. $1 per 1,000 jobs.**

Many companies publish their jobs on Workable (`apply.workable.com/<company>`). This Actor reads Workable's **official public widget API** — the endpoint Workable documents for showing published jobs on a website — and returns every posting with title, department, all locations, employment type, remote flag, publish date and the full description, in one request per company.

- ✅ **Any Workable account** — `apply.workable.com/<company>`, a job URL of that company, the API URL, or just the account name (`katmai`)
- ✅ **One row per job** — Workable lists a job once per location; we merge them and put every location into `locations`
- ✅ **Monitor mode** — schedule it daily and only pay for jobs you have not received before
- ✅ **No browser, no proxy, no login** — one plain HTTPS request per company, so it is fast and stable
- ✅ **Filters** — keywords, excluded words, location, remote, department, posted within N days
- ✅ **No personal data** — no recruiter names or contacts; e-mail addresses inside descriptions are removed

> Need Greenhouse, Lever, Ashby, Workday, Personio and more in the same run? Use the combined [ATS Jobs API](https://apify.com/steadyrow/ats-jobs). This Actor is the Workable-only version with inputs built for Workable.

### What can I use it for?

- **Job boards and aggregators** — pull all the Workable companies you track into one feed
- **Job alerts** — daily monitor run → Slack, e-mail or Google Sheets with only the new roles
- **Hiring signals for sales and recruiting** — which departments a company is growing, and in which countries
- **Labour-market research** — roles by country, employment type and remote policy
- **AI agents** — a typed job feed your agent can call through the Apify API or MCP

### Input

```json
{
    "accounts": [
        "https://apply.workable.com/european-dynamics/",
        "katmai",
        "workable:huggingface"
    ],
    "keywords": [
        "engineer",
        "manager"
    ],
    "excludeKeywords": [
        "intern"
    ],
    "locations": [
        "United States",
        "Greece"
    ],
    "departments": [
        "Operations"
    ],
    "postedWithinDays": 60,
    "maxItemsPerSource": 200,
    "monitorMode": false
}
```

| Field | What it does |
|---|---|
| `accounts` | **Required.** One per line: a careers page URL (`https://apply.workable.com/european-dynamics/`), a job URL of that company, the account name (`katmai` or `workable:katmai`) or a company careers page that links to its Workable page. Entries that belong to another ATS are skipped with a note in the log. |
| `keywords` | Keep jobs whose **title** contains any of these words (whole word, case-insensitive). Turn on `searchInDescription` to search the description too. |
| `excludeKeywords` | Drop jobs whose title contains any of these words. |
| `locations` | Keep jobs whose location or country contains one of these words. `remote` matches remote jobs. |
| `departments` | Keep jobs whose Workable department contains one of these strings. |
| `postedWithinDays` | Only jobs published in the last N days. |
| `maxItemsPerSource` / `maxItems` | Limits per account / per run (0 = no limit). |
| `includeDescription`, `includeDescriptionHtml` | Plain-text and/or HTML description. |
| `monitorMode`, `monitorStateName` | Output only jobs not delivered before; name of the store that remembers them. |

#### Finding the account name

Open the company's job listing: the address looks like `https://apply.workable.com/<account>/j/<code>/`. The `<account>` part is what you need (Workable accounts are lower-case; we lower-case what you type). Links of the form `https://apply.workable.com/j/<code>` do **not** contain the account name — find the company's page `apply.workable.com/<account>` instead. If you only have the company's own website, paste its careers page: the Actor looks for a link to `apply.workable.com/<account>` in it (some company sites block automated requests, and some link only to individual jobs; then paste the Workable page).

### Output

One item per job:

```json
{
    "job_id": "workable:katmai:6B2D05460E",
    "ats": "workable",
    "company": "Katmai",
    "company_board_id": "katmai",
    "title": "Administrative Assistant",
    "department": "Operations",
    "team": null,
    "location": "Fort Sam Houston, Texas, United States",
    "locations": [
        "Fort Sam Houston, Texas, United States"
    ],
    "country": "US",
    "remote": false,
    "workplace_type": null,
    "employment_type": "FULL_TIME",
    "posted_at": "2026-08-19T00:00:00.000Z",
    "updated_at": null,
    "salary_min": null,
    "salary_max": null,
    "salary_currency": null,
    "salary_period": null,
    "salary_source": null,
    "description_text": "SUMMARY\n\nProvides administrative, clerical, and office management support to the Soldier Recovery Unit (SRU) command section…",
    "apply_url": "https://apply.workable.com/j/6B2D05460E/apply",
    "source_url": "https://apply.workable.com/j/6B2D05460E",
    "input": "workable:katmai",
    "scraped_at": "2026-10-20T17:29:58.586Z"
}
```

Workable-specific notes:

- `job_id` is `workable:<account>:<shortcode>` and stays the same between runs.
- `country` is the two-letter country code Workable gives (`US`, `GR`); the readable country is part of `location`.
- `remote` is `true` when the posting allows remote work (Workable's "telecommuting" flag) and `false` otherwise. Workable does not say whether an on-site job is hybrid, so `workplace_type` is `remote` for remote jobs and `null` for the rest.
- `posted_at` is Workable's publish date (day precision, midnight UTC). `updated_at` and `team` are always `null` — Workable does not publish them.
- Workable has no salary field. `salary_*` is filled only when a pay range is written in the description (`salary_source: "description"`); otherwise all salary fields are `null`. Most Workable postings state none — none of the 66 jobs in our main test did.
- A run summary (per account: listed / output / errors) is saved as `SUMMARY` in the default key-value store. An unknown account is reported there and in the log; the other accounts still run.

### Monitor mode: only new jobs

1. Turn on **Monitor mode** and save the input as a task.
2. Add a schedule (for example every morning).
3. The first run returns all matching jobs. Every later run returns only jobs not delivered before — and you pay only for those.

Delivered IDs are kept per account in the named key-value store `workable-jobs-monitor` (change it with `monitorStateName` if you run several independent monitors). In our tests a second run on the same accounts returned 0 jobs, and after forgetting 9 delivered jobs a third run returned exactly those 9.

### Pricing

Pay per event:

| Event | Price |
|---|---|
| Job in the dataset | **$0.001** ($1 per 1,000 jobs) |
| Actor start | $0.002 per run |

Examples: 1,000 jobs ≈ $1. A daily monitor on 20 accounts that finds 30 new jobs ≈ $0.03 + $0.002 per day. Jobs removed by your filters or already delivered in monitor mode are not charged. Set **Maximum cost per run** and the Actor stops cleanly at the limit.

### FAQ

**How many jobs can it get?** All published jobs of an account, in one request. In our tests European Dynamics listed 167 open jobs, Katmai 70 and Hugging Face 6.

**Is it legal?** The Actor reads job postings that companies publish on Workable's public widget API, without logging in and without bypassing any protection. No recruiter or candidate data is collected. You are responsible for how you use the data.

**An account returns "not found".** The account name is probably wrong or the company has left Workable. Open `https://apply.workable.com/<account>` in a browser to check.

**Can I paste a company's own careers page?** Yes, if the page links to `apply.workable.com/<account>` (it worked for huggingface.co in our test). Pages that only link to single jobs (`apply.workable.com/j/<code>`) do not name the account, so paste the Workable page instead.

# Actor input Schema

## `accounts` (type: `array`):

One per line. Paste a careers page URL (https://apply.workable.com/european-dynamics/), a job URL (the whole company is scraped), the account name (`katmai` or `workable:katmai`), or a company careers page that embeds a Workable board.

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

Keep jobs whose title contains at least one of these words (whole-word, case-insensitive). Leave empty to keep all.

## `searchInDescription` (type: `boolean`):

By default keywords are matched against the job title only.

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

Drop jobs whose title contains any of these words (e.g. Senior, Intern).

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

Keep jobs whose location, any of their locations, or country contains one of these words (whole-word, case-insensitive; e.g. London, Germany, US). Use `remote` to match remote jobs.

## `remote` (type: `string`):

Filter by remote eligibility.

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

Keep jobs whose Workable department contains one of these strings (e.g. Engineering).

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

Only jobs published in the last N days (Workable gives the publish date). 0 = no limit.

## `maxItemsPerSource` (type: `integer`):

Stop after this many jobs from one board. 0 = all jobs.

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

Stop the whole run after this many jobs. 0 = no limit.

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

Adds `description_text` (the full job text as plain text).

## `includeDescriptionHtml` (type: `boolean`):

Adds `description_html` (cleaned original HTML).

## `monitorMode` (type: `boolean`):

Remembers every job already delivered (per board) and outputs only jobs you have not received before. The first run outputs all matching jobs. Ideal for a daily schedule — you only pay for new jobs.

## `monitorStateName` (type: `string`):

Name of the key-value store that keeps the list of delivered jobs. Use a different name per task if you run several independent monitors.

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

Detail requests run in parallel up to this number. Requests to one ATS host are additionally limited to about 4 per second.

## Actor input object example

```json
{
  "accounts": [
    "https://apply.workable.com/huggingface/",
    "katmai"
  ],
  "searchInDescription": false,
  "remote": "any",
  "postedWithinDays": 0,
  "maxItemsPerSource": 20,
  "maxItems": 0,
  "includeDescription": true,
  "includeDescriptionHtml": false,
  "monitorMode": false,
  "monitorStateName": "workable-jobs-monitor",
  "maxConcurrency": 4
}
```

# Actor output Schema

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

All Workable job postings collected in this run, one row per job.

# 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 = {
    "accounts": [
        "https://apply.workable.com/huggingface/",
        "katmai"
    ],
    "maxItemsPerSource": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("steadyrow/workable-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 = {
    "accounts": [
        "https://apply.workable.com/huggingface/",
        "katmai",
    ],
    "maxItemsPerSource": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("steadyrow/workable-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 '{
  "accounts": [
    "https://apply.workable.com/huggingface/",
    "katmai"
  ],
  "maxItemsPerSource": 20
}' |
apify call steadyrow/workable-jobs --silent --output-dataset

```

## MCP server setup

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