PieSync allows your organization to sync contacts and share data across your favorite marketing, CRM, invoicing, and e-commerce applications using their intelligent two-way technology. Greenhouse Recruiting's integration with Piesync's allows your organization to use PieSync's powerful If/Then statements to sync information across the two systems. In this article, we will cover:
Configure User Setup Permissions in Greenhouse Recruiting
In order to enable the Greenhouse/PieSync 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 > Users > Your Name.
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.
Repeat as necessary for any other user that should have access to set up the integration.
Create a Harvest API Key for the Greenhouse/PieSync Integration
To create a Harvest API key for the integration, click on the Configure icon in the upper right-hand corner. Navigate to Dev Center on the left-hand panel.
From the Dev Center page, click API Credential Management.
From the API Credential Management page, click Create New API Key to generate the API key for PieSync.
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, give the API key the following list of permissions:
- POST: Add Candidate
- PATCH: Edit Candidate
- GET: List Candidates
- GET: Retrieve Candidate
- Custom Fields
- GET: Get Custom Fields
- GET: List Jobs
- GET: List Sources
- GET: List Users
Note: The above permissions are the minimum permissions needed for the integration.
When finished, click Update.
Your Harvest API key for the Greenhouse/PieSync integration is created and configured. Navigate to your newly created API key and click Copy.
Enable Greenhouse/PieSync Integration
With your Greenhouse Harvest API key copied, navigate to the Greenhouse Integration page on your PieSync account. In the dialog box to enable the integration, input the following in the appropriate fields:
- Email Address (which you use to log into Greenhouse Recruiting)
- Greenhouse Harvest API Key
Click Next when finished, and follow any subsequent steps to finish enabling the integration.
[IF] Supported Conditions/Filters
Once the integration is enabled, your organization can use the following fields for the IF statement in PieSync:
- Do Not Email…
- has Job Applications
- has Resume
- has applied for Job…
- is a Prospect (has no Job Applications)
- Created At…
- Current Company…
- Current Stage of Last Active Application…
- Current Title…
- First Name…
- Jobs Applied For…
- Last Activity…
- Last Applied On…
- Last Name…
- Updated At…
- has no Resume
- has not applied for Job…
- Custom fields...
- Already existing in other application
[THEN] Supported Actions
Once the integration is enabled, your organization can use the following fields for the THEN statement in PieSync:
- add Tag
- remove Tag
- update Coordinator…
- update Recruiter…
- update Current Company…
- update Current Title…
- update First Name…
- update Last Name…
- update Private…
- update Custom Fields
Default Field Mapping
Depending on the other app you are syncing with, you will see a number of standard Greenhouse fields being mapped by default. For instance, in a connection with Google Contacts, the default field mapping looks like this:
Note: PieSync syncs the default name field(s) that come with the apps. Sometimes they have a different structure in both apps you connect (e.g. first and last names are separate in app A and joint in a single field in app B). In the background, PieSync joins first and last names together from app A to B and separates them again from app B to A. Our algorithm is smart about which part it updates in app B.
Customizable Field Mapping
You can custom map your Greenhouse Custom Fields and any additional standard fields that are not included in the default mapping yet. Bear in mind a mapping between two fields can only exist if the types of fields are compatible, and the particular compatibility will determine the direction of the mapping as well. More information on Customizable Field Mapping here.
Currently, there are no Greenhouse integrations on the PieSync platform that support our deletions sync.
Create Greenhouse Candidates
Candidates are intended to be created in Greenhouse through job applications and therefore PieSync won't create any new candidates. This setting cannot be disabled. Existing contacts can be updated at any time.
Syncing Email Preference
You have the ability to sync back the Email Preferences. An easy way to do this would be by setting up a direct mapping from the Do Not Contact field into a custom text field over in your other app. Here, the field on the right is a custom text field which will populate with a simple text label "True/False".
Another option is to use this value to trigger workflows. However, you can also have PieSync directly change certain attributes based on what is happening inside of Greenhouse. This would require setting up specific filters or actions from the PieSync Rules like so:
Another option is to use this value it into trigger workflows. However, you can also have PieSync directly change certain attributes based on what is happening inside of Greenhouse. This would require setting up specific filters or actions from the PieSync Rules like so:
Note: The availability to Sync Unsubscribes/Deletions is app and connection dependent. If the box (screenshots above) is not there to tick, it is simply not possible. PieSync needs to be able to detect unsubscribes/deletions on one side and at the same time be able to add the tag 'PieSync Unsubscribes' or ‘PieSync Trash’ on the other side.