This connector is in open beta. You can freely enable it in your account.
The Kula ATS integration allows you to sync ATS data between Kula and your application through Kombo’s unified API. The tool slug for this connector is kula.
Derived from the Kula interview status: true when the interview is cancelled or marked as a candidate no-show, and false for any other status (not started, in progress, ended).
remote_created_at
remote_updated_at
Offers
Field
Notes
id
remote_id
changed_at
remote_deleted_at
status
application_id
custom_fields
integration_fields
remote_created_at
Roles
Field
Notes
id
remote_id
changed_at
remote_deleted_at
remote_label
scope
unified_type
Candidate tags
Field
Notes
candidate_id
tag_id
id
changed_at
remote_deleted_at
Job-specific application stages
Field
Notes
index
job_id
stage_id
id
changed_at
remote_deleted_at
Job user role assignments
Kula exposes four hiring team lists on each job:
recruiters maps to unified type RECRUITER
hiring_managers maps to unified type HIRING_MANAGER
coordinators maps to unified type COORDINATOR
external_recruiters maps to unified type 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
Interviewing team members
Field
Notes
interview_id
user_id
id
changed_at
remote_deleted_at
Create candidate
Kula POST /v1/candidates does not accept file attachments.
Input Field
Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.phone_number
candidate.social_links.url
application.job_id
application.stage_id
source.name
source.unified_key
source.id
sourced_by.user_id
Create application
Kula POST /v1/candidates does not accept file attachments.
Input Field
Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.phone_number
candidate.social_links.url
application.job_id
application.stage_id
source.name
source.unified_key
source.id
sourced_by.user_id
Move application to stage
Input Field
Notes
application_id
stage_id
Add result link to application
Kula does not expose a dedicated result link field. Result links are written as an application note (POST /v1/applications//notes) using the standard Kombo plain-text summary (label, details, and URL).
Input Field
Notes
application_id
label
url
details.custom_field_name_prefix
details.attributes.key
details.attributes.value
Add note to application
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
Upstream Webhooks
candidate.created: triggered when a candidate profile is created candidate.updated: triggered when a candidate profile is updated application.created: triggered when an application is submitted application.screened: triggered when an application screening completes application.updated: triggered when an application is substantially updated application.stage_changed: triggered when an application stage changes application.rejected: triggered when an application is rejected application.hired: triggered when an application is marked hired job.created: triggered when a job is created job.updated: triggered when a job is updated job_posting.published: triggered when a job posting is published and goes live job_posting.updated: triggered when a published job posting is updated requisition.created: triggered when a requisition is created requisition.updated: triggered when a requisition is updated requisition.opened: triggered when a requisition is opened requisition.filled: triggered when a requisition is filled requisition.closed: triggered when a requisition is closed offer.created: triggered when an offer record is created offer.updated: triggered when an offer record is updated offer.approved: triggered when an offer is approved in workflow offer.deleted: triggered when an offer is cancelled or deleted offer.accepted: triggered when a candidate accepts an offer offer.declined: triggered when a candidate declines an offer Not covered: job unpublished when a posting is taken offline When an application stage changed we re-fetch the application from the Kula API. Not covered: tag assigned to candidates Not covered: screening questions updated on jobs Not covered: interview scheduled Not covered: interview scheduled and interview updated
Automatic Setup
Scope Testing
Delta Syncs
Source Writing
Sync Only Created Applications
Connection Guide
Roles
Job roles (e.g. Hiring Manager)
Kula exposes four hiring team lists on each job:
recruiters maps to unified type RECRUITER
hiring_managers maps to unified type HIRING_MANAGER
coordinators maps to unified type COORDINATOR
external_recruiters maps to unified type RECRUITER |