# Greenhouse Hiring Signals (`pantherjaboba/greenhouse-hiring-signals`) Actor

Monitor public Greenhouse job boards for newly listed, changed, and repeatedly absent openings with bounded title and location filters.

- **URL**: https://apify.com/pantherjaboba/greenhouse-hiring-signals.md
- **Developed by:** [Jeremiah Davis](https://apify.com/pantherjaboba) (community)
- **Categories:** Jobs, Automation
- **Stats:** 2 total users, 1 monthly users, 91.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.00 / 1,000 successful board checks

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

## Greenhouse Hiring Signals

Monitor public Greenhouse job boards and receive one compact report for each successful board check. Reports include the current matched openings, department and location counts, newly observed jobs, selected field changes, and jobs that have been absent from two consecutive complete captures.

### Input

Enter the token from a public Greenhouse board URL. For example, `webflow` is the token in `boards.greenhouse.io/webflow`.

```json
{
  "boards": ["webflow"],
  "monitorId": "store-smoke",
  "titleKeywords": ["engineer", "data"],
  "locationKeywords": ["remote", "new york"],
  "maxJobsPerBoard": 500
}
```

Title and location filters are optional. Within each filter, a job matches any keyword; when both filters are present, it must match both groups. Matching is case-insensitive. Keep the same `monitorId`, board list, filters, and limit across scheduled runs so the actor can compare like with like.

### Output

Every completed board check produces one dataset item with:

- `status`: `baseline` on the first observation, then `checked`
- `total_open` and `matched_open`
- `department_counts` and `location_counts`
- `jobs`: current matched public job summaries
- `changes`: deterministic `newly_observed`, `changed`, and `no_longer_listed` events
- `change_counts`: counts by event type

Store runs are bounded to three minutes, including all configured boards. Use at most ten boards per monitor and raise `maxJobsPerBoard` only when the source reports that the current safety cap is too low.

The first run establishes a baseline and emits no changes. A missing job is described only as `no_longer_listed`, after it is absent from two complete captures; that does not claim the role was filled. Failed, malformed, redirected, oversized, or capped source responses do not advance the saved baseline and do not produce a charged board report.

### Data and source limits

The actor reads Greenhouse's public board API over HTTPS. It stores job IDs, titles, public locations, departments, canonical job links, and public update timestamps. It does not collect applicants, infer salaries, call LinkedIn, use an LLM, or publish full job descriptions or recruiter contact details.

Pricing is $0.02 per successfully delivered board report, including baseline and unchanged reports. Failed checks are uncharged. Configure a maximum run charge in Apify when you want a hard spending limit.

### Scheduled monitoring and state

Keep the same monitor ID and filters when scheduling the Actor in Apify. State is held in actor-created named storage within your own Apify account. Overlapping runs of the same monitor are refused without source reads or charges. The first capture creates a baseline; later captures compare selected fields. Storage removal or account retention may reset the baseline. A resumed run does not recharge a report already visible in its dataset; an uncertain interrupted charge may be waived. Reports are observation evidence, not a claim that a missing role was filled.

Source: https://docs.greenhouse.io/job-board.html

# Actor input Schema

## `boards` (type: `array`):

One to ten public board tokens, such as webflow from boards.greenhouse.io/webflow.

## `monitorId` (type: `string`):

A stable name that keeps this monitor's snapshots separate from your other runs.

## `titleKeywords` (type: `array`):

Optional case-insensitive substrings. A job matches when its title contains any entry.

## `locationKeywords` (type: `array`):

Optional case-insensitive substrings. A job matches when its public location contains any entry.

## `maxJobsPerBoard` (type: `integer`):

Safety limit. A larger board fails without changing its baseline so you can raise the limit deliberately.

## Actor input object example

```json
{
  "boards": [
    "webflow"
  ],
  "monitorId": "store-smoke",
  "titleKeywords": [],
  "locationKeywords": [],
  "maxJobsPerBoard": 500
}
```

# Actor output Schema

## `checks` (type: `string`):

Each item contains board status, totals, public matched jobs, department/location counts, and deterministic changes.

# 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 = {
    "boards": [
        "webflow"
    ],
    "monitorId": "store-smoke",
    "maxJobsPerBoard": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("pantherjaboba/greenhouse-hiring-signals").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 = {
    "boards": ["webflow"],
    "monitorId": "store-smoke",
    "maxJobsPerBoard": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("pantherjaboba/greenhouse-hiring-signals").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 '{
  "boards": [
    "webflow"
  ],
  "monitorId": "store-smoke",
  "maxJobsPerBoard": 500
}' |
apify call pantherjaboba/greenhouse-hiring-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pantherjaboba/greenhouse-hiring-signals"
        }
    }
}
```

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/KfU2Ef0fPzU3M6uCC/builds/dDIXiK6Vh0bLegYyo/openapi.json