Greenhouse, Lever & Workday Jobs Tracker

Every open job straight from company career sites on Greenhouse, Lever, Ashby, and Workday, normalized into one clean format with title, department, location, remote flag, employment type, posted date, salary when the company publishes it, and a direct link. Paste a list of careers links or board slugs, filter by keyword, location, or remote, then turn on monitor mode and schedule it to get only the roles that opened or closed since your last run, plus a hiring summary for every company.

Monitor mode

Monitor mode is the way most people use this Actor. Set onlyNewOrClosed to true and add a schedule, for example every weekday at 7 AM. The Actor remembers the open jobs it delivered for each company and your filters in a named key-value store. The first run delivers every matching job up to maxResults as new. Later runs deliver only jobs that were posted since, as new, and jobs that disappeared from the board, as closed. Jobs that are still open are skipped, and you are not charged for them.

Sample monitor input:

{
  "onlyNewOrClosed": true,
  "companies": [
    "https://job-boards.greenhouse.io/airbnb",
    "https://jobs.lever.co/spotify",
    "https://jobs.ashbyhq.com/ramp"
  ],
  "keywords": ["sales", "account executive", "revenue"],
  "maxResults": 2000
}

A few things are worth knowing before you rely on it:

• A job counts as closed when its ID is no longer on the company's board. A job that is still open but no longer matches your keywords, for example after a title change, is not reported as closed.
• History is kept per company and keyed on keywords, excludeKeywords, locations, and remoteOnly, but not on maxResults. If you change any of those filters, the Actor starts a fresh history and reports every matching job as new again. Adding a company to the list starts a history for that company only.
• Workday career sites show at most 2,000 jobs through their public search. When a Workday board lists 2,000 or more jobs, answers with fewer pages or jobs than it promised, or a board lists a job without an ID, the Actor still reports new jobs but reports no closed ones for that run, so a partial listing never looks like a wave of closures.
• A job the board still lists but that cannot be read, for example one without a title, is counted in skippedPostings and is not reported as closed. Unlisted Ashby jobs are not open to applicants, so they are left out.
• maxResults caps what a run delivers. New and closed jobs past the cap are not remembered, so they are delivered on the next run.
• The history remembers up to 10,000 jobs per company and filter that are open. When more jobs than that match, the extra ones are not reported or charged, and the log says how many, so narrow the filters for a very large board. If a company's history grows too large to save in one record, its oldest jobs keep only their title, so they are still reported when they close.
• When a Workday job is renamed, its link changes too, so it shows up once as closed and once as new. Greenhouse, Lever, and Ashby keep the same ID through a rename.
• If the saved history is ever unreadable, the run fails before charging anything rather than reporting every job as new again. The error names the record to delete from the career-site-jobs-hiring-tracker-monitor store.
• Two schedules running the same companies and filters at the same time share one history, and the run that finishes last wins.

Every run also saves a hiring summary to the HIRING_SUMMARY record of the run's key-value store, free of charge. It has one entry per company with the number of open jobs on the board, how many match your filters, how many are new and closed in monitor mode, how many records were delivered, and any error. The run's Output tab links to it.

What does it do?

Most companies post their jobs through one of a handful of applicant tracking systems, and each one publishes a public job board that anyone can read without a login. This Actor reads those public boards directly: the Greenhouse job board API, the Lever postings API (global and EU), the Ashby job board API, and the JSON search behind Workday careers sites. It turns every posting into the same record shape, so jobs from different systems sit side by side in one dataset. There is no browser, no proxy, and no login involved.

You can give each company as:

• a careers link, such as https://job-boards.greenhouse.io/airbnb, https://boards.greenhouse.io/embed/job_board?for=airbnb, https://jobs.lever.co/spotify, https://jobs.eu.lever.co/mistral, https://jobs.ashbyhq.com/ramp, or https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite,
• a slug with its system, such as greenhouse:airbnb, lever:spotify, or ashby:ramp,
• or a bare slug such as airbnb, which is looked up on Greenhouse, Lever, and Ashby. If more than one has a board by that name, the one with the most open jobs is used, so give a link when you know it.

Workday boards need the full careers link, because the tenant, the data center (wd1, wd5, and so on), and the site name all appear in it. Links to any other site are refused before the run starts.

Who is it for?

• Sales teams who sell to companies that are hiring, for example a team opening ten sales roles is buying sales tools.
• Recruiters and staffing agencies who want to hear the day a target company opens a role.
• Investors and analysts who track hiring as a growth signal, by company, department, or location.
• Job seekers who want a daily feed of new roles at the companies they care about.

How to use

1. Open the Actor in Apify Console and paste career site links, such as a Greenhouse or Lever board.
2. Optionally filter by keywords, excluded keywords, locations, or remote roles under Filters.
3. Click Start and wait for the run to finish.
4. Open the Output tab to preview jobs, then export them as JSON, CSV, Excel, or XML.
5. To see only new and closed roles, turn on monitor mode and add a schedule.

Input

Field	Type	Description
onlyNewOrClosed	true or false	Monitor mode. Outputs only jobs that opened or closed since the last run for the same companies and filters.
companies	list	Careers links or board slugs, one per line. Up to 500 companies. The same board listed twice is read once.
keywords	list	Keep only jobs whose title or department contains any of these words. Case does not matter.
excludeKeywords	list	Skip jobs whose title contains any of these words.
locations	list	Keep only jobs whose location contains any of these, for example New York or Remote.
remoteOnly	true or false	Keep only jobs marked remote by the board or whose location says remote.
maxResults	number	Most job records to deliver in one run. Default 1000, maximum 100,000.

Each company is read whole before anything is delivered, so filters never miss a job on a later page. If one company's board is missing or down, the run carries on with the rest and notes the error in the hiring summary. The run fails only when no company could be read.

Sample input:

{
  "companies": ["airbnb", "lever:spotify", "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"],
  "keywords": ["engineer"],
  "excludeKeywords": ["intern"],
  "locations": ["United States", "Remote"],
  "remoteOnly": false,
  "maxResults": 500
}

Output

Each job is one dataset item. This is a real record:

{
  "jobId": "8306554",
  "changeType": "new",
  "company": "Airbnb",
  "title": "AirCover Specialist, Claims Experience",
  "department": "Community Support",
  "location": "Canada",
  "remote": true,
  "workplaceType": "remote",
  "employmentType": null,
  "postedAt": "2026-10-28T14:52:05Z",
  "updatedAt": "2026-10-28T14:52:05Z",
  "salaryText": "$58,000 - $68,000 CAD",
  "salaryMin": 58000.0,
  "salaryMax": 68000.0,
  "salaryCurrency": "CAD",
  "salaryInterval": null,
  "url": "https://careers.airbnb.com/positions/8306554?gh_jid=8306554",
  "ats": "greenhouse",
  "companyKey": "greenhouse:airbnb",
  "boardUrl": "https://job-boards.greenhouse.io/airbnb",
  "detectedAt": "2026-11-01T18:00:00Z"
}

You can download results as JSON, CSV, Excel, or XML, or read them through the Apify API.

• jobId is the board's own ID, stable across runs. Together with companyKey it identifies a job.
• changeType is new or closed in monitor mode and notTracked otherwise. A closed job keeps the details it had when it was last seen open.
• Text copied from a job board that starts with =, +, -, or @ gets a leading apostrophe, so a spreadsheet opening the CSV export shows it as text instead of running it as a formula.
• remote is true when the board marks the job remote or its location says remote. workplaceType is remote, hybrid, or onsite when the board says, which Lever and Ashby usually do and Greenhouse sometimes does.
• salaryText, salaryMin, salaryMax, and salaryCurrency come from Lever's salary range, Ashby's compensation, or the pay range block in the Greenhouse posting. Workday's public search does not include pay, and many companies do not publish it at all, so these are often null.
• postedAt is a full UTC time for Greenhouse, Lever, and Ashby. Workday only says "Posted 3 Days Ago", so its postedAt is the day that works out to, and null for "30+ Days Ago".
• company is the company name Greenhouse gives, or the board slug for the other systems.

Pricing

This Actor uses pay-per-event pricing.

• Job record: $5.00 per 1,000 jobs delivered to your dataset ($0.005 each).
• Actor start: Apify's standard start event ($0.00005).
• The hiring summary is free, and there is no separate charge per dataset item.

A full snapshot of a company with 200 open jobs costs $1. A daily monitor of 50 companies usually delivers only the roles that opened or closed that day, typically a few to a few dozen per company per week, so a few dollars a month. Keyword and location filters cut the cost further, because only matching jobs are delivered. You can cap any run with Apify's maximum charge setting. The Actor stops cleanly at your limit, and you are only charged for jobs that actually reach your dataset.

Estimated compute cost

Default memory is 512 MB, and the Actor uses under 100 MB of it. Measured on Apify: a snapshot of Airbnb (Greenhouse), Spotify (Lever), and Ramp (Ashby), 463 jobs in all, ran in 5 seconds for about $0.003 of platform usage. A monitor run over those three plus Workday's own careers site (373 open jobs, read 20 a page with a short pause between pages) took 49 seconds and about $0.0015 of platform usage, less than the snapshot because it wrote fewer records. A Workday board at the 2,000-job cap takes one to two minutes on its own. So compute stays well under a cent per run, and the job records are almost all of the cost. If you track many large Workday boards in one run, raise the run timeout above the default hour. If a run times out, resurrect it and it continues after the last company it finished, without charging a job twice.

Data sources and freshness

• Greenhouse job board API: boards-api.greenhouse.io.
• Lever postings API: api.lever.co and api.eu.lever.co.
• Ashby job board API: api.ashbyhq.com.
• Workday careers sites: the public job search JSON that every myworkdayjobs.com careers page itself uses.

Every job is read live from the company's own board at run time, so the data is as fresh as the board. Requests to each site are paced and retried with backoff when a site is busy. If the platform moves a run to another server, it resumes after the last company it finished and never delivers or charges a job twice.

Is it legal to use this data?

The Actor reads job postings that companies publish on public job boards for anyone to view, through the same public endpoints their careers pages use, without logging in. Job postings are business information, not personal data. The data is provided as is, without any guarantee that it is complete, current, or accurate, and a closed job may simply have been moved or renamed. This Actor is an independent tool and is not affiliated with or endorsed by Greenhouse, Lever, Ashby, Workday, or any company whose jobs it reads. You are responsible for how you use the results and for following each site's terms that apply to you.

API and integrations

You can start this Actor and read its results with the Apify API, the Apify Python and JavaScript clients, or the Apify CLI. The API returns each run's dataset in the same formats as the Console.

Apify integrations can pass results on when a run finishes, for example to Google Sheets, Slack, Zapier, Make, or your own webhook. Set them up on the Actor's Integrations tab, and pair them with a schedule for a hands-off feed.

FAQ

Do I need an account or API key for any of these job boards? No. Every source is public and needs no login.

How do I find a company's board? Open the company's careers page and click any job. The link usually contains greenhouse.io, lever.co, ashbyhq.com, or myworkdayjobs.com. Paste the board part of that link.

Why does a bare slug pick the wrong company? Two companies can use the same slug on different systems. Give the full careers link or a prefix such as ashby:ramp to pick the right one.

Why are there no closed jobs for a Workday company? Its board lists 2,000 jobs or more, and Workday's public search stops at 2,000, so the Actor cannot tell a closed job from one it could not see. Use keywords to narrow the board, or track that company's new jobs only.

Why does a company show the status duplicate in the hiring summary? The same board appeared twice in your list, for example once as a bare slug and once as a link. The Actor reads each board once per run, so the second entry delivers nothing.

Can it read iCIMS, SmartRecruiters, or LinkedIn? Not yet. This Actor covers Greenhouse, Lever, Ashby, and Workday.

Related Actors

• Website Contact Enrichment (Emails, Phones): emails, phone numbers, and social links from company websites.
• AI Brand Visibility: ChatGPT, Perplexity, Gemini: how ChatGPT, Perplexity, Gemini, and Claude mention your brand.
• News & Brand Mention Monitor (Google News + RSS): news mentions of your brand in Google News and RSS feeds.

Feedback and custom requests

Found a bug, a wrong value, or a source that changed? Open an issue in the Issues tab on this Actor's page. Need another field, filter, or source, or a version built for your team? Describe it in the Issues tab as a custom request.