# Hiring Signal Radar | Greenhouse, Lever & Ashby (`guille_innovai/my-actor`) Actor

Monitor public job postings from Greenhouse, Lever, and Ashby. Detect hiring changes, extract structured job data, and export evidence-backed business intelligence reports and CRM-ready CSV files.

- **URL**: https://apify.com/guille_innovai/my-actor.md
- **Developed by:** [Guillermo de Leon](https://apify.com/guille_innovai) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 job listings

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 Signal Radar — Greenhouse, Lever & Ashby to CRM

**Public-job intelligence for recruiting analytics, RevOps research and market monitoring. No API keys required.**

Fetch normalized open job postings from up to **12 public company job boards** across Greenhouse, Lever and Ashby. Save them as exportable dataset rows, compare them to a prior snapshot you own, and optionally get an **evidence-linked CRM research CSV** explaining which hiring roles might be relevant to sales operations. No candidate data, private credentials, or auto outreach.

### What you get

- **Dataset**: individual jobs with title, public URL, location, provider, department (where available), compensation (where disclosed), date signal, deterministic ID and fingerprint.
- **Storage → Key-value store → `SNAPSHOT`**: all current normalized jobs; copy into `previousSnapshot` on a subsequent run to identify additions, changes and removals.
- **`SUMMARY`**: boards checked, results counted, errors, comparison status and safety caps.
- **`OPPORTUNITIES`**: company-board-level *research hypotheses*, including role evidence and explainable triage scores.
- **`CRM_EXPORT`**: ready-to-review CSV; buyer identity, email address, buying intent, company size and pain are **not invented**.

#### Copy-paste first run

```json
{
  "sources": [
    {"provider": "ashby", "board": "Ashby"},
    {"provider": "greenhouse", "board": "12twenty"},
    {"provider": "lever", "board": "toptal"}
  ],
  "maxJobsPerSource": 100,
  "previousSnapshot": [],
  "emitUnchanged": false,
  "includeOpportunities": true,
  "includeStableOpportunities": true
}
```

A board is the **slug** from its public careers page, *not* its full URL. Example: from `https://jobs.lever.co/toptal`, choose provider `lever`, board `toptal`; from `https://jobs.ashbyhq.com/Ashby`, choose `ashby`, board `Ashby`. For Lever EU select `region: "eu"`.

The first run is a **baseline**, never evidence of a freshly opened position. On a later run, paste the JSON from the first run's `SNAPSHOT` into `previousSnapshot` to classify `new`, `updated`, and `removed`. There is no automatic cross-run history in this Store edition, by design: your state remains in your own run's storage. You can export that state into a scheduler or another workflow if you want to automate the handoff.

### Pay only for relevant postings

You can narrow the returned job rows with optional `titleKeywords`, `locationKeywords`, and `remoteOnly` parameters. By default `titleKeywords` searches **only the job title**, avoiding jobs that match merely because their department is Sales. For broader research set `titleSearchScope: "title_department_team"` explicitly. These filters are case-insensitive and evaluated before rows are written to the paid dataset. A job must match at least one title term **and** one location term (when both are supplied). For example:

```json
{
  "sources": [
    {"provider": "ashby", "board": "Ashby"},
    {"provider": "greenhouse", "board": "12twenty"}
  ],
  "maxJobsPerSource": 100,
  "titleKeywords": ["sales", "account executive", "revenue operations"],
  "titleSearchScope": "title_only",
  "locationKeywords": ["remote", "united states"],
  "remoteOnly": false,
  "previousSnapshot": [],
  "includeOpportunities": true
}
```

The default `titleSearchScope: "title_only"` ignores `department` and `team`; choose `title_department_team` only if you intentionally want to broaden the results. A public test using keywords `sales` and `account executive` emitted 31 postings under the broader legacy logic; 6 of those did not match either keyword in the visible title. This stricter default should exclude them when the same postings remain available, but the exact count can change over time.

`remoteOnly` relies on a remote label in the ATS-provided location or workplace field. It does **not** invent a remote flag from the job title. Filters are applied **after** the configured cap per provider, so if a board has more jobs than the cap, matching roles beyond that cap may not be fetched. Increase `maxJobsPerSource` (maximum 500) when broader coverage is needed; this can increase platform processing. The saved `SNAPSHOT` keeps all **fetched** records regardless of filters, preserving comparisons across runs. `SUMMARY.changes` counts all fetched changes, while `SUMMARY.dataset_rows` and `SUMMARY.filters.items_emitted` represent the billable output after filtering. If no jobs match, only the low start-event fee may apply.

### What opportunity signals mean

The optional CRM report maps job titles in sales, customer acquisition, sales operations, CRM administration and demand generation into transparent, reviewable research hypotheses. It **does not prove** an actual problem, purchasing intent, spending ability or a reachable buyer. Existing postings remain `RESEARCH`; new relevant roles can raise the activity priority only after **you** provide a prior snapshot. A sales hypothesis is not a verified lead. Outputs include `outreach_ready: false` and qualification gaps until independently researched.

### Limits and reliability

- Up to 12 job boards per run; 1–500 jobs per board, default 100.
- Only fixed Greenhouse, Lever, Ashby public API domains are called (no user-supplied URLs, cookies, proxies or redirects).
- When a board fails or the maximum record cap truncates its list, the Actor **does not infer removed postings** from missing results.
- Dates differ across providers: Greenhouse `updated_at`, Lever `createdAt` and Ashby `publishedAt` are different concepts and **not directly comparable**.
- No database subscriptions, outreach, personal-email scraping, company-size verification or warranty of purchase intent.
- The public Store edition **rejects `autoTrack: true`**. Never supply other users' prior snapshots.
- Company labels use board slugs, not verified legal entities. Multiple boards for one company can produce separate records.
- Please respect each provider's terms and local data laws. Public postings can change or become unavailable.

### Pricing and payment

If a developer configures pay-per-event monetization in the Apify Console, customers are charged according to the clearly displayed **Store listing price and events**. The standard default-dataset-item event supports per-result pricing without additional code; start events can cover initial compute costs. *No monetization is enabled by this README.* Billing, event prices and actual costs are managed by Apify Console.

### Integration

Use the Apify REST API or schedule an Actor run to get public jobs. To build a recurring diff pipeline, keep and feed back your latest `SNAPSHOT` as next run's `previousSnapshot`. Unchanged jobs are omitted by default for a smaller event dataset. For raw research on an existing board, set `includeStableOpportunities: true`.

### Support and source

The source is maintained in a GitHub repository. Issues should contain public board slugs, provider, error summary and sanitized settings, but never credentials or customer data.

API references:

- https://developers.greenhouse.io/job-board.html
- https://github.com/lever/postings-api
- https://developers.ashbyhq.com/docs/public-job-posting-api
- https://docs.apify.com/actors/publishing/monetize

Run checks before deploying this edition: `python -m unittest discover -s tests -v`.

**Disclaimer:** This is a data monitoring and research tool, not a recruiting platform, financial forecast or qualified-lead database.

# Actor input Schema

## `sources` (type: `array`):

Array of objects with provider (greenhouse, lever, ashby), board slug (not URL), and optional region (global or eu for Lever). Example uses Ashby's own board.

## `maxJobsPerSource` (type: `integer`):

Hard cap on processed jobs per board. A cap hit disables removal detection.

## `previousSnapshot` (type: `array`):

Optional: paste the SNAPSHOT JSON from your own previous run to label new, updated and removed postings. Public edition does not access persistent customer history.

## `emitUnchanged` (type: `boolean`):

When comparing runs, include unchanged jobs in the output dataset.

## `includeOpportunities` (type: `boolean`):

Write OPPORTUNITIES JSON and CRM_EXPORT CSV based on matching job titles. These are research hypotheses, not qualified sales leads.

## `includeStableOpportunities` (type: `boolean`):

Optionally include stable existing jobs as research leads. These are never claimed as new openings.

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

Optional: match one of these terms against job title by default (not department or team). For expanded matching select titleSearchScope. Case-insensitive; maximum 20 keywords.

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

Optional: include only jobs with one of these words in location or workplace. Case-insensitive. Multiple terms use OR.

## `remoteOnly` (type: `boolean`):

Only include jobs whose source explicitly indicates remote/remoto in the location or workplace text. Missing remote labels are not assumed remote.

## `titleSearchScope` (type: `string`):

title_only (recommended) avoids results that match only a department or internal team. title_department_team broadens matching for specialized research.

## Actor input object example

```json
{
  "sources": [
    {
      "provider": "ashby",
      "board": "Ashby"
    }
  ],
  "maxJobsPerSource": 100,
  "previousSnapshot": [],
  "emitUnchanged": false,
  "includeOpportunities": true,
  "includeStableOpportunities": false,
  "titleKeywords": [],
  "locationKeywords": [],
  "remoteOnly": false,
  "titleSearchScope": "title_only"
}
```

# Actor output Schema

## `jobs` (type: `string`):

Normalized public job listings stored in the default dataset.

## `opportunities` (type: `string`):

Board-level hypotheses with evidence and qualification caveats; not verified customers.

## `crmExport` (type: `string`):

CSV with publicly observed signals; no invented buyer contacts.

## `summary` (type: `string`):

Collection status, counts, source errors and completeness.

## `snapshot` (type: `string`):

Copy into previousSnapshot on a future run to compare opening 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 = {
    "sources": [
        {
            "provider": "ashby",
            "board": "Ashby"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("guille_innovai/my-actor").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 = { "sources": [{
            "provider": "ashby",
            "board": "Ashby",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("guille_innovai/my-actor").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 '{
  "sources": [
    {
      "provider": "ashby",
      "board": "Ashby"
    }
  ]
}' |
apify call guille_innovai/my-actor --silent --output-dataset

```

## MCP server setup

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

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/mFcnatZQqe4CuQDEV/builds/MNPGnRLITeq4H2cnW/openapi.json