The BambooHR integration pulls candidate details from a variety of locations in Lever. Read through our BambooHR field mapping help article which describes how data from various Lever objects can be configured and mapped to maximize how much data is sent to BambooHR.
Lever's enhanced integration with BambooHR supports passage of the following fields:
Enabling the BambooHR integration
||The BambooHR integration must be configured by a Super Admin on your Lever account and a Full Admin user on the BambooHR account. If the BambooHR key is configured by a user other than a full admin, you may not see all Lever data pre-populated in your BambooHR instance.|
Enable the BambooHR integration in Lever
Navigate to Settings > Integrations and API and toggle on the BambooHR integration.
When you toggle on the BambooHR integration, please read through the accompanying integration details, then click the button Send Request to Enable button to notify Lever Technical Support of your request.
Lever will reach out to you requesting the following required information:
- BambooHR API Key - This key should be generated by a full admin user from your BambooHR dashboard (Details below)
Configuring the BambooHR integration
Creating an API Key
||We recommend that you create a non-employee user in your BambooHR instance with Full Admin access to create the API key (such as firstname.lastname@example.org). Although this is not required, doing so will assure that the integration continues to operate successfully in the event that your admin users depart or have access role changes.|
To generate a BambooHR API key:
- Log into BambooHR then click on your account icon in the top right-hand corner of the dashboard menu and select API Keys.
- Next click on the + Add New Key button in the My API Keys window.
- In the API Key Name text box, type "Lever" then click the Generate Key button.
- Click on the Copy Key link and save the API key in a document you can easily access. Once complete, click the Done button. You will provide this API key to Lever as a part of your configuration.
Creating a BambooHR employee profile record from Lever
Once the integration has been configured you can begin sending data from Lever to BambooHR when candidates are hired. The integration will create a new BambooHR employee profile record.
Before hiring the candidate, make sure that all desired fields are filled out on the candidate, requisition, offer and BambooHR New Hire profile form. The more fields present and populated in Lever, the more fields that will be pre-populated in BambooHR.
Hiring a candidate
Once the candidate details have been filled out, you may then archive the candidate as 'Hired' in Lever. At a minimum, First Name, Last Name, and Home Email are required to create a record in BambooHR.
A new employee record will be created in BambooHR.
The associated Job Info, Employment Status and Salary details will also be included in the new BambooHR employee record.
New stories will appear on the candidate profile page in Lever with the BambooHR ID, notifying the opportunity owner that the candidate was transferred over successfully.
What if I don't want to send a candidate profile to BambooHR?
You are able to prevent candidate profiles from being pushed through the integration by applying the tag 'BambooHR New Hire - Skip' to the candidate profile prior to archiving the candidate as 'Hired.'
Resume and offer upload to BambooHR
In addition to triggering off the Hired archive state and passing candidate information the integration has been updated to also:
- Pass resume, if available
- Pass the candidate offer file
Both actions will be completed via the BambooHR API. Inputs required from the client to set up file upload from Lever to BambooHR are as follows:
|Model Emp ID||Integer field. The ID given by the client will be used in getting the metadata for folders. This corresponds to the client's employee ID or number as it appears in BambooHR.|
|Offer Resume Folder Name||If TRUE, the solution will need to know the folder to upload to in the client's system as every BHR instance may vary in the file structure.|
|Offer Letter Folder Name||If TRUE, the solution will need to know the folder to upload to in the client's system as every BHR instance may vary in the file structure.|
Expected notes for file uploads will be created as follows:
@ownerUsername, New Hire successfully transferred and files successfully uploaded to BambooHR.
New Hire: bambooHRNewHireURL
@ownerUsername, New Hire failed to transfer and files failed to upload to BambooHR.
HTTP Status: API_RESPONSE_HTTP_CODE_AND STATUS
Example of success notification:
@lever, New Hire successfully transferred and files successfully uploaded to BambooHR.
Example of failure notification:
@lever, New Hire failed to transfer and files failed to upload to BambooHR.
HTTP Status: 400 Unauthorized
Message: The security token you passed has expired.