# Workable Jobs Scraper & New Job Alerts (`sysco32/workable-jobs-monitor`) Actor

Scrape all open jobs from any Workable careers page (apply.workable.com/<company>) via Workable's public jobs widget API: departments, functions, locations, remote flag, employment type, full descriptions. Filters and an only-new-jobs monitoring mode.

- **URL**: https://apify.com/sysco32/workable-jobs-monitor.md
- **Developed by:** [Gabor Sziladi](https://apify.com/sysco32) (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 job results

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 & New Job Alerts

Scrape **every open job from any Workable career site** into a clean dataset: title, department, team, locations, remote flag, employment type, posting date, apply link, full plain-text description, and more. The Actor uses Workable's public **jobs widget API** (`apply.workable.com/api/v1/widget/accounts/<company>`), the same endpoint that powers every `apply.workable.com` careers page and embedded Workable job widget. It's fast, reliable and cheap: **$1.50 per 1,000 jobs**.

Turn on **Only new jobs** and schedule the Actor to get a daily feed of new Workable postings, paying only for the new ones.

- ✅ Paste Workable URLs or just company slugs
- ✅ All open jobs, one normalised record per job
- ✅ Filters: keywords, exclude keywords, locations, remote only, posted within N days
- ✅ **Only new jobs** monitoring mode for alerts, webhooks, Slack, Google Sheets, Zapier or Make
- ✅ One broken company never fails the run; errors are listed in the `OUTPUT` summary
- ✅ No login, no proxies, no browser. Polite, rate-limited requests to the official endpoint.

> **Need other ATS platforms too?** The all-in-one [ATS Jobs Scraper (sysco32/ats-jobs-feed)](https://apify.com/sysco32/ats-jobs-feed) covers **9 platforms** (Greenhouse, Lever, Ashby, Workday, SmartRecruiters, Workable, Recruitee, Personio and Teamtailor) and auto-detects the ATS from any careers URL.

### What data you get

Workable publishes department, function, all locations, a remote (telecommuting) flag, employment type, the publication date and the full description in a single request per company, so runs are very fast. Workable's public widget does not publish salary.

| Field | Example |
|---|---|
| `company`, `company_slug` | Company name and Workable identifier |
| `job_id`, `requisition_id` | Stable IDs for deduplication |
| `title`, `department`, `team` | Job title and organisation |
| `location`, `locations[]`, `remote`, `workplace_type` | All locations plus remote / hybrid / onsite |
| `employment_type` | Full-time, part-time, contract… when published |
| `posted_at`, `updated_at` | ISO 8601 UTC |
| `salary` | `{min, max, currency, period, text}` when published |
| `job_url`, `apply_url` | Direct links |
| `description_text` (+ optional `description_html`) | Full job description |

### Input example

```json
{
  "companies": [
    "https://apply.workable.com/huggingface",
    "skroutz",
    "blueground",
    "upstream"
  ],
  "keywords": [
    "engineer"
  ],
  "remoteOnly": false,
  "maxJobsPerCompany": 100,
  "includeDescription": true,
  "onlyNewJobs": true
}
```

You can paste: `https://apply.workable.com/huggingface`, `https://<company>.workable.com`, a job URL, a careers page with an embedded Workable widget, or just the account slug (`huggingface`).

### Output example (real run)

```json
{
  "company": "Hugging Face",
  "company_slug": "huggingface",
  "ats": "workable",
  "job_id": "81B46579FE",
  "requisition_id": null,
  "title": "Open-Source Machine Learning Engineer - EMEA Remote",
  "department": "Open Source",
  "team": "Engineering",
  "location": "Paris, Île-de-France, France",
  "locations": [
    "Paris, Île-de-France, France"
  ],
  "remote": true,
  "workplace_type": "remote",
  "employment_type": "Full-time",
  "posted_at": "2026-05-29T00:00:00Z",
  "updated_at": null,
  "salary": null,
  "job_url": "https://apply.workable.com/j/81B46579FE",
  "apply_url": "https://apply.workable.com/j/81B46579FE/apply",
  "description_text": "At Hugging Face, we're on a journey to democratize good AI. We are building the fastest growing platform for AI builders with over 11 million users who collectively shared over 4 million models, 1 million datasets & 1.5…",
  "description_html": null,
  "source_input": "https://apply.workable.com/huggingface",
  "scraped_at": "2026-10-21T18:15:20Z"
}
```

Download the results as JSON, CSV, Excel or XML, or read them through the Apify API. A per-company summary (jobs found, jobs written, errors) is saved to the `OUTPUT` record of the run's key-value store.

### Pricing

Pay per event, no subscription:

| Event | Price |
|---|---|
| Job result (one job in the dataset) | **$0.0015** ($1.50 per 1,000 jobs) |
| Actor start (per run) | $0.002 |

For example, 500 jobs cost about $0.75. A daily **Only new jobs** monitor that finds 20 new jobs costs about $0.03 per run. Failed companies are never charged, and you can set a maximum cost per run.

### Use cases

- Track hiring at Workable companies such as Hugging Face, Skroutz, Blueground and Upstream, and thousands of European SMEs and startups.
- Build niche job boards and newsletters from a list of target employers.
- Sales and recruiting intelligence: hiring is a buying signal, so see which accounts are hiring, for which teams and where.
- Job alerts for yourself or your candidates via **Only new jobs** plus a schedule.
- Feed clean job data to AI agents, RAG pipelines and spreadsheets.

### FAQ

**Is this legal?** The Actor reads only the public job-board endpoint that Workable provides so job postings can be displayed on career sites and job boards. No login and no personal data, apart from what employers publish in their job ads. You are responsible for how you use the data.

**How do I find the Workable account slug?** Open the company's Workable careers page: `https://apply.workable.com/<slug>/`. Paste that URL, a job URL (`apply.workable.com/<slug>/j/...`) or just the slug. Old `<slug>.workable.com` addresses work too.

**A company returns 0 jobs?** Some companies keep a Workable account but publish their jobs elsewhere. The run still succeeds; the summary shows `jobs_found: 0` for that company.

**How does "Only new jobs" work?** The Actor remembers the job IDs it has already delivered for each company in a named key-value store (`stateStoreName`). Later runs output only unseen jobs. The first run returns everything that matches, and closed jobs drop out of the state automatically. Jobs held back by **Max jobs per company** are delivered in the next run.

**One company failed. What happens?** It's logged and listed in `OUTPUT.errors`, and the other companies are still processed. If you paste a URL from another ATS, the error message points you to [sysco32/ats-jobs-feed](https://apify.com/sysco32/ats-jobs-feed).

# Actor input Schema

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

One company per line. Accepted: `https://apply.workable.com/huggingface`, `https://<company>.workable.com`, a job URL, a careers page with an embedded Workable widget, or just the account slug (`huggingface`). A slug is the last part of `apply.workable.com/<slug>`. For Greenhouse, Lever, Ashby, Workday, SmartRecruiters, Recruitee, Personio and Teamtailor use <a href='https://apify.com/sysco32/ats-jobs-feed'>sysco32/ats-jobs-feed</a>.

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

Keep only jobs whose title, department or team contains at least one of these words or phrases (case-insensitive, whole words). Leave empty for all jobs. Example: <code>engineer</code>, <code>data scientist</code>, <code>product manager</code>.

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

Drop jobs whose title contains any of these words, e.g. <code>intern</code>, <code>senior</code>.

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

Keep only jobs whose location text contains one of these strings (case-insensitive), e.g. <code>Berlin</code>, <code>Germany</code>, <code>London</code>. Add <code>remote</code> to also keep remote jobs.

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

Keep only jobs marked remote by the ATS (or with 'Remote' in the location).

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

Keep only jobs published in the last N days. 0 = no date filter. Jobs without a published date are kept.

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

Stop after this many matching jobs per company. 0 = no limit (all open jobs).

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

Add the full job description as plain text.

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

Add the original description HTML next to the plain text (larger dataset).

## `onlyNewJobs` (type: `boolean`):

Remember the job IDs already delivered for each company in a named key-value store and output only jobs you have not seen before. The first run outputs all matching jobs. Ideal for scheduled runs, alerts and webhooks: you only pay for new jobs.

## `stateStoreName` (type: `string`):

Name of the key-value store that keeps seen job IDs for 'Only new jobs'. Use a different name per independent monitor (for example per schedule or per customer).

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

How many companies to fetch at the same time. Requests to each ATS host are additionally rate-limited.

## `requestIntervalSecs` (type: `number`):

Politeness delay between requests to the same ATS host.

## Actor input object example

```json
{
  "companies": [
    "https://apply.workable.com/huggingface",
    "skroutz",
    "blueground",
    "upstream"
  ],
  "remoteOnly": false,
  "postedWithinDays": 0,
  "maxJobsPerCompany": 25,
  "includeDescription": true,
  "includeDescriptionHtml": false,
  "onlyNewJobs": false,
  "stateStoreName": "workable-jobs-monitor-seen",
  "maxConcurrency": 4,
  "requestIntervalSecs": 0.25
}
```

# Actor output Schema

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

All job postings found in this run, one item per job (company, ats, job_id, title, department, team, locations, remote, workplace_type, employment_type, posted_at, salary, job_url, apply_url, description_text).

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

JSON summary: jobs found and written per company, failed companies with error messages, and whether the run stopped at the spending limit.

# 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://apply.workable.com/huggingface",
        "skroutz",
        "blueground",
        "upstream"
    ],
    "maxJobsPerCompany": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("sysco32/workable-jobs-monitor").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://apply.workable.com/huggingface",
        "skroutz",
        "blueground",
        "upstream",
    ],
    "maxJobsPerCompany": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("sysco32/workable-jobs-monitor").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://apply.workable.com/huggingface",
    "skroutz",
    "blueground",
    "upstream"
  ],
  "maxJobsPerCompany": 25
}' |
apify call sysco32/workable-jobs-monitor --silent --output-dataset

```

## MCP server setup

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

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/NKjpZJ4LoJA2prwqz/builds/7tO3bkqRfIquImwOq/openapi.json