Setting up your Bullhorn integration - Part 1: Setting up the idibu iframe url

This article will walk through each step required to complete the foundation for setting up your Bullhorn integration. It’s the first stage in your setup of either Bullhorn, or Bullhorn Novo. This is to create a bespoke URL, that will then be inserted into a custom tab inside your Bullhorn account.

In this article we’ll cover:

  1. Creating unique ID and Secret tokens to insert into your URL
  2. The two types of URL you can create, and why you might choose one over the other
  3. How to bring everything together to create your URL
  4. Links to the next steps of your integration set up

At this point, we’d like to add a few word of reassurance if you consider yourself to be ‘non-techy’... 

This article is being written by someone from a recruitment background, not a technical background. All the above steps amount to is creating some text codes and then copying and pasting them into another string of text. If you get stuck or feel unsure of anything, please don’t hesitate to contact our support team.


Creating your unique ID and Secret tokens

When we talk about creating your ID and Secret tokens, the word ‘token’ might sound a little misleading if you are not familiar with the term. All we mean by this is a unique letter and number code that is generated automatically for both values.

In this article we take you through each step of the process. As long as you have administrator level access in your idibu account you won’t need any other specialist tools or knowledge.

Once you have created these tokens, you will be ready for the next step.


Using your tokens to create your URL

Having created your tokens following the steps in the article above, all you now need to do is copy them into a URL template we’re going to give you. This is quite straight forward but the key things to watch are that:

  1. You copy every character in each token
  2. ...and insert them into the right bit of the url.

For this step we’d suggest opening Notepad, or a similar ‘plain text’ application. If you are using a Mac, we like ‘Sublime Text’ as an App for this sort of thing - but any plain text application will do.

Why not use Word, Googledocs or similar?

A plain text application means that the URL won’t be hyperlinked during editing, and you therefore won’t find yourself being redirected to your browser each time you click on it.


Creating your URL, step by step:

1. Here is the basic URL template we are going to work with - the correct template to select is based on whether you are using Bullhorn Novo or Bullhorn S-Release:

Bullhorn Novo:

https://v3.idibu.com/c/integration/bullhornnovo/id/VALUE_FOR_ID/secret/VALUE_FOR_SECRET/data_center/

Bullhorn S-Release:

https://v3.idibu.com/c/integration/bullhorn/id/VALUE_FOR_ID/secret/VALUE_FOR_SECRET/data_center/

2. Copy this into your text document.  

3. The bits you will be changing are 'VALUE_FOR_ID' and 'VALUE_FOR_SECRET'. You will also be adding your allocated Bullhorn data centre to the end of the URL. To show you what to do next, we’ll walk you through with our own example: 

Now let’s say for arguments sake that idibu generated my ID token as MONKEYBANANA (which would be cool, but unlikely). I firstly copy this into Notepad, then highlight > 'right click' > and 'copy' the text.

4. I then highlight the VALUE_FOR_ID text in the URL and then right click and ‘paste’

5. Now, in an equally unlikely twist of fate, let’s pretend that idibu generated my SECRET token as ELEPHANTPEANUT

I simply follow the same process to replace the VALUE_FOR_SECRET text:

6. All that remains now is to add the value for your allocated Bullhorn data centre. (If you are unsure of this, then contact your Bullhorn support team, but it is sometimes displayed briefly in the URL when you sign in to Bullhorn). In our example, I'm going to add the value 'CLS2' as shown:

7. The URL is now complete, and I can use this to create my custom idibu tab inside Bullhorn.

We used a couple of silly examples above to make it easier to distinguish where you need to copy and paste your text, and what parts of the URL to leave unchanged. The real ID and SECRET tokens created by your account will look quite different. So your URL will probably look something like this:

https://v3.idibu.com/c/integration/bullhornnovo/id/6014-CFABAFAAA-F8FEC4ABB-3A8E91CCC-1DADD/secret/UU16VDZJ5POAC0JRWSFBKTDIKABCDEFGHIJKLMNO/data_center/CLS2

(Remember: Your actual ID and SECRET values will be different to the above, and are unique to your account. The above is just a fake example.) 

It might look intimidating to someone seeing it for the first time, but as we’ve hopefully demonstrated above - in reality it’s just a line of text.

You can now proceed to part 2 of the setup, or as outlined below, add some extra detail to this URL so that new users are synced into a default idibu group.


Syncing new users to a default Group inside idibu

The URL we just created above is the basic version.  When added to Bullhorn it serves to create a unique and secure link between your idibu and Bullhorn accounts. When a user opens idibu inside Bullhorn, we link their two accounts automatically so vacancy, advert and candidate data can be process seamlessly.

But what about a new Bullhorn user who doesn’t have an idibu account set up?

In this scenario when the user opens idibu for the first time, we’re able to extract some basic details such as their name and email, and create a unique ID that links the two accounts.

However, other details such as office address, phone number and website will still need completing on their idibu profile. They can do this themselves when they first post out an advert, but what can’t be updated dynamically this way is anything other than their very basic user permissions.  For access to other idibu tools you have purchased, you or another administrator will need to allocate these permissions inside their idibu user profile.

That is, unless you create a default idibu group to sync your new Bullhorn users into

Building on the example above, let’s say I wanted to create a default group called ‘Zoo’ where all new users created via Bullhorn are pushed into.  In this group I can specify default address and company info, and can specify the universal permissions I want every user to have.

I therefore will only ever need to intervene and update specific user records to which I want to give special permissions, or to move them into another group. But from day one, they will have the permissions required to do what I need them to at basic level.

Here’s an example of the core information I’ve populated, and some extra permission I’ve allocated for every user in this group:

Having created this group, I can now tell the Bullhorn and idibu integration to push newly created users into this group, simply by adding the details to the URL created earlier.

Important: This only applies to users who have not been added manually to idibu prior to the first integration sync. If you prefer to add the user record manually and allocate them to the correct group in idibu, then the first time they open idibu inside Bullhorn, we will simply link the existing records. This may be preferable if you have multiple locations and want to ensure the user is allocated the correct address details from day one.


Adding Group logic to your URL

1. All we need to do is add some additional details to the URL we have already created. So using our example above we simply would add “/group/Zoo” to the end of the URL:

2. In other words, to add your own group to your URL, you simply add “/group/” followed by your default group name. The key point is to ensure you use exact group name in your URL. If you are struggling for ideas as to what to call your group, then “Default” is a nice clear option.

Here’s how the URL would look with a group called “Default” added:

As per the example above, your own URL with a group titled default would look something like this:

https://v3.idibu.com/c/integration/bullhornnovo/id/6014-CFABAFAAA-F8FEC4ABB-3A8E91CCC-1DADD/secret/UU16VDZJ5POAC0JRWSFBKTDIKABCDEFGHIJKLMNO/data_center/CLS2/group/Default

(Remember: Your actual ID and SECRET values will be different to the above, and are unique to your account. The above is just a fake example.) 


Next steps...

Whichever URL option you have chosen, you are now ready to complete the set up of your Bullhorn integration.

Still need help? Create a ticket Create a ticket