Workato is an enterprise automation platform that enables organizations to integrate their apps and automate business workflows without writing code. Workato connects hundreds of applications—including HR, finance, IT, and CRM systems—through a library of pre-built connectors, allowing teams to build powerful, event-driven workflows in a low-code environment.
Workato’s integration with Greenhouse enables users to connect Greenhouse Recruiting to their broader HR tech stack—syncing candidate data, automating onboarding workflows, and triggering downstream actions in systems such as SAP SuccessFactors, ServiceNow, Workday, Slack, and more. The connector supports real-time event-driven automation using Greenhouse’s Harvest v3 API (OAuth 2.0).
Configure Workato’s Greenhouse connector integration
Workato connects to Greenhouse using OAuth 2.0 authorization code grant (Harvest v3 API). This is the default and only supported method for new connections. All new connections authenticate via OAuth 2.0 and use v3 actions and triggers exclusively.
Complete the following steps to create a new Greenhouse connection in Workato:
- Open Connections in Workato: In your Workato workspace, go to Assets > Connections, then click Create > Connection.
- Search for and select Greenhouse: In the connection search, type “Greenhouse” and select it from the results.
- Name your connection: Enter a descriptive name in the Connection name field (for example, “Greenhouse – Production”). This name identifies the connection across recipes in your workspace.
- Select a project location: Use the Location drop-down to select the project folder where this connection will be stored.
- Configure OAuth scopes (optional): Optionally, select the Harvest OAuth scopes required for your use case. If left blank, Workato uses a default set of scopes that covers standard connector operations.
- Select environment: Choose Production or Sandbox from the Environment drop-down to connect to the appropriate Greenhouse instance.
- Click Connect and authorize: Click Connect. You will be redirected to Greenhouse to sign in and authorize Workato’s access to your account. Once authorized, the connection is established and ready for use.
Connection field reference
| Field | Description |
|---|---|
| Connection name | A unique label for this Greenhouse connection. Used to identify it in recipes and the connections list. |
| Location | The Workato project folder where this connection will be stored. |
| Harvest OAuth scopes | Optional. Select the Harvest API scopes to authorize. Defaults to standard scopes if left blank. |
| Environment | Select Production or Sandbox to target the appropriate Greenhouse instance. |
Use Workato’s Greenhouse connector integration
Workato has many automation workflows available to use once the integration has been enabled. To view the different connectors that are available and how to use them, check Workato's Connector guide here.
Common use case: Sync new Greenhouse hires to an HRIS
This example shows how to automatically sync a newly hired candidate from Greenhouse to an HRIS such as SAP SuccessFactors or Workday.
- In your Workato workspace, click Create > Recipe.
- Give the recipe a descriptive name (for example, “Greenhouse → New Hire Sync”).
- Select the Greenhouse app as the trigger app and choose the New/updated object (v3) trigger.
- In the trigger configuration, select Applications as the object type and set a Status filter of Hired.
- Add an action step using your HRIS connector (for example, Create employee in SAP SuccessFactors).
- Map fields from the Greenhouse trigger output to the HRIS action inputs—such as First name, Last name, Email, Job title, and Start date.
- Click Test recipe to validate the setup with a test event.
- Start the recipe to activate it.
Triggers and actions reference
All triggers and actions listed below are v3 (Harvest v3 API) and require an OAuth 2.0 connection.
Triggers
New object (v3)
Fires when a new record is created in Greenhouse. Uses cursor-based polling.
| Input field | Description |
|---|---|
| Object | Select the object type to monitor: Candidates, Applications, or Interviews. |
| Trigger poll interval | How frequently to check for new events. |
| When first started, pick up events from | Specify the start date/time for the initial event fetch. |
New/updated object (v3) – batch trigger
Fires when a record is created or updated in Greenhouse. Returns records in batches.
| Input field | Description |
|---|---|
| Object | Select the object type: Candidates, Applications, Job posts, Jobs, Offers, Interviews, or Scorecards. |
| When first started, pick up events from | Start timestamp for the initial fetch. |
| Batch size | Maximum number of records to return per trigger event. |
Actions
Create object (v3)
Creates a new record in Greenhouse. Input fields are dynamically generated based on the selected object.
Supported objects: Candidate, Candidate note, Candidate education, Candidate employment, Candidate application, Job, User.
Update object (v3)
Updates an existing record. Requires the object type and record ID. Only provided fields are updated.
Supported objects: Candidate, Candidate application, Job, User.
Search objects (v3)
Retrieves records from a Greenhouse endpoint. Returns paginated results. Supports filtering by IDs, date ranges, and object-specific parameters.
| Input field | Description |
|---|---|
| Endpoint | Select the object type to search (for example, Applications, Candidates, Jobs, Offers, Scorecards, Users). |
| IDs | Comma-separated list of IDs to filter results. |
| Cursor | Pagination cursor for retrieving the next page. |
| Page size | Number of results per page. |
Create attachment (v3)
Uploads a file attachment to a specific application.
| Input field | Description |
|---|---|
| Application ID | ID of the application to attach the file to. |
| Filename | Name of the file, including extension. |
| Attachment type | Type of attachment to create. |
| File content | Raw file content (Base64-encoded). Use this or File URL. |
| File URL | URL of the file. Use this or File content. |
| Visibility | Visibility setting for the attachment. |
Move application (v3)
Moves an application to a different stage within the same job, or transfers it to another job. Replaces the v1 Advance application action and supports a broader range of transitions.
| Input field | Description |
|---|---|
| Application ID | ID of the application to move. |
| From stage ID | Current stage ID of the application. |
| To stage ID | Destination stage ID within the same job. |
| To job ID | Destination job ID when transferring to a different job. |
| Email from user ID | User ID for the sender of the move notification email. |
Reject application (v3)
Rejects an application and optionally sends a rejection email.
| Input field | Description |
|---|---|
| Application ID | ID of the application to reject. |
| Rejection reason ID | Reason for rejecting the application. |
| Notes | Internal notes explaining the rejection. |
| Send email at | Date/time to send the rejection email. |
| Email template ID | Email template to use for the rejection email. |
| Email from user ID | User ID for the sender of the rejection email. |
Mark candidate as hired (v3)
Marks an application as hired and optionally assigns a start date, opening, and close reason.
| Input field | Description |
|---|---|
| Application ID | ID of the application to mark as hired. |
| Start date | Candidate's start date. |
| Opening ID | Opening to associate with the hire. |
| Close reason ID | Close reason for the hire. |
The documentation here includes detailed migration guide along with the object coverage guide with the full object coverage with a detailed v1 v/s v3 capability comparison.
Additional resources
For additional information or assistance, contact Workato Support at support.workato.com or reach out to your Customer Success Manager.
Common errors
Recipe stops working after August 30, 2026
- Cause: Recipes using v1/v2 connections (API key authentication) will stop functioning when Greenhouse removes v1/v2 API support.
- Fix: Migrate all recipes to use a v3 (OAuth 2.0) connection before August 15, 2026. Refer to the Workato Greenhouse v3 migration guide for step-by-step instructions.
v3 action not available in recipe
- Cause: The connection is using API key authentication (v1/v2). v3 actions require an OAuth 2.0 connection.
- Fix: Create a new Greenhouse connection using OAuth 2.0. Update recipes to use the new connection and replace v1 actions with their v3 equivalents.
Common questions
Can I automatically migrate my existing recipes to v3?
No. silent or automatic migration is not supported. When switching to a v3 connection, you must manually update all triggers and actions in each recipe. Existing API key connections will continue to function until August 30, 2026.
Can I use both v1/v2 and v3 actions in the same connection?
No. v3 actions require an OAuth 2.0 Authorization code grant connection, and v1/v2 actions require an API key connection. You cannot mix action versions on a single connection.
Can I upgrade an existing v1/v2 connection to v3?
No. Existing connections cannot be upgraded in place. You must create a new Greenhouse connection using OAuth 2.0 authorization, then update your recipes to use the new connection.
What happens to my recipes if I miss the August 30, 2026 deadline?
All recipes using v1/v2 connections will stop functioning when Greenhouse removes API support on August 30, 2026. Workato recommends completing migration by August 15, 2026 to allow buffer time for testing.
There is no direct equivalent for Get object by ID in v3. How should I migrate it?
Use the Search objects (v3) action and provide a comma-separated list of IDs in the IDs input field. This retrieves the same records as the v1 Get object by ID action.