Cornerstone TalentLink connector for Kombo’s ATS API
This connector is in open beta. You can freely enable it in your account.
The Cornerstone TalentLink ATS integration allows you to sync ATS data between Cornerstone TalentLink and your application through Kombo’s unified API. The tool slug for this connector is cornerstonetalentlink.
Users embedded in TalentLink position teams do not include email addresses or user status.
Field
Notes
id
remote_id
changed_at
remote_deleted_at
first_name
last_name
remote_data
Jobs
We sync one job advert per job. To ensure best results, your customer should only assign one advert per job to your integration.
Field
Notes
id
remote_id
changed_at
remote_deleted_at
name
job_code
description
employment_type
status
post_url
remote_work_status
salary_amount
salary_amount_from
salary_amount_to
salary_currency
salary_period
location
custom_fields
integration_fields
remote_created_at
remote_updated_at
remote_data
Candidates
Field
Notes
id
remote_id
changed_at
remote_deleted_at
first_name
last_name
source
phone_numbers
email_addresses
social_media
location
remote_created_at
remote_updated_at
remote_data
Application Stages
Field
Notes
id
remote_id
changed_at
remote_deleted_at
name
remote_data
Applications
Field
Notes
id
remote_id
changed_at
remote_deleted_at
outcome
current_stage_id
job_id
candidate_id
remote_data
Screening questions
Field
Notes
id
remote_id
changed_at
remote_deleted_at
title
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
TalentLink recruiters map to the unified RECRUITER role.
Operational team members are collapsed into a single Operational role without a unified type, because TalentLink lovValues under that key mix hiring managers, HR, and other roles.
Position approvers are excluded because TalentLink documents them as approval-workflow participants rather than hiring-team members.
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
Create candidate
Creating applications will fail when screening questions are marked as required but are not answered. TalentLink requires querying a separate endpoint to get the status of a submission. This action will time out if, after 5 minutes, the status does not return “SUBMITTED”. It is possible that the application is still created after the action timed out. TalentLink requires phone numbers to include a regional prefix (such as +49). If the input does not contain it, we attempt to use the candidate’s location. If neither of these options work, the phone number will not be submitted.
Input Field
Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.phone_number
candidate.location.city
candidate.location.country
candidate.location.street_1
candidate.location.zip_code
application.job_id
screening_question_answers.question_id
screening_question_answers.answer
attachments.name
attachments.data_url
attachments.data
attachments.type
source.name
source.unified_key
source.id
Create application
Creating applications will fail when screening questions are marked as required but are not answered. TalentLink requires querying a separate endpoint to get the status of a submission. This action will time out if, after 5 minutes, the status does not return “SUBMITTED”. It is possible that the application is still created after the action timed out. TalentLink requires phone numbers to include a regional prefix (such as +49). If the input does not contain it, we attempt to use the candidate’s location. If neither of these options work, the phone number will not be submitted.
Input Field
Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.phone_number
candidate.location.city
candidate.location.country
candidate.location.street_1
candidate.location.zip_code
application.job_id
screening_question_answers.question_id
screening_question_answers.answer
attachments.name
attachments.data_url
attachments.data
attachments.type
source.name
source.unified_key
source.id
Add attachment to application
Input Field
Notes
application_id
attachment.name
attachment.content_type
attachment.data_url
attachment.data
attachment.type
Move application to stage
Moving an application has the same effects as changing its status manually in TalentLink, including any configured workflows.
Input Field
Notes
application_id
stage_id
Add note to application
Notes are appended to the application memo in TalentLink instead of creating separate timeline entries. Adding a note uses TalentLink’s status update operation and may trigger configured workflows.
Input Field
Notes
application_id
content
Get application attachments
Input Field
Notes
application_id
Get candidate attachments
Input Field
Notes
candidate_id
Feature
Notes
API Passthrough
Delta Syncs
Source Writing
Sync Only Created Applications
Connection Guide
Prerequisites
Roles
Job roles (e.g. Hiring Manager)
TalentLink recruiters map to the unified RECRUITER role.
Operational team members are collapsed into a single Operational role without a unified type, because TalentLink lovValues under that key mix hiring managers, HR, and other roles.
Position approvers are excluded because TalentLink documents them as approval-workflow participants rather than hiring-team members.
