Greenhouse
Greenhouse is an applicant tracking system and recruiting software that's designed to help companies build better hiring processes and hire for what's next.
The Greenhouse connector enables you to build even more automation around applicant and candidate workflow, and connect with other human resource management systems.
Use cases
Connect Greenhouse with your HR and IT systems to automate hiring and onboarding. You can integrate the Greenhouse connector with other apps to sync candidate data, automate onboarding, and improve efficiency across your HR and IT workflows. Explore our use cases to discover how you can use the Greenhouse connector to create powerful multi-app workflows:
- Sync Greenhouse offer letters to Box and create onboarding requests in ServiceNow.
- Sync Greenhouse new hires to SAP SuccessFactors.
Example Greenhouse use case
API version
The Greenhouse connector uses both legacy (v1/v2) and v3 APIs:
- API key authentication uses v1/v2 APIs
- OAuth 2.0 authorization code grant authentication uses v3 APIs
MIGRATION REQUIRED
If your connections use API key authentication (v1/v2), migrate to OAuth 2.0 authorization code grant authentication and replace all v1/v2 triggers and actions with their v3 equivalents before August 30, 2026. Greenhouse will remove support for the v1 and v2 APIs on this date.
Refer to the Greenhouse v3 migration guide and the Greenhouse v3 object coverage guide for more information.
Existing connections that use API key authentication continue to run until August 30, 2026.
Connection setup
The Greenhouse connector supports the following authentication types:
Connections that use API key authentication support only v1/v2 actions; connections that use OAuth 2.0 support only v3 actions.
New Greenhouse connections support OAuth 2.0 authorization code grant authentication only. API key authentication is available for existing connections only.
If you use API key authentication, refer to the Greenhouse v3 migration guide to migrate your existing connections and recipes.
OAuth 2.0 authorization code grant authentication (v3)
Use OAuth 2.0 authorization code grant authentication to connect to Greenhouse with v3 APIs. This is the default authentication method for all new connections.
Minimum and default scopes
Harvest OAuth scopes define the level of access Workato has to your Greenhouse instance.
View minimum scopes
The following scope is always included when you select specific scopes:
harvest:users:list
View default scopes
All scopes in this list are requested if you leave the Harvest OAuth scopes field blank:
harvest:application_stages:listharvest:applications:convert_to_candidateharvest:applications:createharvest:applications:destroyharvest:applications:hireharvest:applications:listharvest:applications:moveharvest:applications:rejectharvest:applications:unrejectharvest:applications:updateharvest:approval_flows:createharvest:approval_flows:listharvest:approval_flows:request_approvalsharvest:approval_flows:updateharvest:attachments:createharvest:attachments:destroyharvest:attachments:listharvest:candidate_educations:createharvest:candidate_employments:createharvest:candidates:anonymizeharvest:candidates:createharvest:candidates:destroyharvest:candidates:listharvest:candidates:mergeharvest:candidates:updateharvest:close_reasons:listharvest:custom_field_departments:listharvest:custom_field_offices:listharvest:custom_field_options:createharvest:custom_field_options:destroyharvest:custom_field_options:listharvest:custom_field_options:updateharvest:custom_fields:createharvest:custom_fields:destroyharvest:custom_fields:listharvest:custom_fields:updateharvest:departments:createharvest:departments:listharvest:departments:updateharvest:email_templates:listharvest:interviews:createharvest:interviews:destroyharvest:interviews:listharvest:interviews:updateharvest:job_hiring_managers:listharvest:job_interview_stages:listharvest:job_owners:listharvest:job_posts:listharvest:jobs:createharvest:jobs:listharvest:jobs:updateharvest:notes:createharvest:notes:listharvest:offers:createharvest:offers:listharvest:offers:updateharvest:offices:createharvest:offices:listharvest:offices:updateharvest:openings:listharvest:prospect_pools:listharvest:referrers:listharvest:rejection_reasons:listharvest:scorecard_question_answers:listharvest:scorecards:listharvest:sources:listharvest:user_emails:listharvest:users:activateharvest:users:createharvest:users:deactivateharvest:users:listharvest:users:revoke_permissionsharvest:users:update
Connect to Greenhouse with OAuth 2.0 authorization code grant authentication
API key authentication (v1/v2)
DEPRECATED AUTHENTICATION
Greenhouse will remove support for v1 and v2 APIs on August 30, 2026. Use OAuth 2.0 authorization code grant authentication for new connections.
Use API key authentication to manage existing Greenhouse connections that use legacy APIs. API key authentication isn't available for new connections.
Greenhouse setup for API key authentication
We recommend using an Integration System User (ISU) for integration with Workato. This ensures that permissions are consistent and all operations can be logged on a single account.
Create an API token
Minimum permissions for Harvest API
Connect to Greenhouse using API key authentication (v1/v2)
Last updated: