# Workable Jobs Scraper: Company Boards & Departments (`arman-bd/workable-jobs-scraper`) Actor

Extract public jobs from any Workable careers page. title, department, location, employment type, remote status and description. No login, no proxy, no browser.

- **URL**: https://apify.com/arman-bd/workable-jobs-scraper.md
- **Developed by:** [Arman Hossain](https://apify.com/arman-bd) (community)
- **Categories:** Jobs, Lead generation, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.74 / 1,000 job scrapeds

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

## Workable Jobs Scraper: Company Boards & Departments

![Workable Jobs Scraper: Every opening on any Workable careers page, title, department, location, employment type and the full description](https://api.apify.com/v2/key-value-stores/ZQOcNAOHrIgTacAmy/records/workable-jobs-scraper.jpg)

**Workable Jobs Scraper** pulls every public opening from any **Workable**-hosted careers page, title, department, location, employment type, remote flag, publish date, apply link and the full plain-text description.

Workable powers the hiring of tens of thousands of small and mid-size companies, and every account publishes its openings for programmatic use. The Actor needs nothing configured to reach them: **no browser, no proxy, no login.**

**Agent skill: [SKILL.md](https://api.apify.com/v2/key-value-stores/t7YoTxpZEJOWvw4Ug/records/workable-jobs-scraper.md)**

```
https://api.apify.com/v2/key-value-stores/t7YoTxpZEJOWvw4Ug/records/workable-jobs-scraper.md
```

### What you get

| Output field | Meaning |
|---|---|
| `account`, `company` | Account slug used, and the company name as Workable reports it |
| `shortcode` | Workable's stable per-job code, also the last segment of the apply URL |
| `title` | Job title |
| `department` | Department the role sits in, when the board fills one in |
| `location`, `country`, `city` | Composed location string plus the structured parts |
| `employmentType` | Full-time, Part-time, Contract, Temporary, Internship |
| `isRemote` | Workable's telecommuting flag |
| `publishedAt` | Publish date (falls back to creation date) |
| `applyUrl` | Direct apply link |
| `description` | Full description as clean plain text, HTML stripped, entities decoded |
| `scrapedAt` | Run timestamp |

A `RUN_SUMMARY` record in the key-value store holds per-run counts, the filters used, any account that failed, and any account the cap left no room for.

### Common use cases

- **Aggregate SME hiring across a region.** Workable's customer base skews to companies too small to appear on enterprise boards.
- **Feed a local job board.** One scheduled run refreshes every listing you syndicate.
- **Track departmental growth at private companies.** Department plus publish date shows where headcount is going.
- **Lead generation.** A company hiring for a role is a company buying for it.
- **Labour-market research.** Measure hiring volume by country, department or employment type over time.

### Quick start

Two accounts, everything they have (up to the default 1,000-row cap):

```json
{
 "accounts": ["azumo", "weetabix"]
}
```

Remote engineering roles only, capped:

```json
{
 "accounts": ["azumo", "https://apply.workable.com/weetabix/"],
 "searchTerms": ["engineer", "developer"],
 "departmentFilter": ["engineering"],
 "remoteOnly": true,
 "maxJobs": 50
}
```

Fast, lightweight sweep for change detection:

```json
{
 "accounts": ["azumo"],
 "includeDescription": false
}
```

### Input

| Field | Type | Default | Notes |
|---|---|---|---|
| `accounts` | array | - | **Required.** Account slugs (`azumo`) or full `apply.workable.com` URLs. Mixed input is fine, URLs are normalised to slugs automatically. |
| `searchTerms` | array | `[]` | Keep only titles containing one of these terms (case-insensitive). Empty = all. |
| `departmentFilter` | array | `[]` | Keep only departments matching one of these terms. Empty = all. |
| `remoteOnly` | boolean | `false` | Keep only roles Workable flags as remote. |
| `maxJobs` | integer | `1000` | Cap on the jobs saved by the **whole run**, applied **after** filtering. The allowance is shared evenly across the accounts so no single board crowds out the rest, and whatever the smaller boards leave unused goes to the accounts that had more — the run never stops short of the cap while jobs remain. `0` = no limit. The earlier name `maxJobsPerAccount` is still honoured and means this same run-wide total; when both are given, the tighter one applies. |
| `includeDescription` | boolean | `true` | Include the full plain-text description. Turn off for a much smaller, faster dataset. |

The filters combine with AND: a job must match at least one term in *each* non-empty filter, and satisfy `remoteOnly` if set. `departmentFilter` only helps on boards that actually fill in departments, many small accounts leave the field empty, so start without it.

### Output example

```json
{
 "account": "weetabix",
 "company": "Weetabix",
 "shortcode": "20459A707F",
 "title": "Compliance Engineer",
 "department": "Engineering",
 "location": "Burton Latimer, England, United Kingdom",
 "country": "United Kingdom",
 "city": "Burton Latimer",
 "employmentType": "Full-time",
 "isRemote": false,
 "publishedAt": "2026-07-15",
 "applyUrl": "https://apply.workable.com/j/20459A707F/apply",
 "description": "We are Weetabix. Home to the UK's favourite breakfast cereal …",
 "scrapedAt": "2026-08-06T12:00:00.000Z"
}
```

### Finding an account slug

Open a company's Workable careers page and look at the URL:

| URL you see | Slug |
|---|---|
| `apply.workable.com/acme/` | `acme` |
| `apply.workable.com/acme/j/AB12CD34EF/` | `acme` |
| `acme.workable.com` | `acme` |

You can paste the whole URL, the Actor extracts the slug itself. If a company's careers page is on its own domain, view source and search for `workable.com`; the slug is almost always in an iframe or fetch URL.

### API example

```bash
curl -X POST "https://api.apify.com/v2/acts/arman-bd~workable-jobs-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \
 -H "Content-Type: application/json" \
 -d '{
 "accounts": ["azumo"],
 "searchTerms": ["engineer"],
 "maxJobs": 25
 }'
```

### JavaScript example

```js
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('arman-bd/workable-jobs-scraper').call({
 accounts: ['azumo', 'weetabix'],
 searchTerms: ['engineer'],
 remoteOnly: true,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
for (const job of items) console.log(`${job.company}, ${job.title} (${job.location})`);
```

### Limits and behaviour

- **The cap binds the run, not each account.** `maxJobs` is the most rows a run can deliver, and therefore the most it can charge for. The allowance is shared evenly so one large board cannot crowd out the others, and any share the smaller boards leave unused is handed to the accounts that had more, so you are never short-changed by a cap that was never going to bind. Accounts the cap left no room for are listed in `RUN_SUMMARY.accountsSkipped` rather than quietly returning nothing. An out-of-range value (negative, fractional, or not a number) is refused before anything is fetched; it is never read as "no limit".
- **A job is saved once per run.** A `shortcode` is unique across Workable, so a role reachable through two of the accounts you listed is delivered — and charged — once. The drops are counted in `RUN_SUMMARY.duplicatesSkipped`.
- **Bad accounts don't kill the run.** An unknown slug is recorded in `RUN_SUMMARY.failures` and the run continues; the Actor only errors out if *every* account fails.
- **Transient errors are retried** a few times with exponential backoff before the account is recorded as failed. A slug that does not exist is final for that account.
- **Multi-location roles are collapsed.** Workable lists a job once per location, so a role open in five countries arrives five times under one `shortcode`. The Actor de-duplicates on `shortcode` and keeps the row carrying the complete location list. You get one dataset record per real vacancy.
- **Descriptions are decoded twice.** Job authors paste already-encoded markup into Workable's editor, so entities are decoded before tags are stripped and again afterwards. You get real text, not `<p>`.
- **Public data only.** No authentication, no personal data, no access-control bypass.

### FAQ

**Do I need a Workable API key?** No. You supply no credentials.

**Do I need a proxy?** No. Proxy configuration is not required to run this Actor.

**Does it include salary?** Only if the company writes it into the description, Workable publishes no structured salary field, and this Actor does not invent one.

**Why is `department` null?** Departments are optional in Workable and many smaller accounts never set them. Filter on `searchTerms` instead when that happens.

**What happens if an account is unavailable?** It is reported in `RUN_SUMMARY.failures` and the run continues with the remaining accounts.

**Can I get only new or changed jobs?** Run on a schedule and diff on `shortcode` plus `publishedAt`. Setting `includeDescription: false` makes those sweeps much cheaper.

**Can I integrate it with something else?** Yes, Apify API, client libraries, webhooks, scheduled runs, dataset exports (JSON/CSV/Excel) or MCP. Output is structured JSON.

# Actor input Schema

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

Account slugs or apply.workable.com URLs. The slug is the path segment after apply.workable.com. for https://apply.workable.com/azumo/ the slug is 'azumo'. Full URLs are accepted and normalized automatically.

## `searchTerms` (type: `array`):

Keep only jobs whose title contains at least one of these terms (case-insensitive). Leave empty to keep every job.

## `departmentFilter` (type: `array`):

Keep only jobs whose department matches at least one of these terms (case-insensitive). Leave empty for all departments. Not every Workable board fills in departments.

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

Keep only jobs Workable flags as remote (the board's telecommuting flag).

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

Cap the total number of jobs saved across every account in the run, applied after filtering. The allowance is shared evenly across the accounts so no single board crowds out the rest, and whatever the smaller boards leave unused goes to the accounts that had more, so a run never stops short of the cap while jobs remain. Set 0 for no limit. The earlier name maxJobsPerAccount is still honoured and means this same run-wide total; when both are given, the tighter one applies.

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

Include the full job description as plain text. Disable for a smaller, faster dataset.

## Actor input object example

```json
{
  "accounts": [
    "azumo",
    "https://apply.workable.com/weetabix/"
  ],
  "searchTerms": [
    "engineer",
    "designer"
  ],
  "departmentFilter": [
    "engineering"
  ],
  "remoteOnly": false,
  "maxJobs": 1000,
  "includeDescription": true
}
```

# Actor output Schema

## `items` (type: `string`):

Every record the run produced.

## `runsummary` (type: `string`):

The RUN_SUMMARY record from the run's key-value store.

# 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": [
        "azumo",
        "weetabix"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("arman-bd/workable-jobs-scraper").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": [
        "azumo",
        "weetabix",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("arman-bd/workable-jobs-scraper").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": [
    "azumo",
    "weetabix"
  ]
}' |
apify call arman-bd/workable-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,arman-bd/workable-jobs-scraper"
        }
    }
}
```

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/uPDr5D3UBnvCBkUvC/builds/n4IlfRc5Ga1ZTedjS/openapi.json