Workable Jobs Scraper

Workable Jobs Scraper returns one structured dataset record for each current public job opening on a specified Workable company board. Give it a company slug or public apply.workable.com URL to collect titles, departments, locations, salary text, workplace type, optional description-level content, application URLs, and source URLs for traceable recruiting or job-market analysis.

Best fit

• Use this actor when you already know employers that use Workable and need their current public openings in a consistent dataset.
• Pass one or more employer slugs or Workable careers URLs, then use title, location, or department filters before a record is written and billed.
• This focused public-board workflow complements dedicated tools for employer discovery, candidate records, applications, and interview data.

Focused standalone workflow

This actor is designed as a focused standalone workflow for teams that already have a selected employer list and need a source-linked Workable job dataset. It works as a focused standalone workflow because each call starts with explicit public company boards, applies filters before the dataset write, and preserves the listing and detail sources alongside the result.

From employer list to recruiting signal

A talent-intelligence team maintains a list of competitors with Workable career boards. They pass those employers with an engineering and remote filter. The actor returns title, location, department, workplaceType, postedAt, applyUrl, and source provenance; the team can compare role mix, keep a current hiring watchlist, or route an opening into a job-matching workflow.

Quick start

{
  "companies": ["recurly", "https://apply.workable.com/platzi/"],
  "maxJobsPerCompany": 25,
  "titleIncludes": "engineer",
  "locationIncludes": "remote",
  "departmentIncludes": "engineering",
  "includeDescriptions": true
}

companies accepts raw Workable slugs and public Workable careers URLs. maxJobsPerCompany is a per-employer collection boundary; the actor deliberately uses Workable's bounded public listing route rather than making unbounded requests.

What data you receive

Every dataset row is one public job post. The fields keep source and collection context beside the business data.

Field	Meaning
jobId, companySlug, companyName	Public job identity and employer context.
title, location, department, employmentType	Role fields for filtering and analysis.
workplaceType, salary, postedAt	Public work-model, compensation, and freshness signals when exposed.
descriptionText, requirementsText, benefitsText	Detail-page content when enabled.
applyUrl, jobUrl, sourceListingUrl, scrapedAt	Direct application path and provenance.

{
  "jobId": "54B48C70F0",
  "title": "Staff Software Engineer",
  "companyName": "Recurly",
  "companySlug": "recurly",
  "location": "Medellín, Colombia (Hybrid)",
  "department": "Engineering",
  "employmentType": "Full-time",
  "workplaceType": "hybrid",
  "descriptionText": "We're looking for a Staff Full-Stack Engineer...",
  "applyUrl": "https://apply.workable.com/recurly/j/54B48C70F0/apply",
  "jobUrl": "https://apply.workable.com/recurly/jobs/view/54B48C70F0.md",
  "sourceDetailUrl": "https://apply.workable.com/recurly/jobs/view/54B48C70F0.md",
  "sourceListingUrl": "https://apply.workable.com/recurly/jobs.md?query=a",
  "postedAt": null
}

API and agent use

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~workable-jobs-scraper/runs" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"companies":["recurly"],"maxJobsPerCompany":25,"includeDescriptions":true}'

For an AI agent workflow through Apify MCP, use this prompt:

Collect up to 25 public engineering jobs from the Workable company board recurly. Return title, location, department, workplace type, direct application URL, posted timestamp, and source URLs. Preserve the actor outcome and provenance in the final analysis.

The actor is read-only. It returns its data in the default dataset, a compact OUTPUT contract, and a detailed RUN_SUMMARY diagnostic record. INVALID_INPUT and valid empty matches succeed truthfully; a completely inaccessible board fails as UPSTREAM_FAILED, while useful partial records are retained as PARTIAL.

Pricing and boundaries

This actor uses Pay per event plus Apify platform usage. A validated job written to the dataset costs $0.004 per job; filtering happens before writing and no record is charged before it is persisted. The actor-start event is $0.00005. For a bounded 25-record run, event charges are at most 25 records × $0.004 + $0.00005 = $0.10005, plus Apify platform usage. Workable's public listing route is bounded, and maxJobsPerCompany makes the collection and event-cost ceiling explicit. The live Pricing tab is the source of truth for current event pricing and platform-usage details.

Limits and recovery

The public Workable Markdown listing route returns a bounded current listing, so each company is capped at 30 returned records and no unverified pagination is attempted. If a board is temporarily unavailable, retry later with the same public company slug; if a detail page is unavailable after a listing is collected, the actor preserves the useful listing fields and reports a PARTIAL outcome. Use the OUTPUT and RUN_SUMMARY records to distinguish a valid empty filter result from an unavailable public board.

Freshness and provenance

The implementation uses Workable's public jobs.md listing and matching job-detail Markdown routes. sourceListingUrl, sourceDetailUrl, postedAt, and scrapedAt are persisted so downstream users can verify the source and collection time for every job record.

Best results

• Start from selected employers that visibly host their careers board on Workable.
• Set includeDescriptions to false for a compact role inventory; keep it on when requirements and benefit text matter.
• Preserve sourceListingUrl, sourceDetailUrl, and scrapedAt in downstream reporting so others can verify the public record.
• Schedule a focused repeat collection for hiring monitoring and compare postedAt with scrapedAt rather than treating a single run as a permanent record.

Builder's note

I designed this actor around Workable's public Markdown routes because the listing and job-detail responses are stable, compact, and source-addressable. Keeping a listing source, detail source, direct application URL, and machine-readable run outcome in the same contract makes the data useful to both recruiters and agents without exposing private ATS data.

Responsible use

Use publicly available or authorized data in accordance with applicable laws, source terms, and your organization's data-governance policies. Keep source URLs with shared records so recipients can review the employer's current public posting.