# Hiring Signals Monitor (`durative_entablature/hiring-signals-monitor`) Actor Monitor companies' Greenhouse, Lever and Ashby job boards and get only what changed: new and removed job postings since the last run. Hiring signals for sales, recruiting and market intel. Pay per board checked and per change; first runs are free. - **URL**: https://apify.com/durative_entablature/hiring-signals-monitor.md - **Developed by:** [Michael Workman](https://apify.com/durative_entablature) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $3.00 / 1,000 board checkeds 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 ## Hiring Signals Monitor Know when target companies start or stop hiring. Give this Actor the job boards of the companies you care about, on **Greenhouse**, **Lever** or **Ashby**, schedule it (say, daily), and each run reports only what changed: **New** postings that appeared and **Removed** postings that disappeared since the last check. A new posting is a strong signal. A company hiring its first RevOps lead is shopping for sales tools. A burst of security roles means a security budget. A team that stops posting may have frozen hiring. Sales, recruiting and market-intel teams use these signals to time outreach, without checking careers pages by hand or paying for an intel platform. Have a question? See the [FAQ](#faq). ### Why this Actor - **Changes only.** Generic job-board tools re-output every posting on every run and leave you to work out what's different. This Actor remembers what it saw and outputs the difference. - **Pay for signal, not volume.** You're charged per board checked and per change found. Unchanged boards cost a fraction of a cent, and first runs, failures and alerts are free (see [Pricing](#pricing)). - **No false alarms from outages.** A board that times out or errors keeps its snapshot, so a flaky run never reports postings as removed. A sudden collapse (most of a big board vanishing at once) is reported as one alert instead of hundreds of removals. - **Official public APIs.** It reads each ATS's public job-board API, the same data the company's careers page shows. No browser, no proxies, no login. A run over 100 boards takes a few minutes. - **Your data stays in your account.** Snapshots live in a key-value store in your own Apify account. ### Quick start 1. Click **Try for free**, and paste job-board URLs (or `ats:slug` references) into **Boards**. 2. Run it. The first run outputs every current posting marked `baseline`, so you can see it working. 3. Schedule it (for example daily), and connect the output to email, Slack, Google Sheets or your CRM with Apify **Integrations**, or set **Webhook URL**. From then on each run outputs only New and Removed postings, plus any alerts. ### Input | Field | Description | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Boards** (required) | One board per line, as `ats:slug` or a job-board URL (see below). Invalid entries are reported in the output without failing the run. The same board written two ways is checked once. | | **Watchlist name** | Default `default`. Each name keeps its own snapshots, so you can run separate watchlists (e.g. `competitors`, `prospects`) that don't interfere. | | **Output Baseline Postings** | Default on. The first check of a board has nothing to compare against. When on, its current postings are output as `baseline`. Turn off to add boards to an existing watchlist without flooding your integrations; the snapshot is recorded either way. | | **Webhook URL** | Optional. Each run with something to report sends one POST to this URL (see [Webhook](#webhook)). | #### Naming a board | ATS | `ats:slug` | Job-board URLs recognized | | ---------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | Greenhouse | `greenhouse:stripe` | `https://boards.greenhouse.io/stripe`, `https://job-boards.greenhouse.io/stripe`, `https://boards.greenhouse.io/embed/job_board?for=stripe` | | Lever | `lever:palantir` | `https://jobs.lever.co/palantir`, `https://jobs.eu.lever.co/` | | Ashby | `ashby:ramp` | `https://jobs.ashbyhq.com/ramp` | The slug is the company's name in its job-board URL. Lever boards hosted in the EU are found automatically. #### Example ```json { "boards": ["greenhouse:stripe", "https://jobs.lever.co/palantir", "https://jobs.ashbyhq.com/ramp"], "watchlistName": "prospects", "outputBaseline": true, "webhookUrl": "https://hooks.zapier.com/hooks/catch/123456/abcdef/" } ``` ### Output One dataset item per posting or alert, each with a `type`, so you can filter in the Apify Console or in integrations: | `type` | Meaning | Charged | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | `new` | The posting is on the board now but wasn't at the last successful check. | yes | | `removed` | The posting was on the board at the last successful check and is gone now. Its details are as last seen. We only know it disappeared, not why. | yes | | `baseline` | A current posting from a board's first check (only when **Output Baseline Postings** is on). | free | | `board-not-found` | The ATS says the board doesn't exist. Check the reference, or the company may have moved to another ATS. | free | | `check-failed` | The board couldn't be checked this run (timeout, error, malformed response). Its snapshot is untouched; the next successful check picks up where the last left off. | free | | `suspicious-drop` | A board with more than 10 postings suddenly lost over 80% of them. Reported instead of individual removals, and the snapshot is kept. If the drop persists for 3 consecutive checks it's accepted: that run reports the removals. | free | | `invalid-board-reference` | An entry in **Boards** that isn't a recognized board reference. | free | | `run-summary` | Always the last item: boards checked (baselines and suspicious drops included), skipped because of your charge limit, failed and not found. | free | Posting items carry `watchlist`, `board`, `ats`, `postingId`, `title`, `location`, `department`, `url`, `compensation` (when the ATS publishes it) and `publishedAt`. Alerts carry `watchlist`, `board`, `ats` and a human-readable `message`. ```json { "type": "new", "watchlist": "sample", "board": "greenhouse:stripe", "ats": "greenhouse", "postingId": "8172510", "title": "Abuse Investigator", "location": "Seattle, San Francisco, New York City", "department": "8611 Security Analytics", "url": "https://stripe.com/jobs/search?gh_jid=8172510", "compensation": null, "publishedAt": "2026-09-09T14:50:29.000Z" } ``` A sample of every item type is in [`docs/sample-output.json`](docs/sample-output.json). ### Webhook If **Webhook URL** is set, each run that outputs at least one item sends a single `POST` with a JSON body: ```json { "summary": { "type": "run-summary", "watchlist": "prospects", "boardsChecked": 3, "boardsSkippedByLimit": 0, "boardsFailed": 0, "boardsNotFound": 0 }, "items": [{ "type": "new", "board": "greenhouse:stripe", "title": "Abuse Investigator", "...": "..." }] } ``` `items` holds the same items as the dataset, in the same order, without the run summary. Quiet runs (no items output) send nothing; a run with only `baseline` postings still sends. If the endpoint fails or times out, a warning is logged and the run still succeeds; the results are always in the dataset. The URL is stored as a secret input. ### Pricing Pay per event: | Event | Price | When | | ------------- | ------ | ------------------------------------------------------------- | | Board checked | $0.003 | Each successful check of a board that already has a snapshot. | | Change | $0.01 | Each `new` or `removed` posting. | Everything else is free: a board's first check (its baseline), failed checks, boards not found, suspicious drops and invalid references. **Example:** a daily watchlist of 100 boards that turns up 5 changes a day costs 100 × $0.003 + 5 × $0.01 = **$0.35 a day**, about $10.50 a month. **Your max charge per run is respected.** A board is charged all at once, before its results are output. If its charges would go over your limit, that board and every board after it are skipped, and their snapshots are untouched. The next run reports and charges their changes exactly once, so nothing is lost or double-charged. The run summary and log say how many boards were skipped. ### How snapshots work The first successful check of a board records its postings as the board's **snapshot**; that check is its **baseline**. Each later successful check compares against the snapshot, outputs the differences and updates it. Postings are matched by the ATS's own job ID. - Snapshots are kept per watchlist, in a key-value store named `hiring-signals-` in your Apify account. Deleting that store, or renaming the watchlist, starts fresh with a new baseline. Names ignore case and punctuation, so a rename such as `Prospects` to `prospects` keeps the same snapshots. - **Adding a board** to a watchlist baselines just that board; the others keep their snapshots. A board that was removed and added back isn't baselined again: it's compared against its old snapshot. - **Removing a board** stops checking it. Its postings are not reported as removed. - A failed check, a board not found, a suspicious drop or a board skipped by your charge limit never changes the snapshot. ### Limitations - **Three ATSes:** Greenhouse, Lever and Ashby. Workday, iCIMS, SmartRecruiters and others aren't supported yet. - **You supply the board.** The Actor doesn't find a company's job board from its name or website. Open the company's careers page and copy the job-board URL. - **New and Removed only.** Edits to an existing posting (title, location, pay) aren't reported. - **Public postings only:** what the company's public job board shows. Internal or unlisted postings are invisible. - **Compensation** appears only when the company publishes it on Lever or Ashby, so coverage varies by company. Greenhouse's public API doesn't include it. - **Running more often than daily** rarely adds much: job boards change slowly. Each run is charged per board checked, so frequent schedules cost more for the same signals. ### FAQ #### Getting started **How do I find a company's job board?** Open the company's careers page and click into any job. If the link goes to `greenhouse.io`, `lever.co` or `ashbyhq.com`, copy that board URL into **Boards**. See [Naming a board](#naming-a-board) for the formats recognized. **What if the company uses Workday, iCIMS or another ATS?** It can't be monitored yet. Only Greenhouse, Lever and Ashby are supported. **Does a Lever board in the EU need anything special?** No. If a Lever board isn't found in the US region, the Actor checks the EU region automatically. **How often should I run it?** Daily suits most teams. Job boards change slowly, so running more often rarely finds more, and every run is charged per board checked. **How do I schedule it?** In the Apify Console, open **Schedules**, create one (for example, every day at 8:00) and add this Actor with your saved input. *** #### Watchlists and boards **What's a watchlist for?** It keeps a separate set of snapshots, so you can monitor `competitors` and `prospects` without them interfering. Names ignore case and punctuation: `Prospects` and `prospects` are the same watchlist. **How do I add boards without flooding Slack or my CRM?** Turn off **Output Baseline Postings** for the run where you add them. New boards are baselined silently and only later changes are output. Boards already in the watchlist aren't affected. **What happens if I remove a board?** It stops being checked. Its postings aren't reported as removed. **What if I add a removed board back later?** Its snapshot is still kept, so it isn't baselined again. The next check compares against what it saw last time and reports, and charges, every change since. To start that board fresh, use a new watchlist name. **How do I start a watchlist over?** Delete its `hiring-signals-` key-value store in the Apify Console, or use a new watchlist name. The next run baselines every board again, for free. *** #### Results **Why did my first run output so many items?** That's the baseline: every current posting on each new board, so you can see what's there. It's free. Turn off **Output Baseline Postings** if you'd rather not see it. **A run output nothing but the summary. Is it working?** Yes: nothing changed on your boards since the last run. The summary shows how many boards were checked. **Does `removed` mean the role was filled?** Not necessarily. The posting disappeared from the public board. It may have been filled, paused, cancelled or reposted under a new ID. **Are edits to a posting reported?** No. Changes to a title, location or pay on an existing posting aren't reported, only new and removed postings. **Why is `compensation` empty?** It's filled only when the company publishes pay on Lever or Ashby. Greenhouse's public job-board API doesn't include pay, so Greenhouse postings always show `null`. *** #### Pricing **What's free?** A board's baseline, failed checks, boards not found, suspicious drops and invalid references. You're never charged for a board that couldn't be checked. See [Pricing](#pricing) for the rates. **Which boards are skipped when my max charge per run is reached?** Boards are processed in the order you list them, so skipping starts from the bottom of the list. Put your most important boards first. Skipped boards are picked up on the next run, with nothing lost or charged twice. *** #### Webhooks and integrations **My integration didn't receive anything.** Runs that output no items send nothing. Otherwise, check the run log for a webhook warning; the results are always in the run's dataset. **What does my webhook endpoint need to do?** Accept a JSON `POST` and answer with a 2xx status within 30 seconds. Redirects aren't followed, so use the final URL. *** #### Alerts and troubleshooting **A board shows `board-not-found`.** Check the spelling of the slug against the company's job-board URL. If it used to work, the company has probably moved to a different ATS; find its new careers page and update the reference. **A board shows `check-failed`.** The ATS timed out (after 30 seconds) or returned an error. The snapshot is untouched, so nothing is reported as removed, and the next successful check picks up where the last one left off. If it fails every run, check the board still loads in your browser. **A board shows `suspicious-drop`.** A board with more than 10 postings lost over 80% of them at once, which usually means an outage or a board migration. You get one alert instead of hundreds of removals, and the snapshot is kept. If the drop persists for 3 consecutive checks, it's accepted and that run reports the removals. **An entry shows `invalid-board-reference`.** That line isn't a recognized board. Use `greenhouse:`, `lever:` or `ashby:` plus the slug, or a job-board URL from [Naming a board](#naming-a-board). The rest of the run continues normally. *** #### Data and privacy **Where are my snapshots stored?** In a key-value store in your own Apify account. They aren't shared with the Actor's developer. **Is my webhook URL kept private?** Yes. It's stored as a secret input and left out of logs and error messages, since webhook URLs often embed a token. **Is this legal?** The Actor reads the same public job-board data every visitor to the company's careers page sees, through the ATS's public API. It sends modest request volumes and identifies itself. You're responsible for how you use the data. **Where can I get help?** Open an issue on the Actor's **Issues** tab, with the run link and the board reference involved. # Actor input Schema ## `boards` (type: `array`): Job boards to monitor, one per line, as `ats:slug` on Greenhouse, Lever or Ashby (e.g. `greenhouse:stripe`, `lever:palantir`, `ashby:ramp`) or a job-board URL (e.g. `https://job-boards.greenhouse.io/stripe`, `https://jobs.lever.co/palantir`, `https://jobs.ashbyhq.com/ramp`). Invalid entries are reported in the output without failing the run; duplicates are checked once. ## `watchlistName` (type: `string`): Name of this Watchlist. Each name keeps its own history (in a named key-value store in your account), so separate Watchlists don't interfere. ## `outputBaseline` (type: `boolean`): The first Check of a Board (its Baseline) has nothing to compare against. When on, its current Postings are output marked as Baseline; when off, they're recorded silently and only later Changes are output. Turn off to add Boards to an existing Watchlist without flooding your integrations. ## `webhookUrl` (type: `string`): Optional. When set, each run sends one POST with a JSON body `{ "summary": , "items": [] }` to this URL, e.g. a Zapier, Make or n8n webhook. Runs with nothing to report send nothing. If the POST fails, a warning is logged and the run still succeeds; the results are always in the dataset. ## Actor input object example ```json { "boards": [ "greenhouse:stripe", "lever:palantir", "ashby:ramp" ], "watchlistName": "default", "outputBaseline": true } ``` # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "boards": [ "greenhouse:stripe", "lever:palantir", "ashby:ramp" ] }; // Run the Actor and wait for it to finish const run = await client.actor("durative_entablature/hiring-signals-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "boards": [ "greenhouse:stripe", "lever:palantir", "ashby:ramp", ] } # Run the Actor and wait for it to finish run = client.actor("durative_entablature/hiring-signals-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 '{ "boards": [ "greenhouse:stripe", "lever:palantir", "ashby:ramp" ] }' | apify call durative_entablature/hiring-signals-monitor --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,durative_entablature/hiring-signals-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 ` 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/wFZVylSGB2NehebXC/builds/LPN9OTHwt8ekOl0FM/openapi.json