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
- Configure User Setup Permissions in Greenhouse Recruiting
- Enable Greenhouse/Resource.io Integration
- Next Steps
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 > 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 and configure web hooks 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.
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 in the upper right-hand corner and navigate to Dev Center on the left-hand panel.
From the Dev Center page, click Web Hooks. Click Web Hooks from the subsequent page.
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.
When finished, click Create Web hook.
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:
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 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 [COMPANY NAME].
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, select the permissions in the screenshot below:
When finished, click Update. Your Harvest API key for the Greenhouse/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
- 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 email@example.com and they’ll make sure you’re fully set up and properly connected.