Greenhouse ATS Integration

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

Guides and Resources

Connection Setup Guide

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

Source Setup Guide

Learn how to set up candidate sources in Greenhouse.

View Candidate Sources

How to view and manage candidate sources in Greenhouse.

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
salary_amount
salary_amount_from
salary_amount_to
salary_currency
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
remote_data
remote_created_at
remote_updated_at

Candidates

Field	Notes
id
remote_id
changed_at
remote_deleted_at
first_name
last_name
company
title
confidential
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
remote_data

Applications

We can’t easily infer the type of questions for screening question answers.

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

Tags

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
remote_data

Interviews

Greenhouse only gives us the response status of the interviewers, not the candidate’s. Therefore, we assume that if all interviewers decline the interview, it is considered canceled.

Field	Notes
id
remote_id
changed_at
remote_deleted_at
title
starting_at
ending_at
location
video_conferencing_url
application_id
canceled
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

Greenhouse exposes 4 hiring team lists per job. We also look at per-user job permissions (e.g. Job Admin).

coordinators (shown as “Coordinators” in the UI) maps to COORDINATOR
hiring_managers (shown as “Hiring Managers” in the UI) maps to HIRING_MANAGER
recruiters (shown as “Recruiters” in the UI) maps to RECRUITER
sourcers (shown as “Sourcers” in the UI) maps to SOURCER
Custom job permissions role name values show as-is and 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

Greenhouse derives roles from site_admin on the user and job-assignment state. If job-admin data cannot be fetched, no system role rows are created.

When site_admin is true, Kombo maps to unified type ADMIN
When site_admin is false, Kombo maps to either Job Admin or Basic depending on assignments; both have 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.company
candidate.title
candidate.phone_number
candidate.additional_phone_numbers.phone_number
candidate.location.city
candidate.location.country
candidate.social_links.url
application.job_id
application.stage_id
attachments.name
attachments.content_type
attachments.data_url
attachments.data
attachments.type	Attachments of type “OTHER” will only be visible to admins due to a limitation in Greenhouse’s API.
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.company
candidate.title
candidate.phone_number
candidate.additional_phone_numbers.phone_number
candidate.location.city
candidate.location.country
candidate.social_links.url
application.job_id
application.stage_id
attachments.name
attachments.content_type
attachments.data_url
attachments.data
attachments.type	Attachments of type “OTHER” will only be visible to admins due to a limitation in Greenhouse’s API.
source.name
source.unified_key
source.id
sourced_by.user_id

Add tag to candidate

Input Field	Notes
candidate_id
tag.name

Remove tag from candidate

Input Field	Notes
candidate_id
tag.name

Add attachment to application

Input Field	Notes
application_id
attachment.name
attachment.content_type
attachment.data_url
attachment.data
attachment.type	Attachments of type “OTHER” will only be visible to admins due to a limitation in Greenhouse’s API.

Move application to stage

Input Field	Notes
application_id
stage_id

Reject application

Input Field	Notes
application_id
rejection_reason_id
note

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

Input Field	Notes
application_id

Get candidate attachments

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	Attachments of type “OTHER” will only be visible to admins due to a limitation in Greenhouse’s API.

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
Locate Admin
Create credentials
Candidate source tracking
Create Candidate Full Attachment Retry
Candidate Cutoff Filtering
Roles
System roles (e.g. Admin)	Greenhouse derives roles from site_admin on the user and job-assignment state. If job-admin data cannot be fetched, no system role rows are created.

When site_admin is true, Kombo maps to unified type ADMIN
When site_admin is false, Kombo maps to either Job Admin or Basic depending on assignments; both have no unified type. | | Job roles (e.g. Hiring Manager) | Greenhouse exposes 4 hiring team lists per job. We also look at per-user job permissions (e.g. Job Admin).
coordinators (shown as “Coordinators” in the UI) maps to COORDINATOR
hiring_managers (shown as “Hiring Managers” in the UI) maps to HIRING_MANAGER
recruiters (shown as “Recruiters” in the UI) maps to RECRUITER
sourcers (shown as “Sourcers” in the UI) maps to SOURCER
Custom job permissions role name values show as-is and have no unified type. | | API Passthrough | | | Webhook Subscriptions | application_updated: triggered when an application was updated candidate_stage_change: triggered when a candidate/application stage was changed new_candidate_application: triggered when a new candidate application was created new_prospect_application: triggered when a new prospect application was created delete_application: triggered when an application was deleted hire_candidate: triggered when a candidate was hired unhire_candidate: triggered when a candidate was unhired reject_candidate: triggered when a candidate was rejected unreject_candidate: triggered when a candidate was unrejected candidate_anonymized: triggered when a candidate was anonymized update_candidate: triggered when a candidate was updated including tag assigned/unassigned delete_candidate: triggered when a candidate was deleted interview_deleted: triggered when an interview was deleted job_created: triggered when a job was created job_deleted: triggered when a job was deleted job_updated: triggered when a job was updated job_approved: triggered when a job was approved job_post_deleted: triggered when a job post was deleted job_post_created: triggered when a job post was created job_post_updated: triggered when a job post was updated including published/unpublished merge_candidate: triggered when a candidate was merged offer_created: triggered when an offer was created offer_approved: triggered when an offer was approved offer_updated: triggered when an offer was updated offer_deleted: 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: interview scheduled or updated Not covered: screening questions updated for a job | | Scope Testing | | | Delta Syncs | |

Integration Variants

Current connector: Choose this variant if you want to use the Greenhouse Harvest API For Greenhouse, we also offer the following other connector variants:

Greenhouse (V3)

Choose this variant if you want to use the Greenhouse Harvest API V3 with OAuth2 authentication

Greenhouse Job Board

Choose this variant if you want to write Screening Questions with the Greenhouse Job Board API, this integration’s coverage is limited

Greenhouse Assessment

Greenhouse for the Assessment category

Multiple variants can be used within your Kombo environment at the same time.

General

Features

Guides

ATS API Reference

General API Reference

Greenhouse ATS Integration

Guides and Resources

Connection Setup Guide

Source Setup Guide

View Candidate Sources

Supported Features & Coverage

Integration Variants

Greenhouse (V3)

Greenhouse Job Board

Greenhouse Assessment

General

Features

Guides

ATS API Reference

General API Reference

Documentation Index

​Guides and Resources

Connection Setup Guide

Source Setup Guide

View Candidate Sources

​Supported Features & Coverage

​Integration Variants

Greenhouse (V3)

Greenhouse Job Board

Greenhouse Assessment

Guides and Resources

Supported Features & Coverage

Integration Variants