The Teamtailor ATS integration allows you to sync ATS data between Teamtailor and your application through Kombo’s unified API. The tool slug for this connector is teamtailor.
It is not possible to answer screening questions of type ‘file’ via the Teamtailor API. The submitted answers will be uploaded as other attachments instead. Teamtailor only supports LinkedIn as a social link. Other links will be ignored.
Input Field
Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.title
candidate.phone_number
candidate.social_links.url
application.job_id
application.stage_id
screening_question_answers.question_id
screening_question_answers.answer
attachments.name
attachments.content_type
attachments.data_url
attachments.data
attachments.type
source.name
source.unified_key
source.id
gdpr_consent.given
Create application
It is not possible to answer screening questions of type ‘file’ via the Teamtailor API. The submitted answers will be uploaded as other attachments instead. Teamtailor only supports LinkedIn as a social link. Other links will be ignored.
Input Field
Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.title
candidate.phone_number
candidate.social_links.url
application.job_id
application.stage_id
screening_question_answers.question_id
screening_question_answers.answer
attachments.name
attachments.content_type
attachments.data_url
attachments.data
attachments.type
source.name
source.unified_key
source.id
gdpr_consent.given
Add tag to candidate
Parallel use of this action is not recommended for Teamtailor.
Input Field
Notes
candidate_id
tag.name
Remove tag from candidate
Parallel use of this action is not recommended for Teamtailor.
Input Field
Notes
candidate_id
tag.name
Add attachment to application
It’s not possible to add new “CV”s. Every CV attachment that is added will have type “other” inside TeamTailor. 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
Move application to stage
Input Field
Notes
application_id
stage_id
Reject application
When rejecting an application, Teamtailor shows it as rejected by “Deleted User” in the API. You can however specify a user id under remote_fields.teamtailor.user_id to provide an author for the note behind the rejection.
Input Field
Notes
application_id
rejection_reason_id
note
Add result link to application
In Teamtailor, we can not write additional details to the result link. We can only write the URL and label.
Input Field
Notes
application_id
label
url
Add note to application
To write a note, we need to select a valid admin user. We automatically select the first admin user in the system. You can overwrite this by submitting a valid user ID at remote_fields?.teamtailor?.user_id to this endpoint.
Input Field
Notes
application_id
content
Get application attachments
Input Field
Notes
application_id
Get candidate attachments
Input Field
Notes
candidate_id
Add attachment to candidate
It’s not possible to add new “CV”s. Every CV attachment that is added will have type “other” inside TeamTailor.
Input Field
Notes
candidate_id
attachment.name
attachment.content_type
attachment.data_url
attachment.data
Add result link to candidate
In Teamtailor, we can not write additional details to the result link. We can only write the URL and label.
Input Field
Notes
candidate_id
label
url
Feature
Notes
Source Writing
Sync Only Created Applications
Connection Guide
Prerequisites
Create credentials
API Passthrough
Webhook Subscriptions
candidate.create: triggered when a candidate was created candidate.destroy: triggered when a candidate was deleted candidate.update: triggered when a candidate was updated job_application.create: triggered when a job application was created job_application.destroy: triggered when a job application was deleted job_application.update: triggered when a job application was updated including stage changed job.create: triggered when a job was created job.destroy: triggered when a job was deleted job.update: triggered when a job was updated including being published or unpublished user.create: triggered when a user with access to the Teamtailor dashboard was created user.destroy: triggered when a user with access to the Teamtailor dashboard was deleted user.update: triggered when a user with access to the Teamtailor dashboard was updated Not covered: a tag was assigned or removed from a candidate Not covered: an interview was scheduled or updated Not covered: screening questions were updated for a job
Current connector: Choose this variant if you want to use the full Teamtailor ATS integration with comprehensive read/write capabilities for jobs, candidates, applications, and moreFor Teamtailor, we also offer the following other connector variants:
