JDX & iCIMS Integration

iCIMS

Send approved job postings from JDX into iCIMS, so what candidates read is the job your organization actually approved.

iCIMS_Integration

Approved postings only

Job content reaches iCIMS after it clears your workflow, so what a candidate reads traces back to an approved record with a history.

Qualifications, consolidated

Education, experience, skills, and licenses combine into a single qualifications field.

Mapped to your instance

Any field in your JDX template can flow, provided iCIMS has somewhere to receive it. iCIMS confirms the header names.

What this integration does

JDX is the system of entry for job information. iCIMS stays your applicant tracking system and owns everything from the application forward.

  • Match on job code, usually carried through as the external identifier
  • Route to the right template, with an active or inactive designation that usually controls which iCIMS job template the posting lands against
  • Send posting content only: nothing flows from iCIMS back into JDX
  • Stand it up in about eight weeks, plus lead time to secure an iCIMS consultant

Integration details

 

Built by: JDXpert


Category: ATS


Connection type: Scheduled file transfer over secure SFTP


Direction: Outbound only, JDX to iCIMS


Typical setup: ~8 weeks, not counting any consultant lead time

Not seeing what you need?

Request a technical review and we'll walk your iCIMS administrator or consultant through the mapping, the header names, and the template placement for your instance.