Resource.io

Resource.io enables your organization to improve your response rates and master outbound recruiting. Greenhouse Recruiting's integration with Resource.io allows your organization to automatically push candidates from Greenhouse Recruiting into Resource.io. 

In this article, we will review the steps necessary to enable an integration between Greenhouse Recruiting and Resource.io. 

 

Retrieve Resource.io’s Endpoint URL and Secret Key

Before enabling the Greenhouse/Resource.io integration, Greenhouse Recruiting will need two pieces of information: 

  • Resource.io’s Endpoint URL
  • Resource.io’s Secret Key

To retrieve this information, navigate to Settings in Resource.io and click Connect Webhooks.

Copy down the Endpoint URL and Secret Key. 

 

Configure User Setup Permissions in Greenhouse Recruiting

After you have received your endpoint URL and Secret Key from [COMPANY NAME], 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.

Have the user with Site Admin level permissions edit your user account's permissions by navigating to the Configure icon configure.png > Users > Your Name).

1.png

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 and configure web hooks so that a check is in the checkbox. When finished, click Save.

 2.png

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

 

Enable Greenhouse/Resource.io Integration 

With Resource.io’s endpoint URL and Secret Key copied, and your Greenhouse user permissions enabled, you are ready to enable the Greenhouse/Resource.io integration.

To enable the integration, click the Configure icon configure.png in the upper right-hand corner and navigate to Dev Center on the left-hand panel.

3.png

From the Dev Center page, click Web Hooks. Click Web Hooks from the subsequent page.

4.png

You will be directed to a new page where you Create a New Web Hook. Provide the following details using information retrieved from Resource.io's Settings page.

  • Name
  • When
  • Endpoint URL
  • Secret Key 
 

When finished, click Create Web hook.

 5.png

That's it! Your Greenhouse account and Resource.io account can now talk to each other. These settings dictate execution of the Resource.io web hook once the end user transitions the candidate into an appropriate application stage for a given job.

Web hooks will update candidate data in Resource.io so you know you have the most up-to-date state for each person when you build a segment to communicate with.

 

Create Harvest API key for the Greenhouse Recruiting / Resource.io integration

This grants Resource access to update and see candidates currently contained within Greenhouse. While we continue to iterate on the Harvest API's powerful ability to keep both systems in sync, at this time we use the following endpoints/permissions:

To create a Harvest API key for the integration, click the Configure icon Configure.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.

1._Dev_Center_-_API_Credential_Management.png

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

2._Create_new_API_key.png

In the Create New Credential dialog box, make the following selections:

  • API Type: Harvest
  • Partner: Resource.io
  • Description: Resource.io Harvest API Key

When finished, click Manage Permissions to generate the Harvest API key and automatically assign it the appropriate permissions required by Resource.io.

mceclip0.png

In the subsequent dialog box, click Copy to save your API key to your clipboard. Store the API key in a secure location to provide to Resource.io in the next step. Click I have stored the API Key once you have copied and saved the key.

Note: You cannot access the full API key again after clicking I have stored the API Key. If you lose your API key and need to access it later, you must create a new API key, provide it to the integration partner, and then revoke access to the original key.

3._API_key_created.png

On the subsequent page, confirm the following permissions are assigned to your new API key:

Activity Feed: 

  • GET: Retrieve Activity Feed
mceclip3.png

Candidates:

  • DELETE: Delete Candidate
  • GET: Retrieve Candidate
  • GET: List Candidates
  • PATCH: Edit Candidate
  • POST: Add Candidate
  • POST: Add Note
  • POST: Add Attachment
  • POST: Add Application
  • POST: Add Prospect
  • PUT: Anonymize Candidate
  • PUT: Merge two candidates
mceclip0.png

Sources:

  • GET: List Sources
mceclip2.png

Users:

  • GET: List Users
mceclip1.png

Tags:

  • DELETE: Remove tag from candidate
  • GET: List tags applied to candidate
  • GET: List Candidate Tags
  • PUT: Add a candidate tag
  • POST: Add New Candidate Tags
  • DELETE: Remove Candidate Tags
mceclip1.png

If any of the permissions above are not checked, place a check in the box next to the appropriate permission. Click Save when finished. 

When finished, click Update. Your Harvest API key for the Greenhouse Recruiting / Resource.io integration is created and configured. Provide your Harvest API key to your Resource.io onboarding team so they can set up the integration.

This sync has numerous benefits, including preventing duplicate sourcing and informing your team if a Linkedin, Github or AngelList profile exists in Greenhouse or Resource currently. You also gain the powerful ability to build re-engagement campaigns from prior job search candidates via Resource's Network Tab

 

Using the Integration

Screen_Shot_2020-02-07_at_9.27.29_AM.png

  • Default Sync User - Greenhouse's API requires us to log actions under a user who is present in both systems
  • Maildrop Email -  This allows Resource to send over mail thread activity to Greenhouse profiles. You can follow the link here to confirm what your maildrop address is for your specific Greenhouse account.
  • This part of our sync ensures that campaign emails sent to candidates are tracked within the activity section of their Greenhouse profile as well as in Resource.
  • Greenhouse SSO Domain - Greenhouse hosts your company account on a specific server, which can start with app.greenhouse.com or in rarer cases company.greenhouse.com or app2.greenhouse.com. To find yours, simply sign in to Greenhouse normally and look at the URL prefix in your browser's address bar.

For any questions about your set up and configuration, contact support@resource.io and they’ll make sure you’re fully set up and properly connected.