Greenhouse

Greenhouse (opens new window) is an applicant tracking system and recruiting software that is designed to help make companies great at hiring and hire for what's next.

Workato's 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.

API version

The Greenhouse connector supports both legacy (v1/v2) and v3 APIs:

• API key authentication uses v1/v2 APIs
• OAuth 2.0 authorization uses v3 APIs

MIGRATION REQUIRED

If your connections use API key authentication (v1/v2), migrate to OAuth 2.0 authorization 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.

New Greenhouse connections support OAuth 2.0 authorization only. API key authentication isn't available for new connections.

Existing connections that use API key authentication continue to run until August 30, 2026.

Connection setup

Greenhouse supports two authentication methods:

• OAuth 2.0 authorization code (v3)
• API key (v1/v2)

Connections that use API key authentication support v1/v2 actions only. Connections that use OAuth 2.0 support v3 actions only.

New Greenhouse connections support OAuth 2.0 authorization 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 (v3)

Use OAuth 2.0 authorization to connect to Greenhouse using v3 APIs. This is the default authentication method for all new connections.

Connect to Greenhouse using OAuth 2.0 authorization

Complete the following steps to connect to Greenhouse:

1

Click Create > Connection.

2

Search for Greenhouse and select it as your app.

3

Enter a name in the Connection name field.

Authentication 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. Workato uses a default set of scopes if left blank.

6

Select the Environment (production or sandbox).

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

Create an API token

We recommended 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.

1

Navigate to Settings > Dev Center > API Credential Management.

Greenhouse API credentials

2

Select Harvest to create a new API key for Workato.

Create an API credential for Workato

3

Provide the necessary permissions for this API key.

Select API credential permissions

PERMISSIONS

Ensure that you give this API credential the necessary permissions. If permissions are not configure correctly, certain Greenhouse connector actions and triggers may not work as intended even if the connection is successful. Refer to required permissions for more information.

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 API Credential Management page.

Manage API credential permissions

403 Forbidden errors occur when the API key lacks required permissions. Review the API key's permissions and ensure all listed objects are selected. Refer to the Greenhouse Harvest API documentation (opens new window) for more information.

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

Use API key authentication to connect to Greenhouse using legacy APIs.

Authentication using API token credentials

Connection field	Description
Connection name	Provide a unique name that identifies which Greenhouse instance it is connected to.
API key	The API token credential. Learn how to create an API key below.
User email	The user email this API token is generated from.
Environment	Use the drop-down menu to select a default domain (sandbox or production) or to provide a custom domain. If you leave this field blank, it defaults to production.