Tableau Connector for Bullhorn CRM

Build 23.0.8839

Configuring a Connection

After Installing the Connector you can connect and create a Data Source for data in Bullhorn CRM.

Setting Up a Data Source

Complete the following steps to connect to the data:

  1. Under Connect | To a Server, click More....
  2. Select the data source called Bullhorn CRM by CData.
  3. Enter the information required for the connection.
  4. Click Sign In.
  5. If necessary, select a Database and Schema to discover what tables and views are available.

Using the Connection Builder

The connector makes the most common connection properties available directly in Tableau. However, it can be difficult to use if you need to use more advanced settings or need to troubleshoot connection issues. The connector includes a separate connection builder that allows you to create and test connections outside of Tableau.

There are two ways to access the connection builder:

  • On Windows, use a shortcut called Connection Builder in the Start menu, under the CData Tableau Connector for Bullhorn CRM folder.
  • You can also start the connection builder by going to the driver install directory and running the .jar file in the lib directory.

In the connection builder, you can set values for connection properties and click Test Connection to validate that they work. You can also use the Copy to Clipboard button to save the connection string. This connection string can be given to the Connection String option included in the connector connection window in Tableau.

Connecting to Bullhorn CRM

Begin by providing your Bullhorn CRM account credentials. Set DataCenterCode to the data center code that responds to your data center. Refer to the list here.

If you are uncertain about your data center code, codes like CLS2, CLS21, etc. are cluster IDs that are contained in a user's browser URL (address bar) once they are logged in.

Example: https://cls21.bullhornstaffing.com/BullhornSTAFFING/MainFrame.jsp?#no-ba... indicates that the logged in user is on CLS21.

Note: If you specify callback URL value that contains "/" character at the end, e.g., http://localhost:33333/ you must specify exactly the same value. It must match the callback URL you specify in your application settings.
Adding or removing any character of this parameter results in an error.

Authenticating to Bullhorn CRM (OAuth)

Bullhorn CRM uses the OAuth 2.0 authentication standard.

In all scenarios, to authenticate using OAuth, you must create and configure a custom OAuth application. See Creating a Custom OAuth App for more information.

Desktop Applications

Follow the steps below to authenticate with the credentials for a custom OAuth application.

Scenario 1: Verifier Code

Making any changes to your OAuth application (such as the CallbackURL) requires reaching out to Bullhorn CRM directly, which can be a time-consuming process. So, we highly recommended that you instead use an OAuthVerifier to connect. To obtain a verifier, you also need an OAuth Authorization URL.

Retrieving an OAuth Verifier Code

Construct your authorization URL as follows:
https://<authurl for your data center>/oauth/authorize?client_id=<your OAuth client id>&response_type=code

For example, if you had data center "CLS5", the authentication URL is https://auth.bullhornstaffing.com/oauth/authorize?client_id=your_client_id&response_type=code.

Please refer to the list here to determine the authentication URL for your data center.

Next, retrieve the OAuth verifier code:

  1. Open your authorization URL in a browser. Log in and grant permissions to the connector. You are then redirected to the callback URL, which contains the verifier code.
  2. Save the value of the verifier code.

Get and Refresh the OAuth Access Token

After setting the following, you are ready to connect:

  • OAuthVerifier: Set this to the OAuth Verifier code obtained previously.
  • DataCenterCode: Set this to the respective data center your account is connected with. Find the list of the data centers here. For example, CLS33.
  • OAuthClientId: Set this to the client Id assigned when you registered your application.
  • OAuthClientSecret: Set this to the client secret assigned when you registered your application.
  • InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.

When you connect the connector opens the OAuth endpoint in your default browser. Log in and grant permissions to the application. The connector then completes the OAuth process:

  1. Extracts the access token from the callback URL and authenticates requests.
  2. Obtains a new access token when the old one expires.
  3. Saves OAuth values in OAuthSettingsLocation. These stored values persist across connections.
Scenario 2: Custom CallbackURL

You also have the option of requesting a custom callback URL (for example, http://localhost:33333) from Bullhorn CRM. If you have been provided with a custom CallbackURL, you can set the following to connect to data:

  • CallbackURL: Set this to the custom callback URL provided by Bullhorn CRM.
  • DataCenterCode: Set this to the respective data center your account is connected with. Find the list of the data centers here. For example, CLS33.
  • OAuthClientId: Set this to the client Id assigned when you registered your application.
  • OAuthClientSecret: Set this to the client secret assigned when you registered your application.
  • InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
The connector then completes the OAuth process:
  1. The process finalizes with the access token returned from the Bullhorn CRM API.
  2. Refreshes the access token when it expires.
  3. Saves OAuth values in OAuthSettingsLocation to be persisted across connections.

Next Step

See Using the Connector to create data visualizations.

Copyright (c) 2024 CData Software, Inc. - All rights reserved.
Build 23.0.8839