We rewrote our BambooHR Integration. Unfortunately it sent misleading digest mails instantly. Please disregard.

We’ve overhauled our BambooHR Integration, making an already successful integration even better.  Details below. Unfortunately, the code triggered confusing status mails to all admins at companies that were already using the BambooHR integration.

Please ignore the mails we just sent you

We took the new importer code live yesterday, and it was supposed to be a silent migration. Unfortunately, the new code triggered digest emails to many administrators, letting them know that SI had supposedly updated all their users. We’re now also importing the employee ID field, which is a good thing, but the digest didn’t communicate this well, and it should not have appeared in the initial import at all.  No “real” changes (like core fields or reporting structure) were made to your user base, so you can disregard the mail.

To make things worse, the digest accidentally listed a “deleted user” as the author of the change, not the “BambooHR Import” as it used to. We’re sorry about the confusion this has caused. In effect nothing happened and all is good.

Here’s why the new import is a great thing anyway

The BambooHR integration is our most important integration by far. It has been working reliably since 2011 and saves our customers tons of headaches by keeping BambooHR and SI in sync. We rewrote the integration to make a great feature even better. It is that central to us. Here’s what changed:

More interactive

Especially if you’re a larger company, you’ll love the fact that the preview table can be sorted by any column, and you can use the bar chart at the top to drill into the changes that you’re most interested in.bamboo2

Audit trail, and more secure

Each successful import now leaves an audit trail entry, so you can go back in time and get a detailed explanation what changed at what point. Click the details button for the nitty gritty of “what user changed in what way exactly?”


We’re storing your API key as before, but we’re not displaying it beyond the first couple of characters anymore. Not unlike a credit card you entered into an online shop, you’ll be able to identify which API key you’re using, while it’s not possible to extract it anymore, since only a few characters are displaying.Manage_the_BambooHR_Integration_-_Small_Improvements

More scalable

The old import had some inherent technical limitations that meant it could only preview up to 300 changes at once, which was especially annoying when a larger client wanted to preview the initial import. Now fixed. Preview as many changed users as you like.

More intuitive for new users

When visiting the screen for the first time, you only need to enter your credentials, and then you save them. Only then you’ll get to see the preview screen and the history tab, and you won’t end up in the config tab anymore by default, but in the history tab.

That’s how it should have been right from the start, but the “old” BambooHR Import had grown over time, and while it worked it was just a bit clunky to use. Now fixed.

Built with future integrations in mind

Truth be told, the old import was a technical mess internally. It worked fine, but we couldn’t reuse any of it for what we’re planning. So we made sure that new import is the perfect basis for future integration. We’ll rewrite the Google Apps integration next, and we’re aiming to allow self-service CSV and Excel import later this year. And we’re hoping to provide a convenient Workday import as well soonish.

As always we don’t promise any exact dates (our roadmaps do change) but we’ve come a long way already, so fingers crossed!