apify-icims-job-monitorlisted

Track new iCIMS job postings without re-crawling a career site every day, using the Apify iCIMS Careers API Actor (johnvc/icims-careers-api) in change-detection mode. Set newerThan to a window like 24h or 7d and the Actor filters on the career site's own change data before it opens a single job page, so an employer with four hundred open requisitions costs you only the handful that actually moved. Add includeDetails false and each site costs one page fetch, which makes a daily poll of a large watchlist genuinely affordable. Rows carry url, requisition id, title, date posted and date updated, so diffing two runs tells you what opened, what was edited, and what closed. Use when the user wants job posting alerts, hiring signal, an ats api feed on a schedule, competitor headcount tracking, or a jobs change feed piped into Slack or a database. Pay per row returned, MCP-ready for Claude and other AI agents.
johnisanerd/claude-skill-icims-job-monitor · ★ 0 · DevOps & Infrastructure · score 66

Install: claude install-skill johnisanerd/claude-skill-icims-job-monitor

# iCIMS Job Change Feed, Not a Nightly Re-Crawl Poll a watchlist of employers daily and pay only for the requisitions that moved. ## When to use this skill - The user wants to know when an employer posts something new, not what they have posted overall. - They are building hiring signal, competitor tracking, or a jobs alert product. - They already pulled a full snapshot and now need to keep it current. - They want a scheduled feed into Slack, a database, or a spreadsheet. Not for: the first full pull of an employer's jobs. Do that once with the companion apify-icims-jobs-api skill, then switch to this. See `references/actor-index.md`. ## Why this is cheap and a re-crawl is not The classic iCIMS portal publishes its own change data for every live requisition. With `newerThan` set, the Actor applies the window to that data **before** it fetches any job page, so unchanged jobs are never opened. A naive scraper pays for all four hundred pages every night; this pays for the three that changed. On the modern career-site surface the same filter is applied to the site's own update field. `includeDetails: false` takes it further: no job pages at all, just the list. One fetch per site. ## What you get In list-only mode, one lean row per changed job: - `url` (canonical and stable, the dedupe key), `id` (the employer's requisition number), `title` - `date_posted`, `date_updated` - `tenant`, `source_surface`, `source_domain`, `scraped_at` The Actor's dataset also ships a **chan