iCIMS ATS Integration

iCIMS connector for Kombo’s ATS API

The iCIMS ATS integration allows you to sync ATS data between iCIMS and your application through Kombo’s unified API. The tool slug for this connector is icims.

​

Guides and Resources

Connection Setup Guide

Step-by-step instructions to connect your iCIMS account to Kombo.

​

Supported Features & Coverage

Models

Users

Field	Notes
id
remote_id
changed_at
remote_deleted_at
first_name
last_name
email

Jobs

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
job_code
description
employment_type
status	The status comes from the iCIMS job folder, as configured in the “Map job folders to job statuses” setting. If “Sync posted jobs as open” is enabled there, jobs with a currently posted posting sync as OPEN, even when their folder is mapped to another status. Jobs in additional job folders otherwise have no status. Only synced folders are affected.

If that setting is disabled, only jobs in approved folders and in additional job folders are synced. Jobs in an approved folder sync as OPEN while one of their postings is posted (or always, with “Treat all approved jobs as OPEN”), and all other synced jobs sync as CLOSED. | | visibility | | | category | | | department | | | post_url | | | remote_work_status | We infer the remote work status from the job location if it includes “remote” or “hybrid” | | salary_amount_from | | | salary_amount_to | | | salary_currency | | | salary_period | | | location | | | custom_fields | | | integration_fields | | | remote_url | The direct link only resolves when “Direct Links” are enabled in the customer’s iCIMS Platform | | opened_at | | | closed_at | | | remote_created_at | | | remote_updated_at | |

Job postings

Field	Notes
id
remote_id
changed_at
remote_deleted_at
status
url
job_id

Candidates

Field	Notes
id
remote_id
changed_at
remote_deleted_at
first_name
last_name
company
title
source
phone_numbers
email_addresses
social_media
location
custom_fields
integration_fields
remote_url	The direct link only resolves when “Direct Links” are enabled in the customer’s iCIMS Platform
remote_created_at

Application Stages

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
status
custom_fields
integration_fields

Applications

Field	Notes
id
remote_id
changed_at
remote_deleted_at
outcome	Outcome is only available if the application is using a default application stage, custom stages do not have an outcome
current_stage_id
job_id
candidate_id
screening_question_answers
custom_fields
integration_fields
remote_created_at

Screening questions

Field	Notes
id
remote_id
changed_at
remote_deleted_at
title
description
format

Roles

Field	Notes
id
remote_id
changed_at
remote_deleted_at
remote_label
scope
unified_type

Job-specific screening questions

Field	Notes
index
required
precondition_question_id
precondition_options
job_id
question_id
id
changed_at
remote_deleted_at

Job user role assignments

iCIMS exposes 3 standard job roles:

• hiringmanager maps to unified type HIRING_MANAGER
• recruiter maps to unified type RECRUITER
• secondaryrecruiter maps to unified type RECRUITER with the label “Secondary Recruiter”

Additional hiring team members can be surfaced via the hiring_team_role_field_mappings setting. People referenced by those custom job fields sync with the mapping’s configured label and no unified type.

Field	Notes
job_user_id
role_id
id
changed_at
remote_deleted_at

Job hiring team members

Field	Notes
roles
job_id
user_id
id
changed_at
remote_deleted_at

Actions

Create candidate

Input Field	Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.phone_number
candidate.gender
candidate.social_links.url
application.job_id
application.stage_id
attachments.name
attachments.content_type
attachments.data_url
attachments.data
attachments.type
source.name
source.unified_key
source.id

Create application

Input Field	Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.phone_number
candidate.gender
candidate.social_links.url
application.job_id
application.stage_id
attachments.name
attachments.content_type
attachments.data_url
attachments.data
attachments.type
source.name
source.unified_key
source.id

Add attachment to application

Only attachment of the type CV is supported by iCIMS. This action will fall back to the “Add attachment to candidate” action. Therefore, there could be cases where the attachment may not be added to the application but rather to the candidate.

Input Field	Notes
application_id
attachment.name
attachment.content_type
attachment.data_url
attachment.data
attachment.type

Move application to stage

Input Field	Notes
application_id
stage_id

Add result link to application

Input Field	Notes
application_id
label
url
details.custom_field_name_prefix
details.attributes.key
details.attributes.value

Get candidate attachments

Only CVs are supported by iCIMS. Other attachments can’t be retrieved.

Input Field	Notes
candidate_id

Add attachment to candidate

Only attachment of the type CV is supported by iCIMS.

Input Field	Notes
candidate_id
attachment.name
attachment.content_type
attachment.data_url
attachment.data
attachment.type

Features

Feature	Notes
API Passthrough
Delta Syncs
Custom Field Explorer
Candidates
Applications
Source Writing
Sync Only Created Applications
Connection Guide
Prerequisites
Candidate Cutoff Filtering
Roles
Job roles (e.g. Hiring Manager)	iCIMS exposes 3 standard job roles:

• hiringmanager maps to unified type HIRING_MANAGER
• recruiter maps to unified type RECRUITER
• secondaryrecruiter maps to unified type RECRUITER with the label “Secondary Recruiter”

Additional hiring team members can be surfaced via the hiring_team_role_field_mappings setting. People referenced by those custom job fields sync with the mapping’s configured label and no unified type. |

​

Integration Variants

Current connector: iCIMS

For iCIMS, we also offer the following other connector variants:

iCIMS Assessment

iCIMS for the Assessment category