# Workable Jobs Scraper - Every Opening From Any Workable Board (`practical_ophthalmologist_iuq/workable-jobs-scraper`) Actor

A company that is hiring is a company that is spending. Pull live openings from any Workable careers page via the official public API - paste company domains, no board slugs to look up. Department, location, apply link.

- **URL**: https://apify.com/practical\_ophthalmologist\_iuq/workable-jobs-scraper.md
- **Developed by:** [Scrappeer](https://apify.com/practical_ophthalmologist_iuq) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Workable Jobs Scraper - Every Opening From Any Workable Board

**Pull live job openings straight from any Workable careers board via the official public API. Give it company slugs, get every role with title, team, location, commitment and apply link. No proxy, no API key.**

***

### What it does

Give it a list of Workable board tokens. It calls the official public Workable
board API for each one and returns every live opening in a flat,
spreadsheet-ready schema.

This reads the API Workable already publishes for its customers' own careers
pages. That means **no proxy, no headless browser, no anti-bot arms race** — and
nothing that silently breaks when a page layout changes.

Workable exposes team, commitment and workplace type, so `team`, `employmentType` and `workplaceType` are usually populated.

***

### Input

```json
{
  "boards": ["huggingface"],
  "titleKeywords": ["engineer"],
  "locations": ["Remote"],
  "postedWithinDays": 7
}
```

The board token is **the company slug in apply.workable.com/<company>**. You can paste the full careers URL instead
and it will pull the token out for you.

| Field | Default | Notes |
|---|---|---|
| `boards` | — | Required. Tokens or full careers URLs. |
| `titleKeywords` | — | Keep only titles containing any of these. |
| `excludeKeywords` | — | Drop titles or departments matching any of these. |
| `locations` | — | Keep only matching locations. |
| `departments` | — | Matches department **or** team. |
| `remoteOnly` | `false` | Remote positions only. |
| `postedWithinDays` | `0` | `0` = no limit. Set `1` for a daily new-jobs feed. |
| `includeDescription` | `false` | Adds full description text. Much larger results. |
| `maxJobsPerBoard` | `0` | `0` = no limit. |
| `concurrency` | `5` | Boards fetched in parallel. |

***

### Output

One row per opening:

| Field | Description |
|---|---|
| `companyName`, `boardToken`, `ats` | Who, and where it was read from |
| `jobId` | Stable ID on Workable |
| `title` | Job title |
| `department`, `team` | Org placement |
| `employmentType` | Full-time, contract, intern… |
| `location`, `isRemote`, `workplaceType` | Where the work happens |
| `salary` | Compensation range, when published |
| `publishedAt`, `updatedAt` | ISO 8601 timestamps |
| `jobUrl`, `applyUrl` | Public posting and application links |
| `description` | Full text, only when requested |

Export as **Excel, CSV, JSON or XML**, or pull it through the API.

A board that cannot be found returns one row with an `error` and a hint, so a bad
token never silently vanishes from your results.

***

### Daily new-jobs feed

Schedule it once a day with `postedWithinDays: 1` and you get a clean feed of
roles opened in the last 24 hours across every board you track. Wire it to Slack,
Google Sheets or your CRM through Apify integrations.

***

### Quality notes

- Timestamps are normalised to ISO 8601, so date filters behave predictably.
- Postings that cannot be read are skipped and **reported in the log** rather
  than quietly dropped — and you are not billed for them.
- One malformed posting never takes down the rest of the board.

***

### Limits

- Workable boards only. For a company on a different platform, see the
  multi-platform version of this Actor.
- Boards set to private or password-protected are not accessible.
- `department` and `team` are only as good as what the company fills in.

***

### Support

A board that will not resolve? Open an issue on the **Issues** tab with the
careers URL.

# Actor input Schema

## `boards` (type: `array`):

Company domains, names, or careers URLs - paste your list as-is. acme.com, www.acme.com and the full board URL all work. The board token is the company slug in apply.workable.com/<company>.

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

Keep only jobs whose title contains any of these.

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

Drop jobs whose title or department matches any of these.

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

Keep only jobs whose location matches any of these.

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

Keep only jobs in a matching department or team.

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

Return only remote positions.

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

Only jobs posted in the last N days. 0 means no limit. Set 1 for a daily new-jobs feed.

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

Add the full job description text. Makes results much larger.

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

jobs = one row per opening. companies = one row per board: how many roles are open, which teams are growing, what opened since your last run - built for account lists rather than job lists. both = job rows followed by the summaries.

## `onlyNewSinceLastRun` (type: `boolean`):

Return only jobs that opened since your last run (isNew) and jobs that have since closed (isClosed). The first run records a baseline and returns everything. Built for a daily schedule: a run with no changes returns nothing and costs only the start fee. Changing the boards or filters starts a fresh baseline.

## `maxJobsPerBoard` (type: `integer`):

Cap results per board. 0 means no limit. Starts at 10 so a first trial run stays cheap - clear it to get everything.

## `concurrency` (type: `integer`):

How many boards to fetch in parallel.

## Actor input object example

```json
{
  "boards": [
    "huggingface.co"
  ],
  "remoteOnly": false,
  "postedWithinDays": 0,
  "includeDescription": false,
  "outputMode": "jobs",
  "onlyNewSinceLastRun": false,
  "maxJobsPerBoard": 10,
  "concurrency": 5
}
```

# 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 = {
    "boards": [
        "huggingface.co"
    ],
    "maxJobsPerBoard": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("practical_ophthalmologist_iuq/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 = {
    "boards": ["huggingface.co"],
    "maxJobsPerBoard": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("practical_ophthalmologist_iuq/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 '{
  "boards": [
    "huggingface.co"
  ],
  "maxJobsPerBoard": 10
}' |
apify call practical_ophthalmologist_iuq/workable-jobs-scraper --silent --output-dataset

```

## MCP server setup

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