# Company Hiring Signals — Greenhouse, Lever & Ashby (`asd111/hiring-signal-monitor`) Actor

Turn public job boards into hiring intelligence: open roles by department, eng/sales/GTM split, remote share, 7-day velocity. Monitor mode sends webhook alerts when new roles appear. Official APIs, no login. For Clay, n8n & GTM teams.

- **URL**: https://apify.com/asd111/hiring-signal-monitor.md
- **Developed by:** [叁 时](https://apify.com/asd111) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

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

## Company Hiring Signals — Greenhouse, Lever & Ashby

Turn any company's public job board into structured hiring intelligence.

Enter a list of companies. The Actor pulls their live job postings from **Greenhouse, Lever, and Ashby** (official public job-board APIs — no login, no anti-bot) and returns one clean signal row per company:

- 📊 **Open roles** — total count, top hiring departments
- 🧑‍💻 **Role mix** — engineering / sales / GTM split
- 🌍 **Remote share** — share of remote-friendly roles
- ⚡ **Velocity** — roles posted in the last 7 days, newest posting date
- 🔔 **Monitor mode** — scheduled diffs + webhook alerts when new roles appear

### Who uses this

| Use case | Example |
|---|---|
| **Sales & GTM teams** | A prospect suddenly hiring 3 SDRs + a RevOps lead is building a sales org — a buying signal for outreach timing. |
| **Recruiters & sourcing** | Track target companies; get alerted the day a relevant role opens. |
| **Market & competitor research** | Watch hiring trends across a portfolio of companies over time. |
| **Clay / n8n / Zapier workflows** | Flat output rows drop straight into enrichment tables and automations. |

### Output fields

| Field | Type | Meaning |
|---|---|---|
| `company` | string | Company display name |
| `platform` | string | `greenhouse` | `lever` | `ashby` |
| `boardUrl` | string | The company's job board URL |
| `totalOpenRoles` | number | Open roles right now |
| `engRoles` / `salesRoles` / `gtmRoles` | number | Role counts by function |
| `topHiringDepts` | string | Top 3 departments, e.g. `Engineering(92), Data(28)` |
| `remoteShare` | number | Remote-friendly share (0–1) |
| `newRolesLast7d` | number | Roles posted in the last 7 days |
| `newestPostedAt` | date | Most recent posting date |
| `checkedAt` | date | Timestamp of this check |
| `error` | string? | Only present when the board was not found |

Monitor mode adds: `newJobCount`, `newJobs[]` (title, department, URL, posted date), `webhookSent`.

### Quick start

1. Add companies — each entry needs its ATS `handle`. To find it, open the company's careers page: `job-boards.greenhouse.io/<HANDLE>`, `jobs.lever.co/<HANDLE>`, or `jobs.ashbyhq.com/<HANDLE>`. That path segment is the handle (e.g. `stripe`, `palantir`, `linear`).
2. Leave `platform` empty to auto-detect, or set it explicitly.
3. Run. For monitoring, switch `mode` to `monitor`, add a `webhookUrl`, and schedule the Actor daily.

#### Example input

```json
{
  "mode": "enrich",
  "companies": [
    { "handle": "stripe", "platform": "greenhouse", "name": "Stripe" },
    { "handle": "linear", "platform": "ashby", "name": "Linear" }
  ]
}
```

#### Example output

```json
{
  "company": "Stripe",
  "platform": "greenhouse",
  "boardUrl": "https://job-boards.greenhouse.io/stripe",
  "totalOpenRoles": 654,
  "engRoles": 193,
  "salesRoles": 151,
  "gtmRoles": 44,
  "remoteShare": 0.16,
  "newRolesLast7d": 75,
  "newestPostedAt": "2026-09-17",
  "topHiringDepts": "Account Executives EMEA(22), Global Operations(20), University(15)",
  "checkedAt": "2026-09-17T09:00:00Z"
}
```

### Monitor mode (daily radar)

Run the Actor on an **Apify Schedule** (e.g. every day). The Actor stores a snapshot per company and, on each run:

1. Diffs current postings against the last snapshot,
2. POSTs `newJobs[]` to your `webhookUrl` (Slack, n8n, Zapier, email bridge),
3. Reports `newJobCount` in the dataset.

The first run establishes the baseline (no alerts). From the second run on, you only hear about what changed. Webhook retries with backoff; failed deliveries are flagged in the output, never silently dropped.

> Tip: point the webhook at [n8n](https://n8n.io) or Zapier to route alerts into Slack, email, or your CRM.

### Pricing

- **$0.04 per company check** — includes signals, snapshot diffing and webhook alerts
- **$0.002 per job row** — only when `includeJobList` is enabled

New Apify accounts get a $5/month platform credit, enough to test with.

### Data source & limitations

Data comes from the official public job-board APIs of Greenhouse, Lever, and Ashby — postings are exactly what each company publishes publicly. Department and remote data depend on what the company exposes on its board (e.g. some Greenhouse boards don't publish departments; remote status is then inferred from location text). Role-function classification (eng/sales/GTM) is keyword-based; tell us if your definitions differ and we'll tune it.

### Support

Found a bug or need a field added? Open an issue on the Actor page or leave a review — issues are typically answered within a few days.

# Actor input Schema

## `mode` (type: `string`):

enrich: one-shot signals per company (Clay-friendly flat rows). monitor: diff against the last snapshot and POST your webhook when new roles appear (run daily via Apify Schedule).

## `companies` (type: `array`):

Companies to check. Each needs an ATS board handle (e.g. 'stripe', 'palantir', 'linear'). Leave platform empty to auto-detect.

## `webhookUrl` (type: `string`):

monitor mode only: POST target for new-role alerts (Slack webhook, n8n, Zapier, email bridge)

## `includeJobList` (type: `boolean`):

Also emit every job as a dataset row (charged as job-detail events)

## `concurrency` (type: `integer`):

Parallel company checks

## Actor input object example

```json
{
  "mode": "enrich",
  "companies": [
    {
      "handle": "stripe",
      "platform": "greenhouse"
    },
    {
      "handle": "palantir",
      "platform": "lever"
    },
    {
      "handle": "linear",
      "platform": "ashby"
    }
  ],
  "includeJobList": false,
  "concurrency": 3
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `exampleBoardUrl` (type: `string`):

No description

## `exampleTotalOpenRoles` (type: `string`):

No description

## `exampleNewRoles7d` (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 = {
    "companies": [
        {
            "handle": "stripe",
            "platform": "greenhouse"
        },
        {
            "handle": "palantir",
            "platform": "lever"
        },
        {
            "handle": "linear",
            "platform": "ashby"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("asd111/hiring-signal-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 = { "companies": [
        {
            "handle": "stripe",
            "platform": "greenhouse",
        },
        {
            "handle": "palantir",
            "platform": "lever",
        },
        {
            "handle": "linear",
            "platform": "ashby",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("asd111/hiring-signal-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 '{
  "companies": [
    {
      "handle": "stripe",
      "platform": "greenhouse"
    },
    {
      "handle": "palantir",
      "platform": "lever"
    },
    {
      "handle": "linear",
      "platform": "ashby"
    }
  ]
}' |
apify call asd111/hiring-signal-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,asd111/hiring-signal-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/Z18eQYwwjARDTQM9d/builds/jeK1nyKBJ4KNBYw8H/openapi.json