Hive HRHive is an employee feedback platform and strategic HR partnership.
Hive HR is intuitive, cost effective, user-friendly, data and insight rich, always on an employee engagement platform.
Within the workflow builder, highlight the Hive HR connector.
In the Hive HR connector properties panel to the right of the builder, click on the Authenticate tab and the 'New authentication' button.
This will result in a Tray.io authentication pop-up modal. The first page will ask you to name your authentication and select the type of authentication you wish to create ('Personal' or 'Organisational').
The next page asks you for your 'API token' and 'Organization ID' credentials.
In order to get these fields you will need to contact your Customer Success Representative at Hive HR.
Once you have added these fields to your Tray.io authentication pop-up window, click the 'Create authentication' button.
Go back to your settings authentication field (within the workflow builder properties panel), and select the recently added authentication from the dropdown options now available.
Your connector authentication setup should now be complete.
The examples below show one or two of the available connector operations in use.
Please see the Full Operations Reference at the end of this page for details on all available operations for this connector.
Using the Raw HTTP Request ('Universal Operation')
As of version 1.0, you can effectively create your own operations.
This is a very powerful feature which you can put to use when there is an endpoint in Hive HR which is not used by any of our operations.
To use this you will first of all need to research the endpoint in the Hive HR API documentation v1.0, to find the exact format that Hive HR will be expecting the endpoint to be passed in.
Note that you will only need to add the suffix to the endpoint, as the base URL will be automatically set (the base URL is picked up from the value you entered when you created your authentication).
The base URL for Hive HR is: `https://services.hive.hr\`
For example, say that the 'List integrations' operation did not exist in our Hive HR connector, and you wanted to use this endpoint. You would use the Hive HR API docs to find the relevant endpoint - which in this case is a `GET` request called: `/integration-rpc/api/integrations`.
More details about this endpoint can be found here.
So if you know what your method and endpoint are, you can get the list of your integrations with the following settings:
Body Type : `none`
Final outcome being: https://services.hive.hr/integration-rpc/api/integrations
Below is an example of a way in which you could potentially use the Hive HR connector, to create an integration mapping between Hive HR and Bamboo HR.
The steps will be as follows:
- Setup using a manual trigger and create a new integration in your account
- Create a new integration mapping between Hive HR and another external system
Your completed workflow should look similar to this:
1 - Setup Trigger & Create integration
Select the Manual trigger from the trigger options available. From the connectors panel on the left, add a Hive HR connector to your workflow. Set the operation to 'Create integration'.
Make sure to give a 'Name' and select the 'Type' of your integration.
Now when this workflow is run, it will create an integration with the given details.
Feel free to re-name your steps as you go along to make things clearer for yourself and other users. The operation names themselves often suffice.
2 - Create integration mapping
Next, add the second Hive HR connector to the workflow and set your operation to 'Create integration mapping'.
In order to specify the 'Integration ID', start by using the list mapping icon (found next to the Integration ID input field, within the properties panel) to generate the connector-snake.
While hovering over the 'Create integration' step (with the tail end of the connector-snake), select `id` from the list of output properties displayed. This will auto-populate a jsonpath within your list input field, and update the type selector to jsonpath.
For more clarification on the pathways you have available, open the Debug panel to view your step's Input and Output.
Note that you also need to define the 'User ID' and the 'Foreign ID'.
Now when this workflow is run, it will create an integration mapping with the given details.