Import user data from HR system: BambooHR integration

Keep your employee data in sync and reduce manual work by connecting your BambooHR account with Velory. This integration ensures that key employee details flow seamlessly into Velory, enabling more efficient IT lifecycle management; from onboarding to offboarding.

In the next section, we’ll walk you through how to activate the integration step by step.

How to activate the integration 

1. Sign in as an Admin
2. Go to Settings > Integrations > HR System Sync 

3. Choose BambooHR in the dropdown menu 
4. Follow the steps in the checklist and add Service user ID and Service user token 

5. When this is done, the user synchronization begins 

6. The integration is completed when status is Active and Users are synchronized  

Data fields added from BambooHR 

This is the data Velory can retrieve from BambooHR:

1. id  -> ID of the user in the HR system  
2. username  -> System-assigned username (usually an email)  
3. first_name  -> Employee's first name  
4. last_name  -> Employee's last name  
5. job_title  -> Employee's job title  
6. employee_number  -> Unique identifier for the employee within the organization (used for merging users between Directory and HR systems) 
7. department_name  -> Name of the department the employee belongs to (nullable)  
8. division_name  -> Name of the division the employee belongs to (nullable)  
9. employee_type  -> Type of employment (e.g., full-time, contractor) (nullable)  
10.  cost_center_name  -> Cost center assigned to the employee (nullable)  
11.  state  -> Employment status (e.g., active, inactive)  
12.  employment_start_date  -> Start date of employment (`YYYY-MM-DD`)  
13.  employment_end_date  -> End date of employment (`YYYY-MM-DD`), if applicable (nullable)  
14.  manager_email  -> Email address of the employee’s direct manager  
15.  manager_id  -> Unique ID of the employee’s direct manager (nullable)  
16.  emails  -> List of email addresses associated with the employee  
    1. emails[].type  -> Type of email (`work`, `personal`, etc.)  
    2. emails[].value  -> Email address  
    3. emails[].primary  -> Whether this is the primary email (boolean)  
    4. personal_email  -> Personal email address (nullable)  
17.  phone_numbers  -> List of phone numbers associated with the employee  
    1. phone_numbers[].type  -> Type of phone number (`home`, `mobile`, etc.)  
    2. phone_numbers[].value  -> Phone number  
    3. phone_numbers[].primary  -> Whether this is the primary phone number (boolean)  
18.  groups  -> List of groups the employee is a member of  
    1. groups[].id  -> Unique identifier of the group  
    2. groups[].name  -> Name of the group  
19.  office_location  -> Office location of the employee (nullable)  
20.  building_id  -> ID of the building where the employee is assigned (nullable)  
21.  addresses  -> List of addresses associated with the employee  
    1. addresses[].type  -> Type of address (`home`, `work`, etc.)  
    2. addresses[].street_address  -> Street name and number  
    3. addresses[].locality  -> City name  
    4. addresses[].postal_code  -> ZIP or postal code  
    5. addresses[].country  -> Country name  
    6. addresses[].primary  -> Whether this is the primary address (boolean)
    7. addresses[].raw_address  -> Full unstructured address string  

In addition to the attributes presented above, we can add any attribute available in the Directory or HR system API.

How HR data works together with user data from Active Directory 

If you are connecting both your HR system and your Active Directory, the HR system information will complement the data missing in the Active Directory. Example of such data: Start date employment and end date of employment.