Setting up the Lever integration
This section covers the process for setting up your Lever Requisitions integration app to begin migrating requisition data between Lever and ChartHop.
Setting up the Lever Requisitions integration app requires the following steps:
- Create a Lever API key
- Install the Lever integration app
- Set up the API connection
- Set up the flow of requisition data
- Set up the flow of new hire data
ATS integrations are typically done with help from ChartHop's professional services. Contact your implementation specialist before beginning these steps.
In order for ChartHop to access your organization's Lever recruiting data, you need to create a Lever API key that you can use with ChartHop. You can work with your Lever Requisitions administrator if you have questions.
To create your API key, follow the steps outlined in the Generating API Credentials in Lever. Use the instructions in the Lever documentation to create your API key and use the following values when doing so.
Field | Value |
---|---|
Key name | ChartHop |
Select a preset | Select all read |
Description | Leave this blank |
After you name your key and enable all of its read permissions, you need to configure the key’s write permissions.
Enable the following write permissions:
- Create requisitions
- Delete requisitions
- Update posting
- Update requisition fields
Once you've created your API key in Lever, you can install the Lever integration app in ChartHop.
To install the Lever Requisitions 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 Lever Requisitions app.
- Select Install.
- Select Install from the app install page.
In order to allow ChartHop to access your Lever data, enter your Lever API credential in the Lever Requisitions API Key field in the Settings section of the app. Then, select Save Settings.
Once you establish your API connection, you can configure the type of requisition data flow that the integration runs.
When setting up your integration, you can choose the primary source of truth when referencing new requisition data. Selecting ChartHop results in an outbound job data flow where ChartHop is the source of truth, whereas, selecting Remote System (Lever Requisitions) results in an inbound job data flow where the ATS is the source of truth.
To select your Lever Requisitions integration’s source of truth:
- From the left sidebar, select Apps & Bundles.
- From the sub-menu, select Apps.
- Select the Installed Apps tab.
- Scroll the list down to the Lever Requisitions app.
- Select the Lever Requisitions app.
- From the ChartHop Lever Requisitions app settings page, scroll down to the Source of Truth section.
- Select one of the two options:
- ChartHop - ChartHop is the source of truth and the integration is configured to run an outbound job data flow.
- Remote System (Lever Requisitions) - Lever is the source of truth and the integration is configured to run an inbound job data flow.
You can configure the Lever Requisitions integration app to handle two types of data migrations (job data flows) between ChartHop and Lever Requisitions. Depending on the type of job data flow you choose, you may enable specific configurations that may either be required or optional and yet, recommended.
These are the required and recommended configurations for each job data flow:
Job data flow type | Configurations |
---|---|
Outbound, ChartHop to Lever | Required
Recommended
|
Inbound, Lever to ChartHop | Required
Recommended
|
To and change the configuration options for your Lever Requisitions integration:
- From the left sidebar, select Apps & Bundles.
- From the sub-menu, select Apps.
- Select the Installed Apps tab.
- Scroll the list down to the Lever Requisitions app.
- Select the Lever Requisitions app.
- From the ChartHop Lever Requisitions app settings page, scroll down to the Other Options section.
- Select from the following configuration options described in the table below.
After you select your integration’s source of truth, you can select additional options to further customize and configure it:
Field | Description |
---|---|
Run Daily | With this option enabled, the ATS app runs automatically every day. 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. |
Sync On Change | Enables the outbound job data data flow direction. When enabled, changes to open jobs are automatically pushed to Lever as soon as they are made in ChartHop. This option cannot be selected when Reverse Sync is enabled. |
Reverse Sync | When enabled, Lever becomes the system of record, and ChartHop is updated with new open roles from Lever when the inbound job data flow runs. This option cannot be selected when Sync On Change is enabled. |
Reconciliation | When enabled, reconciles Lever 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 Lever, a matching req is created in Lever. Reconciliations can either happen on an ad-hoc basis or on a daily basis if the Run daily option is enabled. This option cannot be selected when Reverse Sync is enabled. |
Remote Location As Default | When enabled, newly synced records that are not assigned a location are assigned the value Remote Location. |
You can use the new hire webhook job data flow to automatically bring new hires from Lever to ChartHop when the candidate is marked as “Hired” in Lever, along with their relevant personal information, such as address, phone number, and email.
New hire webhooks will not be processed if the person being hired already exists in ChartHop, even if they aren’t actively in a role. As a result, the integration cannot support:
- Internal transfers
- Re-hires
Only the first new hire webhook for a ChartHop job is supported. For example, if they you update an offer packet and re-hire the candidate in Lever, the updated information will not be processed in ChartHop unless the new hire in ChartHop is removed first.
A new hire webhook will not be processed if the job does not exist in ChartHop.
All new hire webhook job data flows are inbound (Lever to ChartHop).
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 Lever Requisitions app.
- Select the Lever Requisitions app.
- From the ChartHop Lever Requisitions app settings page, copy the secret key value under Webhook Setup.
In Lever:
- Navigate to Integrations and API under Settings.
- Select Webhooks.
- Enable Candidate Hire to on.
- Add the webhook.
- Select Verify Connection.
With the webhook enabled, accepted offers in Lever are pulled into ChartHop, alongside the new hire's start date, and contact information.