Workable Jobs Scraper: 3,000+ Companies + Only New Jobs

$0.2/1K jobs | Search Workable jobs from 3,000+ companies, plus selected Greenhouse, Lever and Ashby boards, in one run. Filter by keyword, location, remote and job type. Full descriptions and only new jobs on repeat runs. No login or API key. Independent, unofficial tool. Not affiliated with or endorsed by Workable, Greenhouse, Lever or Ashby.

Workable Jobs Bulk Scraper

Our scraper collects recent jobs from Workable's public job index, which lists postings from more than 3,000 companies, plus a selected set of Greenhouse, Lever and Ashby company boards, in one run. Filter by keyword, location, work arrangement, employment type and posting age. Every row carries the complete original job description in text and HTML, the employer and the location, and keeps its own source. It is ideal for job alerts, recruiting and sourcing pipelines, and hiring-market research across many employers.

• Only Workable's public job index? Our Workable Jobs Scraper costs $0.10 per 1,000 jobs, half of this Actor's price; this Actor adds the Greenhouse, Lever and Ashby boards in the same run.
• Need named employers on Workday or SmartRecruiters too? Our Company Careers Jobs Scraper covers 16 named employers on Greenhouse, Lever, Ashby, Workday and SmartRecruiters plus Workable's job index at the same $0.20 per 1,000 jobs, but its Workable share is capped at 50 jobs per run by default.
• Browse all our job-board scrapers: https://apify.com/nomad-agent

Key Benefits

• No login or API key: nothing to set up, and no account at risk.
• Low pricing: $0.20 per 1,000 jobs, with lower rates on Scale and Business plans ($0.15 and $0.10 per 1,000), plus a $0.00005 start fee per run.
• Many companies in one run: Workable postings from more than 3,000 employers, newest first.
• Full descriptions only: a posting with a missing or truncated description is never returned.
• No repeats across runs: schedule the same search daily and get only postings you have not received yet.

How It Works

1. Provide your search. Every filter is optional:
   • (optional) Search queries (e.g., software engineer, sales manager). A job matches when its title or description contains every word of a query.
   • (optional) Locations (e.g., Germany, London, GR, Europe). Countries match by name, code and native name, so Germany, DE and Deutschland find the same jobs.
   • (optional) Work arrangement (remote, hybrid, onsite) and employment type (Full-time, Part-time, Contract, Internship).
   • (optional) Posted within (e.g., 24h, 7d, 2w). Default is any.
2. Set how many jobs you want with maxItems.
3. Click Start. The form opens with software engineer and 20 jobs, so a first run returns real rows in seconds.

More settings:

• maxItems - How many jobs one run returns. Default is 200; 0, or anything above 200, means 200.
• maxItemsPerSource - How many jobs any one source may contribute. Default is 200, so the newest jobs win whichever system they come from.
• dedupe - On by default: jobs already delivered to your Apify account for the same search are skipped. Set dedupe.enabled to false to get everything again, or set dedupe.key to keep separate alert histories.

Run the same search twice and the second run returns only new jobs, possibly none. That is the repeat suppression working; turn dedupe off to see every job again.

Greenhouse, Lever and Ashby coverage is a short list of company boards today, and it grows over time. A company or board you name is not fetched: inputs such as companies or atsProviders are ignored with a note in the run summary. Most rows come from Workable.

A run returns at most 200 jobs, so split a big export by keyword or country and keep dedupe on so the runs do not overlap.

If you set a work arrangement or employment type, jobs whose posting does not state it are left out. Leave those filters empty to keep them. Workable rows state the work arrangement on almost every posting and the employment type on about two thirds; they carry no salary, deadline or applicant locations, so those fields are null. Salary and applicant locations appear only on some Greenhouse, Lever and Ashby postings.

Data You'll Receive

• Job details: title, complete description (text and HTML), locations, posting date, work arrangement and employment type when stated.
• Employer: company name, plus the source it came from (workable, greenhouse, lever or ashby).
• Links and identity: the original posting URL, plus a stable id and source for deduplication.
• On some Greenhouse, Lever and Ashby jobs: salary, deadline and where an applicant may live (applicantLocations), when the posting says so.

Sample output data

Here is an example job from this Actor (long text shortened for display):

{
  "schemaVersion": "nomad-agent-job-row-v4",
  "source": "workable",
  "id": "46fb145a-cd65-48bd-8c6a-bca58ee43f47",
  "url": "https://jobs.workable.com/view/9Lnuu1ex5wKHre5hybsd9p/machinist-apprentice-in-elmira-at-tri-mach-group-inc.",
  "title": "Machinist Apprentice",
  "company": "Tri-Mach Group Inc.",
  "locations": [
    "Elmira, Ontario, Canada"
  ],
  "applicantLocations": null,
  "postedAt": "2026-10-19T11:20:17.169000Z",
  "deadline": null,
  "description": "Tri-Mach is a leading provider of sanitary stainless steel solutions, specializing in custom equipment and services for the food, beverage, and pharmaceutical industries. For over 30 years, Tri-Mach has remained passionate about providing state-of-the-art machinery and innovative new solutions to ou… [truncated for display]",
  "descriptionHtml": "<p>Tri-Mach is a leading provider of sanitary stainless steel solutions, specializing in custom equipment and services for the food, beverage, and pharmaceutical industries. For over 30 years, Tri-Mach has remained passionate about providing state-of-the-art machinery and innovative new solutions to… [truncated for display]",
  "workType": "onsite",
  "salary": null,
  "employmentTypes": [
    "Full-time"
  ],
  "hiringContacts": []
}

Workable Jobs API

Results are stored in a dataset that you can export as CSV, JSON or Excel, or read through the Apify API. Schedule it, or connect it to Make, n8n, Zapier or an MCP client to push new jobs wherever you need them. Each run also writes a RUN-SUMMARY record to its key-value store, with any input field that was mapped or ignored.

Support and Feedback

We improve these scrapers from your feedback. If something breaks or you need a filter:

• Open an issue on the Actor's Issues tab.
• If this Actor saved you time, a short review on the Store helps other people find it.

Run evidence

Free-tier event rates set 2026-10-19: result $0.0002; actor-start $0.00005. The sample above comes from the default run TyU6WJFA6Df0TFkyi (2026-10-19, build 0.1.2), which returned 200 jobs: 199 from Workable and 1 from Greenhouse. This is an observed example, not a guarantee that repeating it returns this row.

Recent Workable, Greenhouse, Lever and Ashby jobs with complete original descriptions. Each row carries the source ID and URL, title, employer, locations, the original description as text and HTML, posting date, deadline, work arrangement, employment type, salary and the hiring contacts the source names, whenever the source publishes them. Unknown optional facts are null; an empty locations array means the source names no physical place, and an empty hiringContacts array means the source names nobody. locations is where the job is; applicantLocations is where an applicant may live, for example a remote job open only to residents of some countries: it is null when the source states nothing and [] when it states no restriction.

Postings are collected continuously from these public job sources: Greenhouse boards; Lever boards; Ashby boards; Workable. Each row keeps its own source. Every posting is verified before it is served. A posting with a missing, truncated or unverified description is never returned: every row has the full original text. Runs read the stored postings, so they are fast and never touch the source website.

Workable postings come from Workable's public job index (more than 3,000 employers with stored postings in October 2026). Greenhouse, Lever and Ashby postings come from the company boards we collect continuously, a short list today that grows over time. A company or board you name is not fetched: unknown inputs such as companies or atsProviders are ignored with a note in RUN-SUMMARY. Each row's source says which system it came from.

Input

{"schemaVersion": "nomad-agent-simple-inventory-search-v2", "queries": ["software engineer"], "locations": ["Europe"], "locationTypes": ["remote"], "employmentTypes": [], "postedWithin": "7d", "maxItems": 200, "maxItemsPerSource": 200, "dedupe": {"enabled": true, "key": ""}}

Every filter is optional, and an empty list means no filter. Filters are applied to all stored postings before maxItems is counted.

• queries: a posting matches a query when its title or description contains every word of it, as whole words, ignoring case. A posting matches when any query matches.
• locations: a city, region, country name or two-letter ISO country code. Countries match by name, code and native name (Germany, DE and Deutschland find the same postings), and EU and Europe cover their member countries.
• locationTypes (remote, hybrid, onsite) and employmentTypes (Full-time, Part-time, Contract, Internship): while one is set, a posting whose source does not state that fact is left out.
• postedWithin: a positive duration in hours (h), days (d), weeks (w) or 30-day months (m), up to 36500 days, or any. Postings without a source date use the date they were first seen, which later refreshes never reset.
• maxItems defaults to 200; 0, or anything above 200, means 200.
• maxItemsPerSource (default 200, at most 200) caps how many postings each source contributes; maxItems then keeps the newest postings across all sources.
• dedupe suppresses postings already delivered to the same Apify account for the same search; different filters keep separate histories. Set dedupe.enabled to false to get stateless results, or set dedupe.key to keep separate alert histories.

Output

One flat row per posting in the nomad-agent-job-row-v4 format: schemaVersion, source, id, url, title, company, locations, applicantLocations, postedAt, deadline, description, descriptionHtml, workType, salary, employmentTypes, hiringContacts. employmentTypes lists the types the source states (Full-time, Part-time, Contract, Internship) or is null. applicantLocations lists the regions where the source says an applicant may live (for example United States for a remote job open to US residents), null when it states nothing and [] when it states no restriction. Each hiring contact has a name, and a title and url or null. Newest postings come first. A run summary, including any input field that was mapped or ignored, is written to the RUN-SUMMARY record of the run's key-value store.

Fast setup and source code

Public repository · Agent setup skill.

Use the Actor’s current input form for filters, or start with its documented API example. Select the latest build. Read the dataset together with the run summary: a successful status alone does not show that every source was reached.

Restrictive filters or repeat-delivery suppression can produce zero results.

Changes

• October 2026: first release. One run searches the stored Greenhouse, Lever, Ashby and Workable postings with the shared filters (queries, locations, locationTypes, employmentTypes, postedWithin), maxItems and maxItemsPerSource (default 200).