Product UpdatesStatus PageWorkato Academy
English
日本語
Get a trial
Connectivity
App connectors

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:

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:list
  • harvest:applications:convert_to_candidate
  • harvest:applications:create
  • harvest:applications:destroy
  • harvest:applications:hire
  • harvest:applications:list
  • harvest:applications:move
  • harvest:applications:reject
  • harvest:applications:unreject
  • harvest:applications:update
  • harvest:approval_flows:create
  • harvest:approval_flows:list
  • harvest:approval_flows:request_approvals
  • harvest:approval_flows:update
  • harvest:attachments:create
  • harvest:attachments:destroy
  • harvest:attachments:list
  • harvest:candidate_educations:create
  • harvest:candidate_employments:create
  • harvest:candidates:anonymize
  • harvest:candidates:create
  • harvest:candidates:destroy
  • harvest:candidates:list
  • harvest:candidates:merge
  • harvest:candidates:update
  • harvest:close_reasons:list
  • harvest:custom_field_departments:list
  • harvest:custom_field_offices:list
  • harvest:custom_field_options:create
  • harvest:custom_field_options:destroy
  • harvest:custom_field_options:list
  • harvest:custom_field_options:update
  • harvest:custom_fields:create
  • harvest:custom_fields:destroy
  • harvest:custom_fields:list
  • harvest:custom_fields:update
  • harvest:departments:create
  • harvest:departments:list
  • harvest:departments:update
  • harvest:email_templates:list
  • harvest:interviews:create
  • harvest:interviews:destroy
  • harvest:interviews:list
  • harvest:interviews:update
  • harvest:job_hiring_managers:list
  • harvest:job_interview_stages:list
  • harvest:job_owners:list
  • harvest:job_posts:list
  • harvest:jobs:create
  • harvest:jobs:list
  • harvest:jobs:update
  • harvest:notes:create
  • harvest:notes:list
  • harvest:offers:create
  • harvest:offers:list
  • harvest:offers:update
  • harvest:offices:create
  • harvest:offices:list
  • harvest:offices:update
  • harvest:openings:list
  • harvest:prospect_pools:list
  • harvest:referrers:list
  • harvest:rejection_reasons:list
  • harvest:scorecard_question_answers:list
  • harvest:scorecards:list
  • harvest:sources:list
  • harvest:user_emails:list
  • harvest:users:activate
  • harvest:users:create
  • harvest:users:deactivate
  • harvest:users:list
  • harvest:users:revoke_permissions
  • harvest:users:update

Connect to Greenhouse with OAuth 2.0 authorization code grant authentication ​

Complete the following steps to set up an OAuth 2.0 authorization code grant authentication connection to Greenhouse in Workato:

1

Click Create > Connection or press C twice.

2

Search for Greenhouse and select it as your app.

3

Enter a name for your connection in the Connection name field.

Authentication using OAuth 2.0Authentication using OAuth 2.0

4

Use the Location drop-down menu to select the project where you plan to store the connection.

5

Optional. Select the required Harvest OAuth scopes. Refer to Minimum and default scopes for more information.

6

Optional. Enter a value in the Custom domain field. Leave blank to use the default Harvest API host: https://harvest.greenhouse.io. If your organization uses a custom subdomain, such as https://acme.greenhouse.io, enter acme.greenhouse.io.

7

Click Connect.

8

Sign in to your Greenhouse account and authorize access.

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 ​

Complete the following steps to create an API token in Greenhouse:

1

Navigate to Settings > Dev Center > API Credential Management.

2

Select Harvest v3 (OAuth) or Harvest v1/v2 to create a new API key for Workato.

3

Click Create new API credentials.

4

Use the API type drop-down menu to select Harvest or Harvest V3 (OAuth).

5

Use the Partners drop-down menu to select Workato.

6

Use the Description field to enter an API description.

7

Click Manage permissions.

8

Copy and save the API key for use in Workato.

9

Click Close.

10

Provide the necessary permissions for this API key. Refer to Minimum permissions for Harvest API for more information.

PERMISSIONS

Ensure that you give this API credential the correct permissions. Incorrect permissions may prevent some Greenhouse connector actions and triggers from working, even if the connection is successful.

11

Click Save.

Minimum permissions for Harvest API ​

The Greenhouse connector requires an API key with access to specific Harvest API objects. These permissions ensure all triggers and actions function correctly. For example, the reject application action requires the Applications permission.

Grant the following permissions when you create the Harvest API key for Workato. These permissions support standard connector operations:

  • Applications
  • Candidates
  • Close Reasons
  • Custom Field Options
  • Custom Fields
  • Departments
  • Education
  • Job Openings
  • Job Posts
  • Jobs
  • Offers
  • Offices
  • Rejection Reasons
  • Scheduled Interviews
  • Scorecards
  • Sources
  • Tags
  • Tracking Links
  • Users
    • Get: Retrieve User
    • Get: List Users

You can view and manage the permissions for each API key in the Greenhouse API credential page.

If you encounter 403 Forbidden errors, the API key likely lacks required permissions. Review the API key permissions and ensure all listed objects are selected. Refer to the Greenhouse Harvest API documentation for more information.

Connect to Greenhouse using API key authentication (v1/v2) ​

Complete the following steps to set up an API key authentication connection to Greenhouse in Workato using legacy APIs:

1

Click Create > Connection or press C twice.

2

Search for Greenhouse and select it as your app.

3

Enter a name for your connection in the Connection name field.

4

Use the Location drop-down menu to select the project where you plan to store the connection.

5

Enter the Greenhouse API token in the API key field. Refer to Create an API token for more information.

6

Use the On-Behalf-Of user drop-down menu to select the Greenhouse user for the On-Behalf-Of header. Options include User email and User ID.

7

Enter the email address or user ID associated with this API token in the User email / User ID field.

8

Optional. Enter a value in the Custom domain field. Leave blank to use the default Harvest API host: https://harvest.greenhouse.io. If your organization uses a custom subdomain, such as https://acme.greenhouse.io, enter acme.greenhouse.io.

9

Click Connect.

Last updated: