Greenhouse Hiring Signals

Monitor public Greenhouse job boards and receive one compact report for each successful board check. Reports include the current matched openings, department and location counts, newly observed jobs, selected field changes, and jobs that have been absent from two consecutive complete captures.

Input

Enter the token from a public Greenhouse board URL. For example, webflow is the token in boards.greenhouse.io/webflow.

{
  "boards": ["webflow"],
  "monitorId": "store-smoke",
  "titleKeywords": ["engineer", "data"],
  "locationKeywords": ["remote", "new york"],
  "maxJobsPerBoard": 500
}

Title and location filters are optional. Within each filter, a job matches any keyword; when both filters are present, it must match both groups. Matching is case-insensitive. Keep the same monitorId, board list, filters, and limit across scheduled runs so the actor can compare like with like.

Output

Every completed board check produces one dataset item with:

• status: baseline on the first observation, then checked
• total_open and matched_open
• department_counts and location_counts
• jobs: current matched public job summaries
• changes: deterministic newly_observed, changed, and no_longer_listed events
• change_counts: counts by event type

Store runs are bounded to three minutes, including all configured boards. Use at most ten boards per monitor and raise maxJobsPerBoard only when the source reports that the current safety cap is too low.

The first run establishes a baseline and emits no changes. A missing job is described only as no_longer_listed, after it is absent from two complete captures; that does not claim the role was filled. Failed, malformed, redirected, oversized, or capped source responses do not advance the saved baseline and do not produce a charged board report.

Data and source limits

The actor reads Greenhouse's public board API over HTTPS. It stores job IDs, titles, public locations, departments, canonical job links, and public update timestamps. It does not collect applicants, infer salaries, call LinkedIn, use an LLM, or publish full job descriptions or recruiter contact details.

Pricing is $0.02 per successfully delivered board report, including baseline and unchanged reports. Failed checks are uncharged. Configure a maximum run charge in Apify when you want a hard spending limit.

Scheduled monitoring and state

Keep the same monitor ID and filters when scheduling the Actor in Apify. State is held in actor-created named storage within your own Apify account. Overlapping runs of the same monitor are refused without source reads or charges. The first capture creates a baseline; later captures compare selected fields. Storage removal or account retention may reset the baseline. A resumed run does not recharge a report already visible in its dataset; an uncertain interrupted charge may be waived. Reports are observation evidence, not a claim that a missing role was filled.

Source: https://docs.greenhouse.io/job-board.html