Repository navigation
Showcase: ATS Zero-Browser Gateway — protocol-level scraper & MCP server on Apify #4277
ginugokz
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hey everyone! 👋
I wanted to share a project I recently published on the Apify Store that tackles one of the most frustrating parts of modern web scraping: heavy applicant tracking systems (especially Workday, Greenhouse, Lever and Ashby).
Traditionally, extracting jobs from Workday requires running headless Puppeteer/Playwright instances that consume 800MB–1.2GB of RAM, take 45–60 seconds to hydrate, and frequently break on frontend class obfuscations.
How it works:
Instead of launching a browser, ATS Zero-Browser Gateway maps and targets the underlying internal backend JSON/CXS endpoints directly (e.g.
/wday/cxs/{org}/{portal}/jobs).Performance: Extracts 40+ jobs with full descriptions, compensation, and HTML in 8.9 seconds at ~43MB of RAM (vs 45-60s on headless browsers).
Dual-Hash Delta Tracking: Generates deterministic hashes to identify exactly which postings are
ADDED,REMOVED, orUPDATED.MCP Server Native: Fully compatible with the Model Context Protocol (MCP) so AI coding agents (Claude Code, Cursor, Windsurf) can query company careers directly.
n8n Template: Includes a ready-to-import JSON workflow for scheduled pipeline monitoring.
📦 Apify Actor: https://apify.com/ginugokz/ats-zero-browser-gateway
💻 Open-Source GitHub: https://github.com/ginugokz/ats-zero-browser-gateway
Would love any feedback or thoughts from fellow Crawlee & Apify creators!
Edited 17 Oct 2026: SmartRecruiters support was removed because its robots.txt disallows automated access. Supported: Workday, Greenhouse, Lever and Ashby.
All reactions