Ashby ATS Integration

The Ashby ATS integration allows you to sync ATS data between Ashby and your application through Kombo’s unified API. The tool slug for this connector is ashby.

Guides and Resources

Connection Setup Guide

Step-by-step instructions to connect your Ashby account to Kombo.

Source Setup Guide

Learn how to set up candidate sources in Ashby.

View Candidate Sources

How to view and manage candidate sources in Ashby.

Supported Features & Coverage

Models
Actions
Features

Users

Field	Notes
id
remote_id
changed_at
remote_deleted_at
first_name
last_name
email
status
remote_data

Jobs

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
job_code
description
confidential
employment_type
status
visibility
department
post_url
remote_work_status
salary_amount_from
salary_amount_to
salary_currency
salary_period
location
custom_fields
integration_fields
remote_url
opened_at
closed_at
remote_created_at
remote_updated_at
remote_data

Job postings

Field	Notes
id
remote_id
changed_at
remote_deleted_at
title
description_html
status
visibility
url
job_id

Candidates

Ashby allows recruiters to deduplicate candidates based on similar email, name, or social links. Candidate IDs may therefore change after candidate creation. Use application IDs as a source of truth if you want to keep track of a candidate’s progression

Field	Notes
id
remote_id
changed_at
remote_deleted_at
first_name
last_name
company
title
source
phone_numbers
email_addresses
social_media
location
custom_fields
integration_fields
remote_url
remote_created_at
remote_updated_at
remote_data

Application Stages

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
status
remote_data

Applications

Field	Notes
id
remote_id
changed_at
remote_deleted_at
outcome
rejection_reason_name
rejected_at
current_stage_id
job_id
candidate_id
screening_question_answers
custom_fields
integration_fields
remote_url
remote_created_at
remote_updated_at
remote_data

Screening questions

Field	Notes
id
remote_id
changed_at
remote_deleted_at
title
description
format
category

Tags

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
remote_data

Interviews

Ashby implements an Interview Status, but only for the Interview Schedule, not for specific interview events. If the Interview Status is marked as canceled, all interview events are deleted. Therefore, it is not possible to have canceled interviews in Ashby.

Field	Notes
id
remote_id
changed_at
remote_deleted_at
title
starting_at
ending_at
video_conferencing_url
application_id
stage_id
remote_created_at
remote_updated_at
remote_data

Offers

Field	Notes
id
remote_id
changed_at
remote_deleted_at
status
employment_start_date
application_id
custom_fields
integration_fields
remote_created_at
remote_updated_at
remote_data

Rejection reasons

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
remote_data

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-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

Each job’s hiring team lists members with a role title; Ashby’s defaults include 4 types, and organizations can add custom hiring team roles.

Recruiting Coordinator (shown as “Recruiting Coordinator” in the UI) maps to COORDINATOR
Hiring Manager (shown as “Hiring Manager” in the UI) maps to HIRING_MANAGER
Recruiter (shown as “Recruiter” in the UI) maps to RECRUITER
Sourcer (shown as “Sourcer” in the UI) maps to SOURCER
Other role values have no unified type.

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

User roles

Each user has globalRole from Ashby (e.g. Organization Admin, Elevated Access, Limited Access, External Recruiter for agency users).

Organization Admin maps to unified type ADMIN
External Recruiter maps to unified type RECRUITER
Limited Access and Elevated Access have no unified type.
Any other globalRole value has no unified type.

Field	Notes
user_id
role_id
id
changed_at
remote_deleted_at

Interviewing team members

Field	Notes
interview_id
user_id
id
changed_at
remote_deleted_at

Create candidate

Input Field	Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.additional_email_addresses.email_address
candidate.phone_number
candidate.location.city
candidate.location.country
candidate.location.state
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
sourced_by.user_id

Create application

Input Field	Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.additional_email_addresses.email_address
candidate.phone_number
candidate.location.city
candidate.location.country
candidate.location.state
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
sourced_by.user_id

Add tag to candidate

Input Field	Notes
candidate_id
tag.name

Add attachment to application

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
attachment.type

Move application to stage

Input Field	Notes
application_id
stage_id

Reject application

Input Field	Notes
application_id
rejection_reason_id

Add result link to application

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

Due to limitations of the API only the candidate CV can be fetched, the rest of the attachments will be omitted

Input Field	Notes
application_id

Get candidate attachments

Due to limitations of the API only the candidate CV can be fetched, the rest of the attachments will be omitted

Input Field	Notes
candidate_id

Add attachment to candidate

Input Field	Notes
candidate_id
attachment.name
attachment.content_type
attachment.data_url
attachment.data
attachment.type

Add result link to candidate

Input Field	Notes
candidate_id
label
url
details.custom_field_name_prefix
details.attributes.key
details.attributes.value

Feature	Notes
API Passthrough
Webhook Subscriptions	applicationSubmit: triggered when an application w/ candidate was created applicationUpdate: triggered when an application was updated in any way candidateHire: triggered when a candidate was hired candidateStageChange: triggered when a candidate/application stage was changed candidateDelete: triggered when a candidate was deleted interviewScheduleCreate: triggered when an interview was scheduled interviewScheduleUpdate: triggered when an interview was updated jobCreate: triggered when a job was created jobUpdate: triggered when a job was updated jobPostingDelete: triggered when a job posting was deleted jobPostingUpdate: triggered when a job posting was updated jobPostingPublish: triggered when a job posting was published jobPostingUnpublish: triggered when a job posting was unpublished offerCreate: triggered when an offer was created offerUpdate: triggered when an offer was updated offerDelete: triggered when an offer was deleted ping: triggered when a webhook was configured and the endpoint is checked to confirm it is working Not covered: a tag was assigned to a candidate Not covered: When only screening questions are updated on a job
Automatic Setup
Scope Testing
Per Model Tests
Per Field Tests
Delta Syncs
Source Writing
Sync Only Created Applications
Connection Guide
Prerequisites
Create credentials
Candidate source tracking
Roles
System roles (e.g. Admin)	Each user has globalRole from Ashby (e.g. Organization Admin, Elevated Access, Limited Access, External Recruiter for agency users).

Organization Admin maps to unified type ADMIN
External Recruiter maps to unified type RECRUITER
Limited Access and Elevated Access have no unified type.
Any other globalRole value has no unified type. | | Job roles (e.g. Hiring Manager) | Each job’s hiring team lists members with a role title; Ashby’s defaults include 4 types, and organizations can add custom hiring team roles.
Recruiting Coordinator (shown as “Recruiting Coordinator” in the UI) maps to COORDINATOR
Hiring Manager (shown as “Hiring Manager” in the UI) maps to HIRING_MANAGER
Recruiter (shown as “Recruiter” in the UI) maps to RECRUITER
Sourcer (shown as “Sourcer” in the UI) maps to SOURCER
Other role values have no unified type. | | EEO Questions | We support surveys (including surveys with demographic and EEO questions) |

Integration Variants

Current connector: Ashby For Ashby, we also offer the following other connector variants:

Ashby Assessment

Ashby for the Assessment category

General

Features

Guides

ATS API Reference

General API Reference

Ashby ATS Integration

Guides and Resources

Connection Setup Guide

Source Setup Guide

View Candidate Sources

Supported Features & Coverage

Integration Variants

Ashby Assessment

​Guides and Resources

Connection Setup Guide

Source Setup Guide

View Candidate Sources

​Supported Features & Coverage

​Integration Variants

Ashby Assessment

Guides and Resources

Supported Features & Coverage

Integration Variants