Setting up the Greenhouse integration

this section covers the process of setting up the charthop greenhouse integration app which allows you to migrate your job data between greenhouse and charthop setting up the charthop greenhouse integration app requires the following steps create a greenhouse api key install the greenhouse integration app set up the api connection configure the flow of job data set up the flow of new hire data configure outbound group job openings ats integrations are typically done with help from charthop's professional services contact your implementation specialist before beginning these steps create a greenhouse api key in order for charthop to access your organization's greenhouse recruiting data, you need to create an api key to provide to charthop you use greenhouse to create this api key the user that you use to create the api key must have the can manage all organization’s api credentials permission in developer permissions you can work with your greenhouse administrator if you have questions to create your api key, follow the steps outlined in the https //support greenhouse io/hc/en us/articles/202842799 generate api key for greenhouse recruiting use the greenhouse instructions to create your api key and enter the following values when creating the key field name value api type harvest partner charthop description leave this blank once you create your harvest api key, a set of permissions are applied to the connection by default leave all options as their default settings install the greenhouse integration app once you've created your api key, you can install the greenhouse integration app to install the greenhouse integration app from the left sidebar, select apps & bundles from the sub menu, select apps select the availible apps tab scroll the list down to the greenhouse app select install select install from the app install page set up the api connection to allow charthop to access your greenhouse data, enter your greenhouse api credentials in the proper fields in the connection section of the settings tab of the app using the following fields, add both your greenhouse domain and harvest api key field description greenhouse subdomain the subdomain used by your greenhouse instance for example, if your domain is called myorg greenhouse io, then your subdomain would be “myorg” harvest api key the harvest api key generated in greenhouse configure the flow of job data once you establish your api connection, you can configure the type of job data flow that the integration runs select your sync direction & source of truth when setting up your integration, you can choose the primary source of truth when referencing new job data an outbound job data flow sets charthop as the source of truth, whereas, an inbound job data flow sets greenhouse as the source of truth to select your greenhouse integration’s sync direction from the left sidebar, select apps & bundles from the sub menu, select apps select the installed apps tab scroll the list down to the greenhouse app select the greenhouse app from the charthop greenhouse app settings page, scroll down to the basic settings section select one of the two options outbound charthop as source of truth active open jobs in charthop will be pushed to greenhouse inbound greenhouse as source of truth active jobs in greenhouse will be imported from to charthop configure the greenhouse integration depending on the type of job data flow you choose, you may enable specific configurations to match your desired setup basic settings setting what it does notes run daily when turned on, it will syncs data every morning when enabled, regardless of data direction, job related candidate metrics are pulled on a daily basis every morning for customers on the inbound job data flow direction, this also causes the inbound job data flow to run on a daily basis every morning when turned off, syncs will only run manually or based on events depending on other settings recommended for most setups sync on change syncs immediately when a change to a linked open job is made or a new job becomes active only availible for outbound syncs reconciliation reconciliation when enabled, reconciles greenhouse role and field data with charthop, treating charthop as the source of truth for example, if an open job exists in charthop but not in greenhouse, a matching req is created in greenhouse reconciliations can either happen on an ad hoc basis or on a daily basis if the run daily option is enabled only availible for outbound syncs default location if not provided when set to remote, newly synced records that are not assigned a location are assigned the value "remote" for their location job matching job matching settings allow you to configure how charthop jobs are automatically matched to greenhouse jobs and vice versa field what it does match by job codes first when enabled, it matches charthop jobs with existing greenhouse jobs via the requisition id in greenhouse (if the requisition id matches the charthop job code) if no match is found via requisition id (greenhouse) and job code (charthop), then the integration continues to attempt to match based on the chosen “group job openings” option group job openings the fallback method for matching on a job is title title and location none — only matched on job codes title matching advanced settings two options that are used for specific title matching formatting options if it matches to a closed job, what should happen? the logic for matching for closed jobs re open job and create new opening create new job and opening set up the flow of new hire data you can use the new hire webhook job data flow to bring new hires from greenhouse to charthop when the candidate is marked as “hired” in greenhouse, along with their relevant personal information, such as address, phone number, and email new hire webhooks are not processed if the person being hired already exists in charthop, even if they aren’t actively in a role this means that we cannot support (via new hire webhooks) internal transfers re hires only the first new hire webhook for a job in charthop is supported for example, if you update an offer packet and rehire the candidate in greenhouse, the updated information are not processed in charthop unless the new hire in charthop is removed first a new hire webhook is not processed if the job does not exist in charthop all new hire webhook job data flows are inbound (greenhouse to charthop) copy your generated secret key to enable your web hook in greenhouse to configure the new hire webhook job data flow, follow the steps below in charthop from the left sidebar, select apps & bundles from the sub menu, select apps select the installed apps tab scroll the list down to the greenhouse app select the greenhouse app from the charthop greenhouse app settings page, copy the secret key value under new hire webhook in greenhouse follow the instructions in greenhouse to https //support greenhouse io/hc/en us/articles/360005574531 enable a web hook enter the required information using the table below field value name this webhook charthop hire when candidate has been hired endpoint url https //webhook charthop com/v1/webhook/app/greenhouse/5a12dddd6f2b8f0e63fc8e64/5b15fbf1bd35a93451fc5df3 secret key \[obtained above] error recipient email disabled no save the web hook when you are done