Available Connectors
Ashby ATS Integration
Ashby connector for Kombo’s ATS API
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
Users
Users
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| first_name | |
| last_name | |
| status | |
| remote_data |
Jobs
Jobs
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| 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 | |
| opened_at | |
| remote_data |
Job postings
Job postings
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| title | |
| description_html | |
| status | |
| visibility | |
| url | |
| job_id |
Candidates
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 | |
| remote_created_at | |
| remote_updated_at | |
| remote_data |
Application Stages
Application Stages
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| remote_data |
Applications
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 | |
| remote_created_at | |
| remote_updated_at | |
| remote_data |
Screening questions
Screening questions
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| title | |
| description | |
| format | |
| category |
Tags
Tags
Interviews
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 | |
| application_id | |
| stage_id | |
| remote_created_at | |
| remote_updated_at | |
| remote_data |
Offers
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
Rejection reasons
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| remote_data |
Candidate tags
Candidate tags
Job-specific application stages
Job-specific application stages
| Field | Notes |
|---|---|
| index | |
| job_id | |
| stage_id | |
| id | |
| changed_at | |
| remote_deleted_at |
Job-specific screening questions
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
Job hiring team members
| Field | Notes |
|---|---|
| roles | |
| job_id | |
| user_id | |
| id | |
| changed_at | |
| remote_deleted_at |
Interviewing team members
Interviewing team members
| Field | Notes |
|---|---|
| interview_id | |
| user_id | |
| id | |
| changed_at | |
| remote_deleted_at |
Users
Users
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| first_name | |
| last_name | |
| status | |
| remote_data |
Jobs
Jobs
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| 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 | |
| opened_at | |
| remote_data |
Job postings
Job postings
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| title | |
| description_html | |
| status | |
| visibility | |
| url | |
| job_id |
Candidates
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 | |
| remote_created_at | |
| remote_updated_at | |
| remote_data |
Application Stages
Application Stages
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| remote_data |
Applications
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 | |
| remote_created_at | |
| remote_updated_at | |
| remote_data |
Screening questions
Screening questions
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| title | |
| description | |
| format | |
| category |
Tags
Tags
Interviews
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 | |
| application_id | |
| stage_id | |
| remote_created_at | |
| remote_updated_at | |
| remote_data |
Offers
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
Rejection reasons
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| remote_data |
Candidate tags
Candidate tags
Job-specific application stages
Job-specific application stages
| Field | Notes |
|---|---|
| index | |
| job_id | |
| stage_id | |
| id | |
| changed_at | |
| remote_deleted_at |
Job-specific screening questions
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
Job hiring team members
| Field | Notes |
|---|---|
| roles | |
| job_id | |
| user_id | |
| id | |
| changed_at | |
| remote_deleted_at |
Interviewing team members
Interviewing team members
| Field | Notes |
|---|---|
| interview_id | |
| user_id | |
| id | |
| changed_at | |
| remote_deleted_at |
Create candidate
Create candidate
| 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 | |
| screening_question_answers.question_id | |
| screening_question_answers.answer | |
| attachments.name | |
| attachments.content_type | |
| attachments.data | |
| attachments.data_url | |
| attachments.type | |
| source.name |
Create application
Create application
| 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 | |
| screening_question_answers.question_id | |
| screening_question_answers.answer | |
| attachments.name | |
| attachments.content_type | |
| attachments.data | |
| attachments.data_url | |
| attachments.type | |
| source.name |
Add tag to candidate
Add tag to candidate
| Input Field | Notes |
|---|---|
| candidate_id | |
| tag.name |
Add attachment to application
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 | |
| attachment.type |
Move application to stage
Move application to stage
| Input Field | Notes |
|---|---|
| application_id | |
| stage_id |
Reject application
Reject application
| Input Field | Notes |
|---|---|
| application_id | |
| rejection_reason_id |
Add result link to application
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
Add note to application
| Input Field | Notes |
|---|---|
| application_id | |
| content |
Get application attachments
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 |
Add attachment to candidate
Add attachment to candidate
| Input Field | Notes |
|---|---|
| candidate_id | |
| attachment.name | |
| attachment.content_type | |
| attachment.data | |
| attachment.type |
Add result link to candidate
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 |
|---|---|
| Source Writing | |
| Sync Only Created Applications | |
| Connection Guide | |
| Prerequisites | |
| Create credentials | |
| Candidate source tracking | |
| API Passthrough | |
| Webhook Subscriptions | |
| Scope Testing | |
| Per Model Tests | |
| Per Field Tests | |
| Delta Syncs | |
| EEO Questions | We support surveys (including surveys with demographic and EEO questions) |