n8n-nodes-icims-careers-api

An n8n community node that pulls live job postings from any iCIMS career site, backed by the iCIMS Careers API on Apify.

iCIMS publishes no public read API for job postings, so integrating usually means writing a parser per employer. This node gives you one input and structured jobs out, and it handles both public iCIMS surfaces: the classic careers-{tenant}.icims.com portals and the modern career sites hosted on the employer's own domain. It works out which one an employer uses on its own.

Works as a regular node and as an AI Agent tool.

Installation

In your self-hosted n8n: Settings then Community Nodes then Install, and enter:

n8n-nodes-icims-careers-api

Credentials

You need an Apify API key, free to create at apify.com. In the Apify Console go to Settings then API & Integrations and copy a personal API token. Add it in n8n as an Apify API credential. OAuth2 is also supported.

Operations

Job, Get. Give it career site URLs, company names, or both, and it returns one item per job.

| Parameter | What it does | |---|---| | Career Site URLs | Portal root, sitemap, search page, single job URL, or a career site on the employer's own domain | | Company Names | Company names, resolved to their iCIMS career site for you | | Keywords | Optional title filter, applied on the career site where supported | | Changed Since | ISO date, timestamp, or a window such as 24h, 7d, 2w | | Apply the Cutoff To | Whether Changed Since matches edits too, or new postings only | | Max Jobs per Site | Per-site cap, bounds cost. 0 fetches everything | | Max Jobs Total | Overall cap across every site in the run | | Fetch Full Details | Off gives a fast, cheap list-only mode | | Description Format | Text, HTML, Markdown, or both text and HTML |

Cheap change detection

Changed Since is the parameter worth knowing. The filter is applied to the career site's own change data before any job page is opened, so polling an employer with 400 open requisitions costs you only the handful that actually moved. Pair it with Fetch Full Details off and each site costs a single request.

That makes a daily or hourly schedule genuinely affordable, which is the usual reason to reach for this node in n8n.

Output

Three modes. Simplified returns a compact object and is forced automatically when the node runs as an AI Agent tool, to save the agent's context. Raw returns every field. Selected Fields lets you pick exactly what you want.

Simplified gives you resultType, title, organization, locations, remote, employmentType, category, salary, datePosted, dateUpdated, requisitionId, description, url, applyUrl, and errorCode.

Raw adds the HTML and Markdown descriptions, coordinates, validity dates, the employer's own labelled extras, and full source metadata.

Every item carries result_type, either job or error. A dead career site, an employer that moved off iCIMS, or a network-restricted portal comes back as a labelled error item with an error_code rather than failing the run, so a scheduled workflow can branch on it.

Example workflows

Daily new-jobs alert. Schedule Trigger (every morning) then this node with Changed Since 24h, Apply the Cutoff To Posted Date Only, and Fetch Full Details off, then Filter on resultType equals job, then Slack. Costs almost nothing on a quiet day.

Employer watchlist to a database. Schedule Trigger (weekly) then this node with several Company Names and Changed Since 7d, then Postgres upsert keyed on url, which is canonical and survives an employer editing a job title.

Pricing

The Actor bills per job row delivered, so a change-detection run that finds two changed jobs costs two rows rather than a full crawl. Current pricing is on the Actor page.

Links

• Actor: iCIMS Careers API
• Python and MCP examples: Apify-iCIMS-Careers-API
• Apify n8n docs: docs.apify.com
• n8n community nodes: docs.n8n.io

License

MIT