Connectors

OnLink connectors let you connect to the following data sources natively from Atlassian.

As a HR Business Partner, you can quickly connect to the applications without the need for api-specific knowledge or the use of custom code.

Workday

The Workday connector lets you connect to a Workday instance and access Workday resources using the published APIs.

Following details are required to establish the workday connection

Workday API URL: This URL forms the base URI for every API request. Find out how to obtain this URL from this Workday article. The default is https://wd2-impl-services1.workday.com/ccx/service/. You can search for "public web service" in your tenant, access the web services, click on the related action to view WSDL. At the very bottom of the WSDL you will see the URL.
Workday API version: API Version to use e.g “v40.1”
Workday Tenant Name: The tenant for the account. Tenant name is found in the URL when you are logged into Workday. For example, if the URL of your Workday tenant is https://impl.workday.com/sample_company/d/home.html, tenant name is sample_company
Workday Username: The username to connect to the tenant. Workday recommends using an Integration System User (ISU) for integration using third party services like OnLink. This ensures all operations performed by the integration will be logged under this user, and can be audited. Furthermore, it avoids issues of workers getting terminated and their account no longer working.
Workday Password: The password associated with the user.

The Greenhouse connector lets you connect to a Greenhouse instance and access Greenhouse resources using the published APIs.

Following details are required to establish the connection

Greenhouse API URL: Greenhouse service endpoint URL. Should be set to: https://harvest.greenhouse.io
Greenhouse API Token: API token that will be used to establish the connection. Harvest API keys can be obtained in Greenhouse. In order to create a Harvest API key, a user must be granted the “Can manage ALL organization’s API Credentials” in the “Developer permission” section. That user can then go Configure >> Dev Center >> API Credential Management. From there, you can create a Harvest API key and choose which endpoints it may access. Ref: https://developers.greenhouse.io/harvest.html#introduction
Note: Users with Harvest API keys may access all the data in the endpoint. Access to data in Harvest is binary: everything or nothing. Harvest API keys should be given to internal developers with this understanding and to third parties with caution. Each key should only be allowed to access the endpoints it absolutely needs.

The BambooHR connector lets you connect to a BambooHR instance and access BambooHR resources using the published APIs.

Following details are required to establish the connection

BambooHR API URL: BambooHR service endpoint URL. This should be set to https://api.bamboohr.com/api/gateway.php/{company subdomain name}/
where {company subdomain name} is in the URL used to access your account via browser. For example, if you access BambooHR at https://mycompany.bamboohr.com, then the subdomain is "mycompany" and the API url will then be:
https://api.bamboohr.com/api/gateway.php/mycompany/
BambooHR API Key: API Key that will be used to establish the connection. Here's a link from BambooHR that provides more info: https://bamboohr.readme.io/docs#section-authentication.

Please refer to documentation for more information.

Paste the Bamboo HR API key into the API Key field.

Now you need to add your BambooHR subdomain.

API URL is https://api.bamboohr.com/api/gateway.php/{mycompany subdomain name}/
where {mycompany subdomain name} is in the URL used to access your account via browser. For example, if you access BambooHR at https://mycompany.bamboohr.com, then the subdomain is "mycompany" and the API url should be set to:
https://api.bamboohr.com/api/gateway.php/mycompany/

Using the Test feature, we can verify if the connection is successful.