This connector is in open beta. You can freely enable it in your account.
The Talent360 ATS integration allows you to sync ATS data between Talent360 and your application through Kombo’s unified API. The tool slug for this connector is talent360.
Talent360 stores source per application; we use the first source we find as the candidate source.
Field
Notes
id
remote_id
changed_at
remote_deleted_at
first_name
last_name
source
phone_numbers
email_addresses
location
custom_fields
integration_fields
remote_created_at
remote_data
Application Stages
Field
Notes
id
remote_id
changed_at
remote_deleted_at
name
status
Applications
Talent360 tracks a single status per candidate rather than per application, so all applications of the same candidate share the same current_stage_id and outcome. When a candidate is Hired or Rejected, every one of their applications is marked HIRED or DECLINED.
Field
Notes
id
remote_id
changed_at
remote_deleted_at
outcome
current_stage_id
job_id
candidate_id
custom_fields
integration_fields
remote_created_at
remote_data
Roles
Field
Notes
id
remote_id
changed_at
remote_deleted_at
remote_label
scope
unified_type
Job user role assignments
Talent360 job ads expose a single “responsible recruiter” per ad.
The responsible recruiter maps to RECRUITER.
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
Add attachment to application
Talent360 has no application-level file store, so attachments are stored on the underlying candidate as “application” (Bewerbung) documents, regardless of the attachment type.
Input Field
Notes
application_id
attachment.name
attachment.content_type
attachment.data_url
attachment.data
Move application to stage
Talent360 only supports moving applications to the “Qualified”, “Hired” or “Rejected” stages. The early-funnel stages (“New”, “Contacted” and “Interview”) are read-only and cannot be set via the API. Talent360 tracks a single status per candidate rather than per application, so moving one application also moves the candidate’s other applications to the same stage.
Input Field
Notes
application_id
stage_id
Add result link to application
Talent360 has no dedicated result-link field, so the link is added as an internal note (communication) on the candidate: the label becomes the note subject and the URL is the note body. Requires remote_fields.talent360.user_id because every Talent360 communication must be attributed to a user.
Input Field
Notes
application_id
label
url
Add note to application
Talent360 stores notes on the candidate as an internal communication, not on a specific application. Requires remote_fields.talent360.user_id because every Talent360 communication must be attributed to a user.
Input Field
Notes
application_id
content
Get application attachments
Talent360 has no application-level file store, so all documents live on the candidate. Reading an application’s attachments therefore returns every document attached to the underlying candidate.
Input Field
Notes
application_id
Get candidate attachments
Talent360 stores documents on the candidate (not per application), so every returned attachment has a null application_id.
Input Field
Notes
candidate_id
Add result link to candidate
Talent360 has no dedicated result-link field, so the link is added as an internal note (communication) on the candidate: the label becomes the note subject and the URL is the note body. Requires remote_fields.talent360.user_id because every Talent360 communication must be attributed to a user.
Input Field
Notes
candidate_id
label
url
Feature
Notes
Sync Only Created Applications
Connection Guide
Roles
Job roles (e.g. Hiring Manager)
Talent360 job ads expose a single “responsible recruiter” per ad.
The responsible recruiter maps to RECRUITER. |
Was this page helpful?
⌘I
Assistant
Responses are generated using AI and may contain mistakes.
