Push Bullhorn data such job orders, job submissions and placements Geckoboard datasets
On macOS and Linux you'll need to open a terminal and run chmod u+x path/to/file (replacing path/to/file with the actual path to your downloaded app) in order to make the app executable.
Open up a terminal (on linux/max) and a command prompt (on windows), and run your script.
./bullhorn-to-dataset push
When you run this - will ask for the username, password and geckoboard apikey. This will need to be input on every run.
Enter your Bullhorn username:
Enter your Bullhorn password:
Enter your Geckoboard apikey:
Should you not want to input these details all the time - please refer to environment variables section
When the script is running there will be basic output of its progress... Similar to below, should an error occur, it will output the error and any error message it can provide.
Authenticating with Bullhorn...Success
Querying data from Bullhorn
Queried 2 job orders
Pushing 2 records to geckoboard
Finished
If you wish, you can provide environment variables instead of needing input - this is useful for running on a server or service. The following environment variables are required to be set.
GECKOBOARD_APIKEY=key
BULLHORN_USER=username
BULLHORN_PASS=password
To use the environment variables you will need to need to pass the switch --creds-from-env after the push command.
Both the job submissions and placements have a load of custom fields that you might want to pull in into the dataset.
This is possible with only environment variables. The environment variable follows the following rule ENTITY_CUSTOMFIELDS
So for placements the environment variable will be PLACEMENT_CUSTOMFIELDS. For job submissions its JOBSUBMISSION_CUSTOMFIELDS,
and for client contacts its CONTACT_CUSTOMFIELDS.
You can specify a list of comma seperated values of as many fields a dataset can accept.
PLACEMENT_CUSTOMFIELDS=customDate1,customText10,customText22,customFloat3,customFloat4
If you specify an invalid custom field or a valid field but out of range you will get the appropriate error message to help
Hopefully this is obvious, but this is where your Geckoboard API key goes. You can find yours here.
These are your credentials you use to login to your instance of Bullhorn, unfortunately they don't provide an API key. So use the credentials to login over the API to retrieve an access token.
By default this app will periodically pull data from Bullhorn and push to Geckoboard every 15 minutes.
If you plan to use your own scheduler like cron or something, then you may pass the switch --single-run
This creates a single dataset in your account called bullhorn-joborders