# Job Board Change Monitor — Greenhouse & Lever (`pietrofilippo/job-board-change-monitor`) Actor

Track new jobs, changed fields and confirmed removals between successful board checks.

- **URL**: https://apify.com/pietrofilippo/job-board-change-monitor.md
- **Developed by:** [Pietro Filippo](https://apify.com/pietrofilippo) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 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

## Job Board Change Monitor

Monitor one Greenhouse or Lever public board across scheduled runs. Each successful check produces one dataset row containing `changes`, `listedCount`, `pendingRemovalCount`, the observation time and an evidence URL.

```json
{"board":"https://job-boards.greenhouse.io/webflow","snapshotStoreName":"my-job-monitor"}
```

Use the same named store for future runs. The store belongs to the account running the Actor. A different name starts a new baseline. Use a unique board/store pair per independent monitor and do not run overlapping writers. Scheduling must keep one run at a time; v0.1 does not implement a distributed lock.

The Actor uses limited permissions. Start with a fresh store name and let the Actor create it; do not pre-create the store yourself. Later runs by the same account can reuse that Actor-created store. An existing store created manually or by another Actor is unsupported and can fail with a permission error. If that happens, choose a fresh name. This Actor does not request additional access to unrelated stores in your account.

The first successful run saves a baseline and returns an empty `changes` array. Later runs report `added`, `updated` and `removed`. Tracked fields are title, location, canonical URL and available Lever department, commitment and workplace type. Description, salary and source update timestamps are not change triggers in this version.

A missing job is retained as pending on the first complete check where it is absent. It is reported as removed only if still absent on the next successful check. An incomplete response or outage fails the run without a board-check charge or advancing the baseline; the start fee still applies. A returning pending job is not falsely reported as newly added. Removal describes disappearance from the public board, not proof that the role was filled.

Maximum 5,000 jobs per board. Lever pagination is not an atomic source snapshot; repeated IDs are rejected, and two-run removal confirmation reduces transient false removals. Results are published before updating state. If the state write fails after publication, changes may be repeated on the next run; consumers should deduplicate event deliveries if required.

Configured price: $0.01 per successful check, including baseline checks and checks with zero changes, via `board-checked`, plus Apify's $0.00005 start event (one event at the default 256 MB memory). The price is per board check, not per change. Verify the current Pricing tab. The separate `SUMMARY` record reports counts and whether the budget stopped the run.

# Actor input Schema

## `board` (type: `string`):

A hosted Greenhouse or Lever board URL. Up to 5,000 jobs. Do not include filters.

## `snapshotStoreName` (type: `string`):

Choose a fresh name and let this Actor create the store; do not pre-create it. Reuse the name across later runs. Existing stores created outside this Actor are unsupported. Run only one writer per board/store pair. A new name resets the baseline.

## Actor input object example

```json
{
  "board": "https://job-boards.greenhouse.io/webflow",
  "snapshotStoreName": "job-monitor-snapshots"
}
```

# Actor output Schema

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

No description

## `summary` (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 = {
    "board": "https://job-boards.greenhouse.io/webflow",
    "snapshotStoreName": "job-monitor-snapshots"
};

// Run the Actor and wait for it to finish
const run = await client.actor("pietrofilippo/job-board-change-monitor").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 = {
    "board": "https://job-boards.greenhouse.io/webflow",
    "snapshotStoreName": "job-monitor-snapshots",
}

# Run the Actor and wait for it to finish
run = client.actor("pietrofilippo/job-board-change-monitor").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 '{
  "board": "https://job-boards.greenhouse.io/webflow",
  "snapshotStoreName": "job-monitor-snapshots"
}' |
apify call pietrofilippo/job-board-change-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pietrofilippo/job-board-change-monitor"
        }
    }
}
```

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/VYvw4Py2WpsYGnzT8/builds/8oKJGnx831SGum8YL/openapi.json