# Hiring Intent Account Watch — Who to Work This Week (`grokbob/hiring-intent-account-watch`) Actor

From $1.00 per 1,000 who-to-work decision cards with signals. Intent events free; empty/blocked/failed $0. Account book → Greenhouse/Ashby diffs → ranked next steps. NOT a jobs CSV / ATS pack.

- **URL**: https://apify.com/grokbob/hiring-intent-account-watch.md
- **Developed by:** [Bob](https://apify.com/grokbob) (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

$1.00 / 1,000 who-to-work decision cards

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 Intent Account Watch — Who to Work This Week

**Slug:** `hiring-intent-account-watch`\
**SKU:** **decision chain** — not a jobs CSV / ATS pack clone\
**Store:** public listing · https://apify.com/grokbob/hiring-intent-account-watch

Buyer named **account book** → watermarked Greenhouse / Ashby board diffs → **intent events** (under hood) → ranked **who-to-work** cards with **copy-ready next steps**.

***

### Vertical desk chain (MUST)

1. **Input** — your account book (`greenhouse` board\_token / `ashby` slug). Not scrape-the-internet.
2. **Sense** — watermarked diffs → intent events only: `new_req`, `closed_req`, `dept_surge`, `role_family_change`.
3. **Decide** — ranked **who to work this week** + why (account · signal · freshness). **One card per account.**
4. **Act** — `copyReadyNextStep` on each card. Open req titles = **evidence pointers**, not the SKU.

**Primary dataset view = `whoToWorkCard`.** Job JSON is evidence under the hood only. Flat job-row primary = **KILL**.

***

### Pricing

| Event | Price | Rule |
| --- | --- | --- |
| `decision-card` (primary) | **$0.001** · **$1.00 / 1,000** | Charge **once per account card with signals** (who-to-work). |
| Intent events | **$0** | Under hood — **not** billed as PPE. |
| Raw job rows | **never charged** | **Never** emitted as product. |
| `EMPTY` / `BLOCKED` / `FAILED` | **$0** | No charge. |
| Custom `actor-start` | **None** | Platform start fee only if ever run. |

***

### Input

| Field | Meaning |
| --- | --- |
| `accounts` | `{ id, provider, token\|slug }` or seeds `greenhouse:stripe` / `ashby:notion` |
| `watermarks` | Optional prior snapshots (else KV `WATERMARKS`) |
| `deltaOnly` | Default `true` — intent from diffs |
| `maxAccounts` | Hard cap (default 25) |
| `roleFamilyFilter` / `departmentFilter` | Optional |
| `dryRunMock` | Offline fixtures |

**Providers:** Greenhouse + Ashby only. **NO Workable · NO LinkedIn · NO Indeed.**

***

### Output (primary = decision card)

```json
{
  "rowType": "decision_card",
  "whoToWorkCard": true,
  "accountId": "stripe",
  "provider": "greenhouse",
  "rank": 1,
  "score": 12,
  "why": ["account=stripe (greenhouse)", "signal=new_req×3", "freshness=2026-09-30T…"],
  "openReqTitlePointers": ["Software Engineer, Backend", "Account Executive, Enterprise"],
  "copyReadyNextStep": "Work stripe this week — hiring intent on Greenhouse board \"stripe\". …",
  "signalSummary": { "new_req": 3 },
  "hasSignals": true,
  "status": "OK",
  "billed": true,
  "chargeEvent": "decision-card"
}
```

Intent events (`rowType: intent_event`) are secondary / under hood.

***

### Free path (Gate PASS elegant)

- Greenhouse: `https://boards-api.greenhouse.io/v1/boards/{token}/jobs?content=true`
- Ashby: `https://api.ashbyhq.com/posting-api/job-board/{slug}`
- Auth: none. UA: `grokbob/hiring-intent-account-watch`
- Polite sequential GETs · ~350ms+ pacing · backoff 429/5xx · hard cap accounts/run

***

### Kill-locks

1. NOT jobs CSV / multi-ATS pack clone / twin of `ats-jobs-undercut-pack-ppe`
2. NOT Workable / LinkedIn / Indeed
3. NOT Pure PPE job-row theater
4. MUST watchlist → watermark → intent → **who-to-work card** → copy-ready next step
5. Primary output = job rows → **FAIL / Challenge KILL**
6. CapEx $0 face rebuilds only · no invent/PPE drift · Soft Elite only after stranger use

***

### Status

**Public Store listing** — Console `decision-card` sticker locked **$0.001** · **$1.00 / 1,000**. Soft Elite credit only after stranger use (owner runs ≠ board Elite). See `READINESS.md`.

# Actor input Schema

## `accounts` (type: `array`):

Named accounts to watch. Objects {id, provider, token|slug} or strings greenhouse:stripe / ashby:notion. Greenhouse + Ashby only — no Workable/LinkedIn/Indeed.

## `seeds` (type: `array`):

Optional string seeds alias for accounts: greenhouse:stripe, ashby:notion.

## `watermarks` (type: `object`):

Per-account prior snapshot (jobIds / jobIdHash / deptCounts). Usually persisted in KV key WATERMARKS.

## `deltaOnly` (type: `boolean`):

Emit intent from watermark diffs. First run (empty watermark) yields new\_req events; matching watermark yields fewer/no new events.

## `maxAccounts` (type: `integer`):

Hard cap accounts/run (polite sequential).

## `roleFamilyFilter` (type: `array`):

Optional: engineering, sales, marketing, product, design, talent, finance, legal, operations, data, other.

## `departmentFilter` (type: `array`):

Optional substring match on department names.

## `dryRunMock` (type: `boolean`):

Offline fixtures only; no upstream board calls.

## Actor input object example

```json
{
  "accounts": [
    {
      "id": "stripe",
      "provider": "greenhouse",
      "token": "stripe"
    },
    {
      "id": "notion",
      "provider": "ashby",
      "slug": "notion"
    }
  ],
  "seeds": [],
  "watermarks": {},
  "deltaOnly": true,
  "maxAccounts": 25,
  "roleFamilyFilter": [],
  "departmentFilter": [],
  "dryRunMock": false
}
```

# Actor output Schema

## `whoToWorkCards` (type: `string`):

No description

## `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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "accounts": [
        {
            "id": "stripe",
            "provider": "greenhouse",
            "token": "stripe"
        },
        {
            "id": "notion",
            "provider": "ashby",
            "slug": "notion"
        }
    ],
    "seeds": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("grokbob/hiring-intent-account-watch").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 = {
    "accounts": [
        {
            "id": "stripe",
            "provider": "greenhouse",
            "token": "stripe",
        },
        {
            "id": "notion",
            "provider": "ashby",
            "slug": "notion",
        },
    ],
    "seeds": [],
}

# Run the Actor and wait for it to finish
run = client.actor("grokbob/hiring-intent-account-watch").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 '{
  "accounts": [
    {
      "id": "stripe",
      "provider": "greenhouse",
      "token": "stripe"
    },
    {
      "id": "notion",
      "provider": "ashby",
      "slug": "notion"
    }
  ],
  "seeds": []
}' |
apify call grokbob/hiring-intent-account-watch --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,grokbob/hiring-intent-account-watch"
        }
    }
}
```

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/614dSi29rXT5Qshiw/builds/y6MAYNJNzbLWlBngA/openapi.json