Integrating BambooHR and Bridge

Document created by Ike Bennion Employee on Jun 8, 2016Last modified by Ike Bennion Employee on Jul 29, 2016
Version 7Show Document
  • View in full screen mode


BambooHR is a notable human resource information system (HRIS) that Bridge has built an integration for. This document describes the integration and the steps for a client to configure.




The current version of the integration only entails a one-way push of data from BambooHR to Bridge. The process entails uploading an initial baseline set of data and setting up a Bamboo-side webhook that listens for updates for specific fields. Bamboo then pushes those updates to Bridge on a scheduled timeframe that the client can define. This push of data will create a new user, update a user and delete a user in Bridge when those actions are taken in BambooHR. Changes are "pooled" and then pushed according to the timeframe selected by the client.


The process entails three parts, determining fields to map, setting up the webhook and providing the necessary token to the Bridge team to then complete the configuration process with a file that is uploaded into the backend of the client Bridge account.



    • Admin access to BambooHR
    • Webhooks need to be enabled for the BambooHR account. This can be done by contacting BambooHR support.
    • A list of the fields you would like to bring from BambooHR into Bridge (listed in a field mapping document to share with your implementation consultant).
    • A URL provided by your implementation consultant for where the webhook payload should be sent.
    • A CSV that contains all of the data intended for the integration exported from BambooHR.




Field Mapping

    1. Download or acquire from your implementation consultant the field mapping document.
    2. List your BambooHR domain in cell B1 of the mapping document.
    3. List the BambooHR fields that you would like to send from Bamboo to Bridge in column A (highlighted).
    4. Select one of the BambooHR fields to serve as the unique identifier in Bridge. Note that field in column C. Note that this field will also be the value users will use to log on if using Bridge authentication, or if you are using Single Sign On, this will be the field that Bridge matches up to the assertion passed by your SSO service to log in a user.
    5. If the field should be titled something differently in Bridge than in Bamboo, denote the new title in Bridge in column B.
    6. Rename the file replacing "CLIENT" with your company name in the file name.
    7. Send the file to your implementation consultant. They will assist you in filling out the remaining fields.
    8. Export a CSV file from Bamboo that contains all of the intended fields for the BambooHR integration.
    9. The specified item was not found. to establish an initial data baseline for Bridge (including creating new attribute pills, if needed). Bridge will update all changes from this data set moving forward.


BambooHR Webhook Configuration

    1. As a user with BambooHR admin permissions, log into BambooHR.
    2. Click on Settings (represented by an icon of a set of cogs).
    3. Click on Webhook in the resulting drop down menu.
    4. Click Add Webhook.
    5. Provide the new webhook a name. The name can be anything of your choosing that will identify the webhook to you an other Bamboo admins.
    6. Under the section titled "What fields do you want to monitor?" browse for and select the fields that you would like to be sent to Bridge.
    7. Make sure that "Termination Date" is included in this list. This field is required for the integration.
    8. Under the section titled "What fields do you want to post?" browse for and select those same fields that you would like to be sent to Bridge.
    9. Make sure that "Termination Date" is also included in this list.
    10. Under the section titled "What format should the data be in?" select JSON.
    11. Under the section titled "Where should the data be posted?" input the full URL as provided to you by your Bridge implementation consultant.
    12. Under the section titled "When should the data be sent?" select a frequency that makes sense according to your internal processes.
      • You should consider configuring this frequency to occur in a "non-peak" access timeframe (for example, 2 a.m. local time).
      • At minimum you should consider sending data on a weekly basis.
      • At maximum you should consider sending data hourly.
    13. Click Save.
    14. Notify your Bridge implementation consultant that the configuration of the webhook is complete.


Your implementation consultant will notify you when the configuration file has been uploaded to your Bridge account, completing the configuration.



Ensuring the integration is working as expected could take two forms: first, creating fake data sets or second, waiting for changes to happen within the organization and verifying those changes also synced in your Bridge instance.


Scenario One

    1. Create one new test user. Wait for the sync to occur and check the data in Bridge (for testing purposes, you could accelerate the push cadence in your webhook configuration).
    2. Modify the test user. Wait for sync. Verify the data.
    3. Delete the test user. Wait for sync. Verify the data.


Scenario Two

    1. Note the data that is changed in BambooHR according to the regular workflow of your HR group. Verify those changes are also made in Bridge.




What I'm ExperiencingWhat's Likely HappeningSteps to Fix it
I do not see all of the fields that I chose to push from BambooHR to Bridge.

The field was not mapped in the BambooHR Mapping document,


the configuration file was improperly formatted.

  • Verify that your mapping document contained the intended field.
  • Contact your implementation consultant (or CSM) to either notify of the intended field or notify them that the field was not mapped.
I do not see intended changes to my data reflected in Bridge.If you are checking immediately after a scheduled sync, Bamboo may still be pushing the data or Bridge may still be processing the data.
  • Verify the timeframe on your webhook.
  • Wait roughly 60-90 minutes and check again on your data.
  • Contact your implementation consultant (or CSM).


Additional Reading



2 people found this helpful