Finding the best talent is the key to any successful organization, but it doesn’t stop at hiring – it’s just as important to support new hires, empower them to be productive and successful in their new role.
By leveraging Kallidus Sapling, you can provide significant improvements to your People Operations team and Hiring Managers, while completely streamlining the Candidate and Employee experience through the Lever integration.
The Lever integration is currently only available to customers on Lever’s Professional or Enterprise plan (see plan details here).
This article covers the following topics:
- Overview of Lever
- How It Works
- Setting up the Integration and Data Flow - Video
- Setting up the Integration Step-by-Step Instructions
- Step #1. Confirm Company Settings in Lever
- Step #2. Enable the Sapling Integration in Lever
- Step #3. Setup the Webhook in Lever
- Step #4. Copy the Signature Token from Lever into Sapling
- Step #5. Enable the Lever Integration in Sapling
- Step #6. Configure the fields you want to be mapped from Lever to Sapling
- Integration Fields
- Key Factors to be aware of
- 💡 Looking to do more?
Overview of Lever
Lever provides the best-rated recruiting software, applicant tracking system (ATS), and recruitment marketing tools used by top businesses.
How It Works
Setting Up the Integration
Data Flow Overview
Setting up the Integration Step-by-Step
Step #1. Confirm your Company Settings in Lever
Navigate to Settings → Company
Ensure your Departments/Teams, Locations, and Work Types in Lever match your Departments, Locations, and Employment Statuses in Sapling respectively
Step #2. Enable the Sapling Integration in Lever
Navigate to Settings → Integrations and API
Locate HRIS and Onboarding → Toggle on the Sapling integration slider
- Scroll down and click "Generate new key" → Click "Copy" and then "Done"
Save this newly-generated API key somewhere as you'll need for Step 4 below
Step #3. Setup the Webhook in Lever
Navigate to Settings → Integrations and API → Webhooks
Toggle on the "Candidate hired"’ slider and click "Add webhook"
Copy and paste the webhook address below into the Lever webhook address field:
- Change the "domain" in the webhook URL above to your own Sapling domain
- Your Sapling domain is the first part of your Sapling URL
- Copy the signature token from your Lever webhook and save it somewhere as you'll need it for Step 4 below
Step #4. Enable the Lever Integration in Sapling
Navigate to the Integrations → Applicant Tracking System → Lever
Input the API key and signature token retrieved from Lever
- Click "Next"
Step #5. Configure the fields you want to map from Lever to Sapling
There are 5 standard fields that can be mapped from Lever to Sapling when enabling the integration:
Select the appropriate Lever field from the dropdown, or select "None". For more details, please review the Integration Fields section of this article.
- Click "Next" and "Activate" to complete the integration setup
Kallidus is continually expanding the number of fields that sync between Lever and Sapling.
- Here is a full list of the Lever to Sapling integration fields and their setup details
For Sapling to create new Pending Hire profiles, the following fields are required at minimum - and they are all synced from the Lever candidate profile by default:
- First Name
- Last Name
- Personal Email
During the integration setup, you will have the option to map the following standard fields:
- Job Title
- Start Date
In addition to the 5 standard fields above, you also have the option to map additional custom fields from Lever Offers and Requisitions. When doing so, please ensure your field names, types, and values match between Lever and Sapling. For custom Offer fields, we will automatically map Lever Offer fields to Sapling fields with matching names - no action is required on your end. For custom Requisition fields, you will need to map corresponding fields under Sapling's Profile Setup:
Please note that Sapling's native Pay Rate, Pay Frequency, and Rate Type fields are not supported at this time. To sync compensation data from Lever to Sapling, you'll need to create the following custom fields under Sapling's Profile Setup - the field mapping guide linked above has more details:
- Offered compensation amount
- Type of earnings
Key factors to be aware of
Field Names, Types, and Values in Lever and Sapling
For the fields to sync correctly, ensure you match the field names, field types, and values between Lever and Sapling.
- For example: If you're selecting "Option A" from a dropdown field in Lever, you'll need to ensure "Option A" is a value available in the corresponding Sapling field in order for the field to sync.
- As a guide for matching your Lever and Sapling field types, please see below:
|Lever field type||Sapling field type||Notes|
|Currency||Currency||When using only a single currency in Lever|
|Currency||Number||When using multiple currencies in Lever|
|Dropdown||Multiple choice question|
|Text (single line)||Short/long text||Long text is ideal to avoid max character limit|
|Textarea||Short/long text||Long text is ideal to avoid max character limit|
Multiple Instance Management
You can have leveraged multiple Lever instances that can send candidate data to Sapling.
This can be configured directly under the integration page in Sapling.
There are two options for resending a candidate from Lever to Sapling:
Option 1: In Lever, unhire and rehire the candidate.
Option 2: In Lever, go to Settings > Integrations > Webhooks > Scroll down to Recent Webhook Deliveries. Then locate the correct webhook for that candidate and click on 'rerun'. This will resend the candidate to Sapling.
Managing Internal Movements and Rehiring
This integration supports rehiring and internal movements without issue. Even if a user already has an active/inactive profile in Sapling, the integration will still create a new Pending Hire profile for internal movers/rehires as long as their new Start Date comes after their previous Start Date. In these cases, you will see the "resolve duplicate" warning on the Pending Hire dashboard.
Confidential Postings, Opportunities, or Requisitions Management
Lever's setup article on API credentials states as follows:
"By default, information associated with confidential postings, opportunities, or requisitions will be excluded from the access granted by the Lever API credential. If you wish for the generated API key to grant access to confidential information in your Lever environment, move the 'Allow access to confidential data' toggle to the on position."