Company Jobs Monitor: Greenhouse, Lever, Workday, Ashby & More
Pricing
$1.50 / 1,000 job rows
Get only the jobs a company posted since your last run. Reads the public job feeds of Greenhouse, Lever, Ashby, Workable, Recruitee, Workday, Phenom and Eightfold; SmartRecruiters is closed by its host's robots.txt (measured 2026-09-07). Pay per job row; status rows and quiet days are free.
Company slugs (e.g. stripe, spotify) or careers-page URLs. A bare slug is looked up across Greenhouse, Lever, Ashby, SmartRecruiters, Workable and Recruitee (every host's robots.txt is read and obeyed first; api.smartrecruiters.com currently disallows this actor, measured 2026-09-07, so a SmartRecruiters board returns the free not-found row naming that rule, with no request made, until the host permits it). Workday must be given as a URL (e.g. https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite), because a Workday board is keyed by a tenant AND an arbitrary site id that cannot be guessed from a company name — open the company's careers page and paste the address. Any *.wdN.myworkdayjobs.com link works, including a link to a single job. Phenom and Eightfold sites live on the employer's own domain (careers.lilly.com/us/en/…, jobs.cvshealth.com, careers.micron.com/careers, <company>.eightfold.ai/careers): paste any page of the careers site and the host is asked which of the two it is — its robots.txt is read first (once per host per run) and a feed path it disallows is not requested, then one request to each permitted feed; a host on neither gets a free not-found row naming both answers, and a host whose robots.txt refuses or cannot be read gets the same row with that reason in RUN_SUMMARY. To skip the question, or when a probe misses, name the platform: phenom:careers.lilly.com/us/en or eightfold:careers.micron.com/micron.com (host, then the tenant domain — derived from the host when omitted: careers.micron.com → micron.com, vodafone.eightfold.ai → vodafone.com).
When on, the first run returns all current jobs and every later run returns only the jobs that appeared since — which is what makes this cheap to schedule. Two things are remembered: what was delivered to you, and what your own title filters excluded. Anything held back for any other reason — the per-company cap, the run's charge limit — is NOT remembered and arrives on a later run. State is stored per company list in a key-value store named career-jobs-monitor-state on your account; change the company list and monitoring starts fresh for the new list. A company with nothing new gets a free no-new-jobs row, so a quiet day never looks like a broken run.
Adds the description text to each row (bigger output). For Workday boards it also fills in the resolved location, the employment type and the exact posting date — but it costs one extra request per posting, so a several-thousand-job Workday board takes minutes rather than seconds. On Phenom and Eightfold the description is one extra request per posting made ONE A SECOND on the employer's host (Phenom's also fills updated_at); descriptions that do not fit the per-board time budget are counted in a free partial row, never left blank silently — use maxJobsPerCompany or raise boardTimeBudgetMinutes for a large board.
Keep only jobs whose title contains ANY of these words (case-insensitive). Example: engineer, junior, intern. Empty keeps everything. Filtering happens before you are charged. In monitor mode a job your filters excluded counts as handled and is remembered, so widening this list applies to jobs posted from then on.
[]Drop jobs whose title contains ANY of these words (case-insensitive). Example: senior, staff, director. In monitor mode a job your filters excluded counts as handled and is remembered, so removing a word here applies to jobs posted from then on.
[]Rather than leaving a company silently out of the results, add a row saying what happened. Every status this actor can emit: not-found (no supported job board answered for that name, a URL on a platform we don't cover, a board whose feed could not be reached on this run, or an employer host whose own robots.txt disallows the feed path or could not be read, so the feed was not asked — the exact reason is in RUN_SUMMARY), no-open-jobs (the board you named was reached and lists nothing open), filtered-out (the board has jobs but none matched your title filters — the note says how many were on it), no-new-jobs (monitor mode: the board was reached and nothing on it is new since your last run), charge-limit-reached (this run's maximum charge limit ran out, or billing itself failed — jobs held back by the limit were not delivered; if billing itself failed, the rows already written are un-marked instead. Either way they are not marked as seen and arrive next run), results-truncated (paging stopped short of the whole board — the note says whether the SOURCE refused the rest or this actor's own sourceSafetyGuard or boardTimeBudgetMinutes stopped the run, with the numbers behind the claim) and partial (a request to the source failed twice, or — with descriptions on for a Phenom or Eightfold board — the per-board time budget ran out before every description was fetched, so that company's rows are an incomplete picture of its board; the note says how many). These rows are FREE — they are never charged. Turn off for job rows only.
This actor's own runaway protection, not a limit any job board imposes. 0 = the built-in 50,000 postings per board, which sits well above the largest board ever measured (starbucks.eightfold.ai, 22,985) and has never been reached on a live board — it exists only so a paging loop against a third-party feed cannot run away. If the guard is ever reached, the run emits a free results-truncated row saying THIS ACTOR stopped it and naming this input, and the count is exact. Greenhouse, Ashby, Workable and Recruitee serve a whole board in one response and ignore this.
This actor's own limit on how long one company's board may take to read, not a limit any job board imposes. 0 = the built-in 20 minutes. It exists for the one feed shape that is slow by construction: Eightfold serves 10 postings per request and rate-limits anything faster than about one request a second, so its 22,985-posting Starbucks board would take ~38 minutes — longer than a run with several companies can spend on one of them, and a run that times out delivers nothing and explains nothing. When the budget runs out the rows read so far are delivered, a free results-truncated row says THIS ACTOR stopped the read and states the board's own size, and RUN_SUMMARY carries truncation_reason: our-guard with guard: time. Raise it together with the run timeout to read a huge Eightfold board whole, or use maxJobsPerCompany. The same budget covers per-posting description requests on Phenom and Eightfold. Every other platform measured reads its largest board in well under a minute.
0 = no limit. Caps the rows you are delivered and charged for per company — a single large Workday, Phenom or Eightfold board can run to several thousand postings (CVS on Phenom: 19,036; Starbucks on Eightfold: 22,985). On Eightfold it also shortens the read, which is the cheap way to watch a huge board. In monitor mode it caps how many NEW jobs arrive per run; anything over the cap is not marked as seen, so it comes on the next run instead of being lost. The cap never changes the reported board size: RUN_SUMMARY states the board's own total as jobs_found (never the cap) and what the fetch handed the run as jobs_fetched.