BambooHR Integration Overview – Kantata Knowledge Base

INFO

Our new BambooHR integration is available through Kantata Connect, our newest integration and workflow platform that is currently in the first phase of its release. During this time, all available workflows are prebuilt—or migrated over from M-Bridge Workflows—for you by our team. If you want to create a new customized workflow, you will need to contact Customer Success.

As Kantata Connect develops over the next few months, you will be able to create custom workflows on your own from within the Connect platform. Please check our Upcoming Releases article for more information on when this functionality and new integrations will become available.

Overview

The new BambooHR integration with Kantata Connect syncs data between your BambooHR and Kantata OX accounts. With this integration, you can access workflows that enhance your Kantata OX processes and help you manage your employees, reports and analytics, and more.

As account members (Kantata OX) and employees (BambooHR) are added or removed, Kantata Connect automatically syncs that information so you’re always using the most up-to-date information in your recipes.

To learn more about Kantata Connect, see the Kantata Connect Overview article.

Note: The Kantata Connect platform uses phrases and titles that are similar to Kantata OX components, but it’s important to note that they serve different functions. For example, a Task and Project in Kantata Connect are different from a Task and Project in Kantata OX.

BambooHR Recipes

There are two recipes available for the new BambooHR Integration:

Both recipes use the BambooHR: Employee User Mappings lookup table to pair a BambooHR employee to their matching Kantata OX user. The table automatically updates as new users are added in both BambooHR and Kantata OX.

BambooHR Employees to Kantata OX Users

The BambooHR: Employees to Kantata OX Users recipe syncs employee data from BambooHR to Kantata OX.

Note: Kantata OX account members must be active in order for this recipe to sync properly.

BambooHR Time Off to Kantata OX Time Off Entries

The BambooHR Time Off to Kantata OX Time Off Entries recipe is responsible for syncing time off data from Bamboo HR to Kantata OX.

This recipe runs on a set schedule and fetches all time off entries in your BambooHR account from today to approximately two years in the future. Any time off entries that fall outside of this timeframe will not sync.

Note: Kantata OX account members must be active and all BambooHR time off entries must first be approved in order for this recipe to sync properly.

Lookup Tables

A Lookup table—also known as a mapping table—allows you to map integration data in Kantata Connect. Lookup tables are used to pair different points or sets of data between two systems. For example, if users in System A have different names from users in System B, the lookup table will link System A users' data to the specified users in System B.

When BambooHR is enabled, the following tables are prebuilt for you:

Note: It’s recommended to use a one-to-one mapping system where you map one employee to just one user to ensure the data will sync more accurately between BambooHR and Kantata OX.

Employee User Mappings Lookup Table

The Employee User Mapping table is used to match a BambooHR employee to a Kantata OX account member.

This table contains three columns:

BambooHR Employee ID—The system-generated ID for the BambooHR Employee.
Kantata OX User ID—The system-generated ID for the matching Kantata OX user.
Status—The status—Active or Inactive—of the Kantata OX user.

User Custom Field Mappings Lookup Table

The User Custom Field Mapping table is used to match a BambooHR employee to a user custom field in Kantata OX.

This table contains two columns:

BambooHR Employee Field Name—This column is prepopulated with the names of all BambooHR Employee standard fields. Custom fields may be added if needed.
Kantata OX User Custom Field ID—The system-generated ID for the Kantata OX user level custom field.