Workable Jobs Scraper

Export public Workable career-board jobs by company slug or URL, including job titles, locations, departments, workplace type, remote flags, posting dates, job URLs, application URLs, and optional descriptions.

Use this Actor when you need a repeatable CSV, JSON, Excel, API, or AI-agent export of Workable-hosted job boards for recruiting intelligence, hiring-signal monitoring, sales research, or job-market analysis.

What Does Workable Jobs Scraper Do?

Workable Jobs Scraper turns public Workable career pages into structured job listing rows.

• Scrape by company slug: use recurly from https://apply.workable.com/recurly/.
• Scrape by URL: paste Workable company career pages, apply.workable.com job links, or current jobs.workable.com/view job pages.
• Filter jobs: use keyword, location, department, work type, and remote filters.
• Collect job details: export titles, locations, departments, workplace labels, remote flags, posting dates, job URLs, and Workable IDs.
• Optionally include descriptions: fetch job detail data for description, requirements, and benefits HTML.

Input Example

{
  "companySlugs": ["recurly"],
  "query": "engineer",
  "maxItems": 20,
  "includeDescription": false
}

You can also paste Workable URLs:

{
  "startUrls": [
    {
      "url": "https://apply.workable.com/recurly/"
    }
  ],
  "maxItems": 20
}

Individual current Workable job pages are accepted too:

{
  "startUrls": [
    {
      "url": "https://jobs.workable.com/view/dHWbxHXmt9g9mfaewTC2eX/full-stack-engineer"
    }
  ],
  "maxItems": 1,
  "includeDescription": true
}

Output Example

{
  "companySlug": "recurly",
  "jobTitle": "Senior Software Engineer, Platform Engineering",
  "location": "Broomfield, Colorado, United States",
  "departments": [],
  "workplace": "hybrid",
  "remote": false,
  "publishedAt": "2026-08-01",
  "url": "https://apply.workable.com/recurly/j/55F8A87FA4/",
  "jobId": 5999351,
  "sourceJobId": "5999351",
  "shortcode": "55F8A87FA4",
  "city": "Broomfield",
  "region": "Colorado",
  "country": "United States",
  "workType": "Full-time",
  "applicationUrl": "https://apply.workable.com/recurly/j/55F8A87FA4/apply/",
  "sourceType": "company_board",
  "descriptionHtml": null
}

Who Is It For?

Input settings

Tips For Better Results

• Use company slugs for clean inputs: they are shorter and less fragile than copied URLs.
• Start with a small maxItems: confirm the board and filters before scheduling large runs.
• Use includeDescription only when needed: it adds larger HTML fields and may require detail requests when a board feed omits them.
• Leave filters empty for full board exports: filters can exclude roles if company naming differs.
• Check board availability: not every company uses Workable or keeps old postings public.
• Use multiple boards safely: an unavailable board is recorded in the run summary while the Actor continues with other valid boards.

API usage

Run Workable Jobs Scraper from your own code with the Apify API.

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = {
  "companySlugs": ["recurly"],
  "maxItems": 10,
  "includeDescription": false
};

const run = await client.actor('fetch_cat/workable-jobs-scraper').call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("fetch_cat/workable-jobs-scraper").call(run_input={
  "companySlugs": ["recurly"],
  "maxItems": 10,
  "includeDescription": False
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~workable-jobs-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"companySlugs":["recurly"],"maxItems":10,"includeDescription":false}'

Use with AI agents via MCP

Workable Jobs Scraper can be used by AI assistants through the hosted Apify MCP server.

Claude Code setup

claude mcp add --transport http apify "https://mcp.apify.com?tools=fetch_cat/workable-jobs-scraper"

Claude Desktop, Cursor, or VS Code JSON config

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/workable-jobs-scraper"
    }
  }
}

Example prompts

• "Run Workable Jobs Scraper with this input JSON and summarize the dataset."
• "Export the latest Workable Jobs Scraper results to a table I can review."
• "Schedule this Actor for monitoring and tell me what changed between runs."

Limits And Notes

• The Actor extracts public Workable career-board data; it does not access private applicant systems.
• Filters are applied locally to the public job title, description, location, department, employment type, and workplace fields that Workable exposes.
• Descriptions, requirements, and benefits are only included when includeDescription is enabled and available.
• Closed, removed, or unsupported job URLs fail with an actionable source warning instead of silently producing an empty successful run.
• The Actor uses public Workable job-board endpoints and bounded retries. It does not require a Workable API key.
• RUN_SUMMARY and PENDING_WORK in the default key-value store record board-level warnings and unfinished boards when a run is cut short.

Support

Report bugs, wrong output, blocked runs, or missing fields from the Actor page. Include the Apify run ID or run URL, your input JSON, what you expected, what the Actor returned, and one reproducible public URL so the issue can be tested quickly.

Privacy and data handling

This Actor runs with Apify limited permissions and only processes data needed for the documented run. It uses job-search inputs and public job-posting results to produce the output dataset and sends requests to public Workable Jobs pages/endpoints; results are stored in Apify run storage for your account. FetchCat does not use your inputs or outputs for advertising, does not use them for model training, and does not retain them outside the Apify run except for transient support debugging when you explicitly share run details. You are responsible for using the Actor lawfully, respecting the target site's terms, and avoiding unnecessary personal or sensitive data in inputs.