Note: If you are interested in enabling free job ads through Monster, see the following article: Monster Organic Job Posts
Monster is a global online employment solution for people seeking jobs and the employers who need great people.
Greenhouse Recruiting's integration with Monster allows users to post jobs from Greenhouse Recruiting to Monster via web hook, and to view information in Greenhouse Recruiting for candidates who applied to those jobs posted on Monster. In this article, we will cover how to:
Configure User Setup Permissions in Greenhouse Recruiting
Contact a Greenhouse Recruiting 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 following permissions to your account:
- Can manage ALL organization's API Credentials
- Can manage and configure web hooks
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 and Can manage ALL organization's API Credentials so a check is in each checkbox. When finished, click Save.
In addition to the above developer permission, the user configuring the integration should have a Site Admin permission level, or a Job Admin permission level with the additional user-specific permission Can manage custom fields.
Repeat these steps for all users who should have access to set up the integration.
Create a Harvest API Key for the Greenhouse Recruiting / Monster Integration
To create a Harvest API key for the integration, click 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 Monster.
In the Create New Credential dialog box, make the following selections:
- API Type: Harvest
- Partner: Monster
- Description: Monster Harvest API Key
When finished, click Manage Permissions to generate the Harvest API key and automatically assign it the appropriate permissions required by Monster.
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 Monster 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.
On the subsequent page, confirm the following permissions are assigned to your new API key:
If any of the permissions above are not checked, place a check in the box next to the appropriate permission. Click Save when finished.
Your Harvest API key for the Greenhouse Recruiting / Monster integration is created and configured. Send the key to your Monster onboarding team so they can set up the integration.
Retrieve Monster's Endpoint URL and Secret Key
Before enabling the Greenhouse Recruiting / Monster integration, you will need two pieces of information:
- Monster's Endpoint URL
- Monster's Secret Key
To retrieve this information, share the following details with the Monster Customer Success team:
- Harvest API key created in the previous step
- Greenhouse Recruiting email address
Enable Greenhouse Recruiting / Monster Integration
With Monster's endpoint URL and Secret Key copied and your Greenhouse Recruiting user permissions enabled, you are ready to enable the Greenhouse Recruiting / Monster 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. From this page provide the following details:
- Name: We suggest Monster Integration
- When: Be sure to select the right web hook so the web hook fires at the appropriate event in Greenhouse Recruiting [Job Post Updated]
- Endpoint URL: The Endpoint URL received from the Monster Customer Success team
- Secret Key: The Secret Key received from the Monster Customer Success team
When finished, click Create Web hook.
That is it! Your Greenhouse Recruiting account and Monster account can now talk to each other. These settings dictate execution of the Monster web hook once the end user transitions the candidate into an appropriate application stage for a given job.
Create Custom Job Field
This portion of the configuration allows Greenhouse Recruiting users to configure which jobs should post to Monster.
Click the Configure icon in the upper right-hand corner, then click Custom Options on the left-hand panel.
Under the Company Custom Fields section, click Jobs.
On the Manage Job Fields page, click + Add Field.
Enter the following information in the Create New Job Field dialog box:
- Field: PostJobToMonster
- Description: Determines if the job needs to be posted to Monster
- Type: Yes/No
- Required: Yes
Click Save when you are finished.
If you would like a job to be posted to Monster, when entering the Job Details, select "Yes" for the PostJobToMonster field.
Use Greenhouse Recruiting / Monster Integration
When a candidate applies to a job in Monster, Monster will add the candidate to Greenhouse Recruiting on the appropriate job. Monster will provide the following information about the candidate in Greenhouse Recruiting:
- First name
- Last name
In addition to the above information, the following candidate information will be pushed to Greenhouse Recruiting based on its availability in Monster:
- Phone number
- Cover letter
Note: The Greenhouse Recruiting user whose email address is provided to the Monster Customer Success team (to retrieve the Monster Endpoint URL and Secret Key) will be used in the On-behalf-of header associated with the Harvest API key.