Greenhouse

  • 23 April 2020
  • 0 replies
  • 43 views

Introduction to Greenhouse

Greenhouse Recruiting’s integration with Tonkean allows you to create/disable Greenhouse accounts along with taking all of your traditional actions you’d be able to take within Greenhouse. In this article, we will cover how to: 

  • Configure User Setup Permissions in Greenhouse Recruiting

  • Create a Harvest API Key for the Greenhouse/Tonkean Integration

  • Using Greenhouse actions in Tonkean

Configure User Setup Permissions in Greenhouse Recruiting

In order to enable the Greenhouse/Tonkean integration, you will need the developer permission Can manage ALL organization’s API Credentials

Contact a Greenhouse user in your organization with Site Admin level permissions with the additional user-specific permission Can edit another user's advanced permissions to apply the API credential management permission to your account. Have the user with Site Admin level permissions edit your user account's permissions by navigating to the Configure icon  uFQSLMmXsDgJU44PLAVDZW2pl4W9N0BSBcc1QruXivL-hMt4R9Kr1ApBQ5nA922GlXlRtDVorwvzqJ-W7Qm968bWl5SyZ-pHQlagAtYNCG1Ipyt2H8MDmRFuGcbkW57G-XlsSuko > Users > Your Name)

j3y6Du1YJhoh96FKgRandBx81s7a1MqVCtzh9dWq4RKkpOZ6AW89VGRxCFUjeYQVi_QsA_pWrwegutG7MjDqxQSQllTWN3gIkMI_uE0bkenAC1fEzgXCm6_3gcNdc8baKLoQZYYd

 

The user with Site Admin level permissions should navigate to the Permissions panel on your user page and expand the Developer Permissions dropdown menu. 

Select Can manage ALL organization’s API Credentials so that a check is in the checkbox. When finished, click Save.

oOZyHN0VgDAHq4ZIL2VnrzORzhaEtQXVl__KB6hsSB2U0qzh154ObRgGqQVoiLgwGyRq-p1aZZu468TxuMO9-hm7Li2zc-CFeKN1sMSaZG4au6mJCFn-dk1Fj50RqpyJRdbYA2YD

Repeat as necessary for any other user that should have access to set up the integration.

 

Create a Harvest API Key for the Greenhouse/Tonkean Integration

To create a Harvest API key for the integration, click on the Configure icon Screen_Shot_2018-05-24_at_5.31.51_PM.png in the upper right-hand corner. Navigate to Dev Center on the left-hand panel.

From the Dev Center page, click API Credential Management.

E2qm9b5CQCJS23PDY3JhD5enlXWFaZqMCQB4JmH7vhYDs33IKQTFZ-YWYiSSRJeV1I6zpg4OB50fpXj6-DwD_nOdcbo4VrdigVEB7b4AKYSs9tC4U5pvQRZLXPhi7fgOtdvh6tqk

 

From the API Credential Management page, click Create New API Key to generate the API key for Tonkean.

 

AV-pFRzEnchButctMz3vg4GSOyTvVyJ5phYPJTTfoniKjsqKCmXMrCJCLDCJ5R5bNAifd8J957bZs953oYbCvYBA1L236c9lXlN0sVM0W7fsurelA2aBV_Lcvk5uBx1YM1jerOkk

 

From the Create new credential dialog box, give your API key a name and select Harvest from the Type dropdown menu. When finished, click Create

 

 

On the Manage API Key Permissions page, please ensure that you select all of the entities you want Tonkean to be able to pull data from, and also push updates to. When finished, click Update.

 

Your Harvest API key for the Greenhouse/Tonkean integration is created and configured. Provide your Harvest API key to your Tonkean onboarding team or paste it within the Greenhouse Data Source integration screenshot above and click Connect.
 

How to use the Tonkean Integration with Greenhouse

A great example of how you can utilize Tonkean & Greenhouse is for account provisioning/de-provisioning. An example could be when a user is created in the “Recruiting” Okta Group, you want to automatically create a Greenhouse account for that user.

 

Using the “Create User” action, you simply need to put in the Okta fields of the user (first name, last name, email address).

 

 

It’s important that you are updating/creating data on behalf of a Greenhouse User who has the correct permissions to create accounts. Specifically, you need that user’s unique Greenhouse ID (which can be found on the Users page within Greenhouse, extracting it from the URL of their profile). 

Once you have the ID, simply putting it in the last field “Create On Behalf Of” will complete the process.

Any action that is not native can be done via the Custom Data Source Action. This is more advanced and requires the use of Greenhouse’s API documentation. More information can be found in this article.


This topic has been closed for comments