Client Hiring Signal Monitor

Know the moment one of your own target-account companies starts hiring in your niche — before the req goes stale and a competing agency gets there first. Built for staffing/recruiting agencies and embedded recruiters, not as another firehose of every company on the internet.

What you get, per run:

• Know instantly when a target account starts hiring — watched across Greenhouse, Lever, Ashby and Workable, not just the one ATS you happen to check manually.
• See the trend, not just a snapshot — a growing / shrinking / steady / new signal per company, comparing this run's matching-role count to last run's, so you can tell real momentum from noise.
• Only what's new — by default you're alerted to newly-posted matching roles only, not re-notified about the same postings every run.

Sample output (one row per company, real shape):

{
  "company": "Acme Robotics",
  "ats": "greenhouse",
  "token": "acmerobotics",
  "hiring": true,
  "matchCount": 3,
  "previousMatchCount": 1,
  "expansionSignal": "growing",
  "matches": [
    {
      "id": "6789012",
      "title": "Senior Backend Engineer",
      "location": "Remote (US)",
      "url": "https://job-boards.greenhouse.io/acmerobotics/jobs/6789012",
      "postedAt": "2026-09-19T14:02:00.000Z",
      "isRemote": true
    }
  ],
  "firstSeenRoleAt": "2026-08-30T09:15:00.000Z",
  "checkedAt": "2026-09-21T10:00:00.000Z"
}

• No web scraping, no headless browser — four documented public ATS job-board JSON APIs, the same endpoints each ATS's own careers-page widget calls.
• Read-only. Never applies, never writes to any external system.
• Your list, not the market. You supply the companies. This is deliberately not a firehose of every company using these ATSs.
• Full behaviour is in ./SPEC.md. Part of the RecruitOps suite alongside candidate-cross-reference — use that one to verify/enrich a candidate before you pitch them for a role this actor surfaces.

---

1. Quick start (Apify Console)

1. Open the Actor, paste this into Input, and click Start:

   {
     "companies": [
       { "name": "Example Co", "ats": "greenhouse", "token": "examplecoinc" },
       { "name": "Another Co", "ats": "lever", "token": "anotherco" }
     ],
     "rolePatterns": ["backend engineer", "site reliability"],
     "remoteOnly": false,
     "emitMode": "new_only"
   }
   

2. The first run seeds each company's state and emits no matches (so you're not flooded on setup) — but you'll still see each company's current matchCount and hiring status right away.

3. Every run after that reports newly-appeared matching roles, plus the expansionSignal trend (is this company's matching-role count growing?).

4. Results appear in the run's Dataset; a one-line OUTPUT_SUMMARY is in the Key-value store.

2. Finding each company's ATS token

• Greenhouse: from boards.greenhouse.io/{token} — the token is right after the domain.
• Lever: from jobs.lever.co/{token}.
• Ashby: from jobs.ashbyhq.com/{token}.
• Workable: from apply.workable.com/{token} (their account subdomain) — the same {token} used in that URL is what the actor calls internally.

If a company's careers page is on a custom domain, check its page source for one of the above URLs — most companies embed the ATS's hosted board or widget even behind a custom domain.

3. Why this exists

Generic "who's hiring" scrapers already cover the whole market at scale — not a niche this actor competes in. What a staffing agency or embedded recruiter actually needs is narrower and more urgent: the instant one of their own target/client companies opens a role in their specialization, so they can be first to pitch a candidate. See ./SPEC.md §1 for the full reasoning and pricing.

4. Local development

npm ci
npm run check   # typecheck + lint + unit tests
npm run dev     # runs against real ATS APIs using local input, if configured
npm run build   # compiles to dist/

5. License

Proprietary — see ./LICENSE. © 2026 BuildersArk LLC.