Workable Jobs Scraper

Export public Workable company-board jobs and supported individual job pages with source identifiers, locations, departments, workplace labels, dates and application links. Optional detail collection can include description, requirements and benefits HTML. Public board records support separate recruiting and hiring research rather than access to private applicant systems or an automated application service.

Quick start

Begin with a known board such as Recurly and a small shared cap, then inspect source links and filters before expanding a company list. The existing query example is:

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

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

• Export current Recurly Workable jobs — Start with the company board and its available public job metadata.
• Find Recurly engineering jobs — Try a title and description keyword filter.
• Include software-engineer descriptions — Collect available public job descriptions for closer review.
• View all public examples

What you get

One saved public job row with board or direct-posting identity, sourceType, sourceUrl and available employment metadata. Numeric company-board IDs and Jobs by Workable tokens can differ, so sourceJobId preserves a stable string form. Descriptions, requirements and benefits remain optional and can be unavailable on a public source.

Who is it for?

• Recruiting researchers inspecting known companies' public roles and employment labels.
• Sales and market analysts reviewing bounded hiring signals by department or region.
• Job-data teams joining source-identified listings in their own datasets.
• Automation developers exporting public board records into existing reports or review workflows.

How you can use the data

• Review Recurly engineering candidates. Use the existing recurly slug and engineer query, retaining title, departments and workplace context. Local filters match exposed source fields rather than guaranteeing all company roles or applicant eligibility.
• Inspect optional public descriptions. Enable descriptions for a small shortlist when you need requirements or benefits HTML. A detail request is needed only when the company feed omits the text, and missing fields remain distinct from a fully described job.
• Retrieve a known current posting. Use the existing Jobs by Workable URL template below and keep sourceType, sourceJobId and sourceUrl. Its identifier shape differs from company-board IDs, and a closed or unsupported link can produce a source warning rather than a fabricated job.
• Maintain your own board observations. Store IDs, job URLs, workplace labels and publication dates before comparing separate exports. Unavailable boards and pending work need their run diagnostics retained, while schedules, notifications and hiring conclusions are downstream work.

Input settings

Setting	JSON key	Type / default	Description
Company slugs	companySlugs	array, form example ["recurly"]	Workable company slugs from apply.workable.com URLs, for example recurly from https://apply.workable.com/recurly/.
Start URLs	startUrls	array, form example [{"url":"https://apply.workable.com/recurly/"}]	Public company boards or individual job URLs from apply.workable.com and jobs.workable.com/view.
Search query	query	string	Optional case-insensitive keyword filter applied to each title and description.
Locations	locations	array	Optional location filters, for example London, United States, or Remote.
Departments	departments	array	Optional department filters, for example Engineering, Product, or Sales.
Work types	workTypes	array	Optional Workable job type or workplace filters, for example full, hybrid, or remote.
Remote only	remote	boolean	Set to true to keep only jobs marked as remote, or false to keep only non-remote jobs. Leave empty for both.
Maximum jobs	maxItems	integer, default 20	Maximum number of job listings to save across all company boards.
Include job descriptions	includeDescription	boolean, default false	Include public description, requirements, and benefits HTML. An individual detail request is made only when the company feed does not contain it.
Maximum run time	maxRunSeconds	integer, 60–270, default 270	Safety budget including shutdown time. Already saved rows remain available if the run reaches its limit.

Provide at least one source in either list. API calls do not inherit the form's example company. Runs accept up to 100 unique sources combined, and all requests use direct public access without a proxy. See each input's help for validation and safety limits.

Existing board URL input

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

Existing individual job URL input

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

Output data

The existing illustrative Recurly row shows shape rather than a current posting lookup:

{
  "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
}

JSON key	Label	Type	Description
companySlug	Company slug	string	Company-board slug or normalized company name for a direct Jobs by Workable posting.
companyName	Company name	string / null	Company display name when available.
jobTitle	Job title	string	Public posting title.
location	Location	string / null	Combined city, region, and country.
departments	Departments	array	Employer-supplied departments or teams.
workplace	Workplace	string / null	Remote, hybrid, or on-site workplace mode.
remote	Remote	boolean	Whether Workable marks the role as fully remote.
publishedAt	Published	string / null	Workable publication timestamp or date.
url	Job URL	string	Canonical public job page.
jobId	Job ID	integer / string	Numeric company-board ID or UUID for a Jobs by Workable posting.
sourceJobId	Source job ID	string	Stable string representation of the source identifier.
shortcode	Shortcode	string	Company-board shortcode or Jobs by Workable token.
city	City	string / null	Posting city when supplied.
region	Region	string / null	Posting state or region when supplied.
country	Country	string / null	Posting country name.
countryCode	Country code	string / null	Country code when supplied by the source.
workType	Work type	string / null	Source employment or job type.
applicationUrl	Application URL	string	Public application link, or the job page if no separate link is available.
employmentType	Employment type	string / null	Source employment label, such as full-time.
language	Language	string / null	Posting language when supplied.
descriptionHtml	Description HTML	string / null	Public description, included only when requested.
requirementsHtml	Requirements HTML	string / null	Public requirements, included only when requested.
benefitsHtml	Benefits HTML	string / null	Public benefits, included only when requested.
sourceType	Source type	string	company_board, company_job, or jobs_workable_job.
sourceUrl	Source URL	string / null	Public Workable URL used for the result.
raw	Raw source record	object	Normalized source data and additional employer-supplied fields.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event is charged once after input validation. A started run can incur this charge even when no jobs are available.

The item event applies to each saved job row. Unavailable sources and empty searches do not create job-result charges. The Actor stops collecting more jobs when the result-charge budget is exhausted. Keep the shared cap small when checking a board or filter.

See the live Pricing tab for current rates and discounts. Platform usage can also apply.

Tips for best 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.
• Request descriptions only when needed: larger HTML fields are useful for detailed role reviews but make results heavier.
• 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.

Limits and caveats

• 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.
• Unavailable public boards and postings, or searches with no usable matches, finish successfully with an empty dataset and explanatory run warnings. An unavailable response does not establish whether a posting was private or deleted.
• Invalid inputs, broken extraction, essential storage or billing errors still fail. A mixed batch keeps useful jobs and reports isolated source failures. A run with no successfully processed available sources fails when extraction errors remain.
• Public Workable sources require no Workable API key.
• RUN_SUMMARY and PENDING_WORK in the default key-value store provide best-effort source warnings and progress. A hard timeout can prevent the final checkpoint. Start a new run for unfinished sources rather than resurrecting the same run.

The shared cap bounds saved jobs across boards. Leaving filters empty still does not guarantee a complete board archive. Public role, location and remote labels can change or be missing, and no hiring decision or application eligibility is inferred from them.

Keep RUN_SUMMARY and PENDING_WORK with your own interpretation of a partial export. Their presence reports warnings or unfinished boards rather than automatically creating a monitoring history or change alert.

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.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

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}'

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)

MCP and AI agents

You can ask your AI assistant to collect data with Workable Jobs Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Workable Jobs Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

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

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Workable Jobs Scraper by Fetch Cat, or give it the identifier fetch_cat/workable-jobs-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Collect up to five Recurly engineering jobs and help me compare their locations and workplace labels.”
• “Get five public Recurly job descriptions and summarize the available requirements and benefits. Leave missing information marked as missing.”
• “Retrieve the public Workable posting at this job link and help me review its employment details. Tell me if it is unavailable instead of inventing a job.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I scrape multiple Workable companies in one run?

Yes. Add multiple values to companySlugs or multiple URLs to startUrls.

Can I export Workable jobs to CSV or Excel?

Yes. Export the Apify dataset as CSV, Excel, JSON, XML, or RSS after the run.

Why did I get zero jobs?

Check that the company slug exists on apply.workable.com, remove strict filters, and try a small run without query, locations, or departments.

Why are descriptions missing?

Set includeDescription to true. Some boards or jobs still may not expose all detail fields.

Is this a Workable API alternative?

It can be used as an API-style export for public Workable career boards through Apify API, datasets, schedules, webhooks, and MCP.

Related Actors

• Ashby Jobs Scraper — Collect public Ashby job-board openings and available job details.
• ATS Jobs Scraper for 6 ATS Sources — Collect public job-board openings and available job details from supported applicant-tracking systems.
• Built In Jobs Scraper — Collect public Built In job listings and available company context.
• Dice Jobs Scraper — Collect public Dice technology job listings and available job details.
• Freelancer Jobs Scraper — Collect public freelance project listings and available project details.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥