# Workable Published Hiring Footprint Brief (`jpmarketdata/workable-hiring-footprint-brief`) Actor

Summarize a Workable employer board by unique published roles, recent publication dates, countries and departments. Multiple location rows count as one role. Unofficial.

- **URL**: https://apify.com/jpmarketdata/workable-hiring-footprint-brief.md
- **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community)
- **Categories:** Jobs, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.00 / 1,000 employer hiring footprint createds

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 Published Hiring Footprint Brief

> **Unofficial** — independent tool, **not affiliated with, endorsed by, or sponsored by Workable**. It reads only publicly visible pages. Support, reliability guarantees and the full disclaimer are at the bottom of this page.

Summarize known employers' published Workable boards for recruiting operations and talent-market research. Counts describe job advertisements, not hires or employee headcount.

### Input

Provide 1–3 exact lowercase Workable account slugs, not URLs. All values are validated before network access and duplicates are removed in input order. `recentDays` defaults to 7 UTC calendar days, including today. `maxItems` defaults to 1; the event budget and maxItems select a prefix before requests.

### Output

One row per selected board. `publishedRoleCount` deduplicates by shortcode; `locationPlacementCount` counts source rows. Each country and department count deduplicates shortcode within that group; group counts may sum above the board-wide role count because one role can span countries. `recentPublishedRoleCount` uses the source `published_on` date and does not claim a role first appeared then. Top groups contain at most five entries, sorted by count descending and label ascending. A validated empty board emits one explicit zero-role row.

`EXPECTED_OUTPUT.example.json` illustrates an observed WorkMotion snapshot. Live role, location and country counts change; each run uses the UTC time after that board's response is retrieved for `fetchedAt` and the publication window.

### Limits

Use only Workable's documented public GET endpoint, following its one redirect to the public widget API after checking both hosts' live robots files. No private SPI token, application endpoint, browser, proxy, paid API or retries after 403/429. Limit to three boards and eight HTTP requests including robots and redirects, 2 MiB per board response, 256 KiB per robots response, 30 seconds per request, 90 seconds per run and 256 MB memory. Reject malformed JSON, missing or conflicting shortcode identity, invalid publication dates, unexpected redirects, oversized responses and ambiguous partial lists. Validate all selected boards before output or charge.

### Pricing

The sole primary event `hiring-footprint-created` is $0.02 per delivered board row. No actor-start or secondary charge. Dataset rows and charged events must match; an output-write failure after earlier successful rows can leave those earlier rows billable.

### Privacy

Only board name, slug, aggregate role/location/country/department counts and source provenance are returned. Do not persist job descriptions, titles, application links, email addresses, phone numbers, applicant information, raw responses or person names.

### Sources and terms

Workable documents the public published-jobs endpoint at https://help.workable.com/hc/en-us/articles/115012771647-Using-the-Workable-API-to-create-a-careers-page. Check https://www.workable.com/robots.txt and https://apply.workable.com/robots.txt on each run. The applicability of https://jobs.workable.com/terms section 15.2 to this public API is recorded as uncertainty under DR-0007; no blanket permission is claimed.

### If something goes wrong

- **Wrong number or a failed run?** Open a ticket on the **Issues** tab. I read every one and reply within 2 business days (Japan time).
- **You never get a fake "empty" result.** If the site can't be read, the run fails and says so.
  One validated employer-board brief is one billable event, including a confirmed zero-open-roles result. Source failures before delivery have no event charge.
- **Checked every week.** An automatic test runs this tool weekly; if the site changes, I fix it.
- **Public pages only.** No login, no personal data, and it goes easy on the site.

### More tools by the same author

- [ATS Hiring & Pay Disclosure Sample Brief](https://apify.com/jpmarketdata/ats-hiring-pay-disclosure-brief)

All tools (Japan marketplaces, real estate, jobs, racing, prediction markets): <https://apify.com/jpmarketdata>

### Disclaimer

Unofficial, independent tool — **not affiliated with, endorsed by, or sponsored by Workable**. Product names and logos belong to their owners and only say where the data comes from. Data is read from public pages, for market research; check before you act on it.

# Actor input Schema

## `slugs` (type: `array`):

One to three account slugs from Workable board URLs. No arbitrary URLs.

## `recentDays` (type: `integer`):

Count unique roles whose published\_on date falls within this many UTC calendar days, including today.

## `maxItems` (type: `integer`):

Maximum unique slugs selected in input order, further limited by the available event budget.

## Actor input object example

```json
{
  "slugs": [
    "workmotion"
  ],
  "recentDays": 7,
  "maxItems": 1
}
```

# Actor output Schema

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

No description

# 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 = {
    "slugs": [
        "workmotion"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpmarketdata/workable-hiring-footprint-brief").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 = { "slugs": ["workmotion"] }

# Run the Actor and wait for it to finish
run = client.actor("jpmarketdata/workable-hiring-footprint-brief").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 '{
  "slugs": [
    "workmotion"
  ]
}' |
apify call jpmarketdata/workable-hiring-footprint-brief --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/workable-hiring-footprint-brief"
        }
    }
}
```

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/fSCvGKzWlSjkwItHJ/builds/fINNcgbiUzuqbVPYb/openapi.json