This connector is in open beta. You can freely enable it in your account.
The Recruit CRM ATS integration allows you to sync ATS data between Recruit CRM and your application through Kombo’s unified API. The tool slug for this connector is recruitcrm.
Recruit CRM screening questions are always free-text inputs.
Field
Notes
id
remote_id
changed_at
remote_deleted_at
title
description
format
remote_data
Roles
Field
Notes
id
remote_id
changed_at
remote_deleted_at
remote_label
scope
unified_type
remote_data
Job-specific application stages
Field
Notes
index
job_id
stage_id
id
changed_at
remote_deleted_at
Job-specific screening questions
Field
Notes
index
required
precondition_question_id
precondition_options
job_id
question_id
id
changed_at
remote_deleted_at
Job hiring team members
Field
Notes
roles
job_id
user_id
id
changed_at
remote_deleted_at
User roles
Field
Notes
user_id
role_id
id
changed_at
remote_deleted_at
Create candidate
If an exact-email candidate already exists in Recruit CRM, this action reuses the most recently updated profile instead of creating a duplicate candidate. CV and OTHER attachments written by this action live on the candidate profile, not on a specific application record.
Input Field
Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.company
candidate.title
candidate.phone_number
candidate.location.city
candidate.location.country
candidate.location.state
candidate.location.street_1
candidate.location.zip_code
candidate.availability_date
candidate.salary_expectations.amount
candidate.social_links.url
application.job_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
Create application
If an exact-email candidate already exists in Recruit CRM, this action reuses the most recently updated profile instead of creating a duplicate candidate. CV and OTHER attachments written by this action live on the candidate profile, not on a specific application record.
Input Field
Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.company
candidate.title
candidate.phone_number
candidate.location.city
candidate.location.country
candidate.location.state
candidate.location.street_1
candidate.location.zip_code
candidate.availability_date
candidate.salary_expectations.amount
candidate.social_links.url
application.job_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
Add attachment to application
CV and OTHER attachments live on the candidate, not on a specific application record. This action writes those files 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 note to application
Recruit CRM notes are attached to the candidate profile, not to a specific application. You need to configure a target note type ID in the integration settings.
Input Field
Notes
application_id
content
Get application attachments
CV and OTHER attachments live on the candidate, so they can appear on every application for that candidate.
Input Field
Notes
application_id
Feature
Notes
Source Writing
Sync Only Created Applications
Connection Guide
Roles
System roles (e.g. Admin)
API Passthrough
Webhook Subscriptions
candidate.assigned: triggered when a candidate was assigned to a job in Recruit CRM candidate.external.applied.jobs: triggered when a candidate applied to a job through Recruit CRM’s external form candidate.hiringstage.updated: triggered when an application stage changed on a job candidate.unassigned: triggered when a candidate was unassigned from a job candidate.created: triggered when a candidate was created candidate.created.talentpool: triggered when a candidate was created from a talent pool candidate.updated: triggered when a candidate was updated candidate.external.profile.updated: triggered when a candidate updated their profile through Recruit CRM’s external profile form candidate.deleted: triggered when a candidate was deleted job.created: triggered when a job was created job.updated: triggered when a job was updated job.status.updated: triggered when a job status changed job.deleted: triggered when a job was deleted contact.created: triggered when a contact was created contact.updated: triggered when a contact was updated contact.deleted: triggered when a contact was deleted Not covered: interview scheduled Not covered: interview updated Not covered: tag assigned Not covered: job published Not covered: job unpublished Not covered: screening questions updated
