# ATS Jobs Monitor - Greenhouse, Lever, Ashby & More (`prevailing_glow/ats-jobs-monitor`) Actor Open jobs from Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee & Personio boards. Auto-detects the ATS, salary, filters, alerts on new jobs. - **URL**: https://apify.com/prevailing\_glow/ats-jobs-monitor.md - **Developed by:** [Dave West](https://apify.com/prevailing_glow) (community) - **Categories:** Jobs, Automation, Lead generation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 1 bookmarks - **User rating**: No ratings yet ## Pricing from $1.00 / 1,000 job results 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 ## ATS Jobs Monitor: open jobs from Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee and Personio Get **every open job of any company** straight from its official applicant tracking system (ATS) job board, as clean, flat data: title, department, team, location, remote flag, employment type, **salary where published**, posting date, apply link and the full description. Give it company names, domains, careers-page URLs or `ats:slug` pairs and it **finds the right job board automatically**. Turn on **monitor mode** and schedule it to get **job alerts**: each run outputs only the jobs that are **new, changed or removed** since the last run. - ✅ 7 ATS platforms: **Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee, Personio** - ✅ **Auto-detection**: `Hugging Face`, `figma.com` or `https://jobs.lever.co/acme` all work - ✅ Uses the companies' **public job-board feeds**: no login, no proxies, no browser, fast and reliable - ✅ **Salary** (min / max / currency / interval) where the board publishes it, plus salary ranges found in the description - ✅ Filters: keywords, location, department, remote only - ✅ **Change monitoring**: new, changed and removed jobs since the previous run - ✅ Per-company **summary and HTML report**: detected ATS, open roles, roles by department, change vs. last run - ✅ Privacy-friendly: **e-mail addresses and phone numbers are removed** from descriptions - ✅ Pay only for results: companies that aren't found are **free** ### Use cases - **Job aggregation and job boards**: build a niche job board (remote, AI, fintech, Dutch startups...) from hundreds of company career pages and keep it fresh with daily monitor runs. - **Hiring signals for sales (B2B lead generation)**: a company hiring 5 data engineers or its first RevOps manager is a buying signal. Track target accounts and get alerted when they open roles in your buyer's department. - **Recruitment and talent sourcing**: see which companies hire for the roles you place, the moment new jobs go live, with salary ranges where published. - **Market research and competitive intelligence**: headcount growth by department, new locations and offices, remote vs. on-site mix, salary bands per role. - **Job seekers and communities**: watch a shortlist of dream companies and get only the new roles. - **Investors and analysts**: hiring velocity as a growth indicator across a portfolio or a market. ### Supported ATS platforms | ATS | Detected from | Salary | Notes | |---|---|---|---| | Greenhouse | name, domain, `boards.greenhouse.io/…`, `job-boards.greenhouse.io/…` | structured pay ranges where published | | | Lever | name, domain, `jobs.lever.co/…` (EU boards too) | structured salary range + text | | | Ashby | name, domain, `jobs.ashbyhq.com/…` | structured compensation + summary | | | Workable | name, domain, `apply.workable.com/…` | – (from description) | | | SmartRecruiters | name, domain, `jobs.smartrecruiters.com/…` | – (from description) | descriptions need one request per job | | Recruitee | name, domain, `{company}.recruitee.com` | structured where published | | | Personio | name, domain, `{company}.jobs.personio.de` | – (from description) | XML feed | If a company's board isn't found automatically (for example the slug differs from the name), give it explicitly: `greenhouse:stripe`, `lever:spotify`, `ashby:notion`, `workable:huggingface`, `smartrecruiters:BoschGroup`, `recruitee:bunq`, `personio:acme`, or paste the job-board URL. ### Quick start 1. Add companies, one per line: `stripe`, `figma.com`, `Hugging Face`, `https://jobs.ashbyhq.com/notion`, `smartrecruiters:BoschGroup`. 2. Optionally filter: keywords `engineer, data`, locations `Amsterdam, remote`, department `Engineering`. 3. Click **Start**. Jobs appear in the dataset; the **HTML report** and **SUMMARY** show one line per company. 4. For job alerts: turn on **Monitor mode** and add a **schedule** (e.g. daily). Connect Slack, e-mail, Google Sheets or a webhook through Apify integrations. Run it with no companies to get a free preview with a few example companies. ### Input example ```json { "companies": ["stripe", "figma.com", "Hugging Face", "ramp", "bunq", "smartrecruiters:BoschGroup"], "keywords": "engineer, data", "locations": "Amsterdam, London, remote", "remoteOnly": false, "includeDescription": true, "monitorMode": true, "maxJobsPerCompany": 500 } ``` | Field | Default | What it does | |---|---|---| | `companies` | – | Names, domains, careers/job-board URLs or `ats:slug`. Empty = free preview | | `keywords` / `locations` / `departments` | – | Comma-separated; any term matches (OR), different filters combine (AND). Short terms (≤3 letters, e.g. `go`, `US`) match whole words | | `remoteOnly` | `false` | Only jobs the board marks as remote | | `atsFilter` | all | Only try these ATS during detection | | `includeDescription` | `true` | Description as HTML and plain text | | `monitorMode` | `false` | Output only new, changed and removed jobs since the last run | | `monitorStoreName` | `ats-jobs-monitor-state` | Named key-value store holding the monitor state | | `maxJobsPerCompany` | `500` | Max rows per company (newest first) | | `outputNotFoundRows` | `true` | Free `company-not-found` row for companies without a detectable board | | `maxConcurrency` | `5` | Companies processed in parallel | | `useDetectionCache` | `true` | Remember each company's ATS for 30 days | ### Output One flat row per job (dataset), real example: ```json { "rowType": "job", "company": "ramp", "companyName": null, "ats": "ashby", "boardSlug": "ramp", "jobId": "0d731586-3626-48fb-9dc5-3061ae5fd240", "title": "Customer Experience Associate - London", "department": "Customer Experience", "team": "CX Frontline", "location": "London", "locations": ["London"], "country": "United Kingdom", "remote": false, "workplaceType": "Hybrid", "employmentType": "Full-time", "salaryMin": 39000, "salaryMax": 43000, "salaryCurrency": "GBP", "salaryInterval": "year", "salaryText": "£39K – £43K • Offers Equity", "salarySource": "structured", "postedAt": "2026-10-01T18:38:56.489Z", "updatedAt": null, "applyUrl": "https://jobs.ashbyhq.com/ramp/0d731586-3626-48fb-9dc5-3061ae5fd240/application", "jobUrl": "https://jobs.ashbyhq.com/ramp/0d731586-3626-48fb-9dc5-3061ae5fd240", "descriptionHtml": "

About Ramp

Ramp is building…", "descriptionText": "About Ramp\nRamp is building the smart infrastructure for finance teams…", "changeType": null, "changedFields": null, "scrapedAt": "2026-10-01T18:51:13.412Z" } ``` - `salarySource`: `structured` (min/max from the ATS), `text` (salary text from the ATS), `description` (a salary range found in the description) or `null`. - `changeType` (monitor mode): `baseline` (first run), `new`, `changed` (with `changedFields`, e.g. `["title","salaryMin"]`) or `removed` (job no longer on the board; basic fields from the last run). - Companies whose board can't be found get a `rowType: "company-not-found"` row with what was tried (free; turn off with `outputNotFoundRows`). **SUMMARY** (key-value store, JSON) and **OUTPUT.html** (report): per company the detected ATS and board URL, open roles on the board, matching roles, rows output, remote roles, rows with salary, roles by department and new / changed / removed counts versus the last run, plus totals per ATS. Real run (10 inputs, 1 October 2026): Stripe (Greenhouse, 714 open roles), Figma (Greenhouse, 165), Notion (Ashby, 134), Ramp (Ashby, 158), Spotify (Lever, 79), bunq (Recruitee, 14), Hugging Face (Workable, 8), Personio (Personio, 1) and Bosch (SmartRecruiters, 4,815) were all detected automatically; one made-up company got a free "not found" row. ### Monitor mode (job alerts) The first run stores every matching job and outputs them once as `baseline`. Later runs with the same companies and filters output only: - **new** jobs (posted since the last run), - **changed** jobs (title, department, team, locations, remote, workplace type, employment type or salary changed), - **removed** jobs (closed or unpublished). State is kept per company and filter set in a named key-value store, so adding a company to the list does not reset the others. Descriptions are not compared (boards re-render them often). If two schedules monitor the same company with the same filters, give each its own `monitorStoreName`. ### Pricing Pay per event, no subscription: | Event | Price | When | |---|---|---| | Company checked | $0.002 | once per company whose job board was found and read (also when no job matches your filters) | | Job result | $0.001 | per job row in the dataset (including `removed` rows in monitor mode) | Companies that aren't found or can't be read are **not charged**, and the free preview (empty input) is not charged. Examples: 50 companies with 40 matching jobs each = 50 × $0.002 + 2,000 × $0.001 = **$2.10**. A daily monitor of 100 companies with ~30 changes per day = $0.20 + $0.03 = **$0.23/day**. Set a maximum cost per run and the Actor stops cleanly when it is reached. ### FAQ **Is this allowed?** It reads the public job-board feeds that companies publish through their ATS so their jobs can be shown on their own careers pages and job sites. No login, no personal data: e-mail addresses and phone numbers are removed from descriptions. **A company wasn't found. What now?** Auto-detection tries slugs derived from the name or domain (e.g. `huggingface`, `hugging-face`). If a company uses a different slug or another ATS, paste its job-board URL or use `ats:slug`. Companies on other systems (e.g. in-house careers sites) are reported as not found and not charged. **Why are SmartRecruiters runs slower?** Its feed lists jobs without descriptions, so each description is a separate request. Turn off `includeDescription` for big boards if you only need titles and locations. **Does it use proxies or a browser?** No. Only official JSON/XML job-board endpoints, a few polite requests per company. **How fresh is the data?** Live at run time. Schedule hourly or daily runs with monitor mode for alerts. **Can I get the data in Google Sheets, Slack or my CRM?** Yes, through Apify integrations, webhooks or the API (JSON, CSV, Excel). **Can a company be matched to the wrong board?** Boards that report a different company name, or have no jobs, are only used as a fallback and flagged `lowConfidence` in the summary. Use `ats:slug` to be certain. ### Support Found a board that isn't detected or a field that looks wrong? Open an issue on the Actor's Issues tab with the company and the expected job-board URL. # Actor input Schema ## `companies` (type: `array`): One company per line: a name (Hugging Face), a domain (figma.com), a careers or job-board URL (https://jobs.lever.co/acme), or an explicit board as ats:slug (greenhouse:stripe, smartrecruiters:BoschGroup). Names and domains are matched to their job board automatically. Leave empty to see a free preview with example companies. ## `keywords` (type: `string`): Only jobs whose title, department or team contains one of these comma-separated words, e.g. engineer, data, product manager. Leave empty for all jobs. ## `locations` (type: `string`): Only jobs in one of these comma-separated locations (city, country or 'remote'), e.g. Amsterdam, Berlin, remote. ## `departments` (type: `string`): Only jobs in one of these comma-separated departments or teams, e.g. Engineering, Sales. ## `remoteOnly` (type: `boolean`): Only jobs the board marks as remote. ## `atsFilter` (type: `array`): Limit auto-detection to these applicant tracking systems. Leave empty to try all. ## `monitorMode` (type: `boolean`): Compare with the previous run of the same companies and filters and output only jobs that are new, changed (title, location, department, salary...) or removed since then. The first run outputs every job once as the baseline. Schedule the Actor (e.g. daily) to get job alerts. ## `monitorStoreName` (type: `string`): Named key-value store that keeps the jobs seen in previous runs. Use a different name per schedule if two schedules monitor the same company with the same filters. ## `includeDescription` (type: `boolean`): Add the description as HTML and plain text (e-mail addresses and phone numbers are removed). Turn off for smaller, faster results. ## `maxJobsPerCompany` (type: `integer`): Maximum job rows per company (newest first). In monitor mode this caps the changes output per company. ## `outputNotFoundRows` (type: `boolean`): Adds a free company-not-found row to the dataset for each company whose job board could not be found, so you can fix the input. Turn off for a dataset with job rows only. ## `maxConcurrency` (type: `integer`): How many companies are checked at the same time. ## `useDetectionCache` (type: `boolean`): Cache which ATS and slug each company uses (30 days) so later runs skip detection. ## Actor input object example ```json { "companies": [ "stripe", "notion", "bunq" ], "remoteOnly": false, "monitorMode": false, "monitorStoreName": "ats-jobs-monitor-state", "includeDescription": true, "maxJobsPerCompany": 10, "outputNotFoundRows": true, "maxConcurrency": 5, "useDetectionCache": true } ``` # Actor output Schema ## `jobs` (type: `string`): One row per job: company, ATS, title, department, location, remote, salary, dates and links. ## `allFields` (type: `string`): Full rows including descriptions (HTML and text) and change flags. ## `report` (type: `string`): Per company: detected ATS, open roles, roles by department and changes since the last run. ## `summary` (type: `string`): Per-company summary: ATS, board URL, open and matching roles, roles by department, changes, not-found companies. # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "companies": [ "stripe", "notion", "bunq" ], "maxJobsPerCompany": 10 }; // Run the Actor and wait for it to finish const run = await client.actor("prevailing_glow/ats-jobs-monitor").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "companies": [ "stripe", "notion", "bunq", ], "maxJobsPerCompany": 10, } # Run the Actor and wait for it to finish run = client.actor("prevailing_glow/ats-jobs-monitor").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 '{ "companies": [ "stripe", "notion", "bunq" ], "maxJobsPerCompany": 10 }' | apify call prevailing_glow/ats-jobs-monitor --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,prevailing_glow/ats-jobs-monitor" } } } ``` 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 ` 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/tBHCdH9bu35yQKllS/builds/dKX8yHEooHkoftmET/openapi.json