Bullhorn CRM Connection
See the Connector Marketplace topic. Please request your administrator to start a trial or subscribe to the Premium Bullhorn CRM connector.
Bullhorn CRM is a commercial distributed SQL database management system.
This topic describes how to authenticate to Bullhorn CRM and configure any necessary connection properties in the Bullhorn CRM connection connector.
Connection Configuration
Each connection property available in the Bullhorn CRM connector is explained below.
Connection Name
The name of the connection to be created should be provided. This is the name that will display on the list of available connections.
Data Center Code
The data center code where your account’s data is hosted.
Example: CLS2, CLS5 etc…
Find the list of the data centers here.
Rest URL
This is used as the base URL of the Bullhorn CRM REST API.
This is retrieved automatically during the OAuth flow in WEB mode.
If you execute the OAuth flow manually in APP mode, you must specify this after getting it as an output of the GetOAuthAccessToken.
Client ID
The client Id assigned when you register your application with an OAuth authorization server.
Client Secret
The client secret assigned when you register your application with an OAuth authorization server.
Refresh Token
The OAuth refresh token for the corresponding OAuth access token.
Advanced Configuration
This section contains advanced configuration parameters.
Include Custom Fields
A boolean indicating if you would like to include custom fields in the column listing.
Setting this to true will cause custom fields to be included in the column listing, but may cause poor performance when listing metadata.
Include Custom Tables
Whether to include custom tables or not. When off, performance will be higher, but the custom tables cannot be retrieved.
If set to TRUE, the custom tables will be retrieved, at the cost of some performance.
Use Default OrderBy
Indicates if a default order by should be applied if none is specified in the query.
By default, the Bullhorn CRM connector applies an order by when none is specified.
This ensures that duplicate records do not get output when returning data.
However, this will have a significant impact on performance for very large tables.
If your use case can handle the possibility of duplicate primary keys, it is recommended to turn this off if you would like to have better performance.
After entering all the details, click on the TEST button.
If the connection service identification and authentication details are provided correctly, a success message stating “connection available” is generated.
Click on the CREATE button to save the changes.
If the details are incorrect or the server is down, you will get a message “Connection unavailable”.
If you have any feedback on Gathr documentation, please email us!