Paylocity to JSM Assets

Paylocity to JSM Assets

Paylocity to JSM Assets

Use this guide to import employee records from Paylocity into Jira Service Management (JSM) Assets through OnLink. It covers the Paylocity connection, Assets import setup, field mapping, sample API structure, and testing workflow.

Outcome: OnLink retrieves employee data from Paylocity and imports it into JSM Assets using the field mapping you define.

Before you begin

  • Confirm you have access to OnLink from Manage your apps in Jira.

  • Confirm you have permission to create or edit JSM Assets import configurations.

  • Prepare the target Assets object type and attributes, such as First Name, Last Name, Email, Job Title, Manager Name, and Hire Date.

  • Review the Paylocity connection setup instructions: Paylocity API

  • Review the OnLink Assets import setup instructions: JSM Assets Data Synchronization

1. Configure the Paylocity connection

  1. In Jira, go to Manage your apps.

  2. Open OnLink, then go to Connections.

  3. Select Add System.

  4. Choose Paylocity from the connection options.

  5. Follow the connection setup prompts and save the connection.

After the connection is established, continue with the Assets import configuration.

2. Create the Assets import configuration

  1. Open the OnLink app from Manage your apps.

  2. Create or open the JSM Assets import configuration that will receive Paylocity employee data.

  3. Select the Paylocity connection you configured earlier.

  4. Configure the API and field mapping values in the import configuration.

Paylocity employee API reference: https://developer.paylocity.com/integrations/reference/get_corehr-v1-companies-companyid-employees

3. Configure employee field mappings

The following example maps Paylocity employee fields to JSM Assets attributes.

key:id=id map:info.firstName=First Name map:info.lastName=Last Name map:info.email=Email map:info.jobTitle=Job Title map:info.supervisor=Manager Name map:info.hireDate=Hire Date

Mapping reference

Configuration

Description

Configuration

Description

key:id=id

Uses the Paylocity employee id as the unique identifier. This allows OnLink to update the same Assets object on future imports instead of creating duplicates.

map:info.firstName=First Name

Maps the employee first name from Paylocity to the First Name text attribute in Assets.

map:info.lastName=Last Name

Maps the employee last name from Paylocity to the Last Name text attribute in Assets.

map:info.email=Email

Maps the employee email address from Paylocity to the Email attribute in Assets.

map:info.jobTitle=Job Title

Maps the employee job title from Paylocity to the Job Title attribute in Assets.

map:info.supervisor=Manager Name

Maps the Paylocity supervisor value to the Manager Name attribute in Assets.

map:info.hireDate=Hire Date

Maps the employee hire date from Paylocity to the Hire Date attribute in Assets.

4. Optional configuration settings

Use optional config: entries to control which API is called and how much data is processed.

Setting

Purpose

Setting

Purpose

config:filter=activeOnly

Limits the import to active employees.

config:max_loops=10

Sets the maximum number of pagination loops that OnLink should process during the data retrieval step.

config:api

 

Changes the Paylocity API endpoint used by the configuration. If this setting is not provided, the default API is employees.

To get cost centers

config:api=corehr/v1/companies/{companyId}/costCentersAndLevels

To get position codes and job titles

config:api=positionManagement/v1/companies/{companyId}/positions

To get work locations

config:api=apiHub/corehr/v1/companies/{companyId}/workLocations

5. Review the Paylocity API response structure

Click Fetch Sample in OnLink to retrieve a sample API response. Use the response to identify the Paylocity fields that should be mapped into JSM Assets.

{ "totalCount": 0, "employees": [ { "id": "string", "companyId": "string", "relationshipId": "string", "lastName": "string", "displayName": "string", "status": "string", "statusType": "string", "currentStatus": { "status": "string", "statusCode": "string", "statusType": "string", "effectiveDate": "2025-12-09T00:51:22.580Z", "changeReason": "string", "changeReasonCode": 0, "additionalProp": {} }, "info": { "firstName": "string", "lastName": "string", "displayName": "string", "middleName": "string", "preferredName": "string", "suffix": "string", "address": { "address1": "string", "address2": "string", "city": "string", "state": "string", "postalCode": "string", "country": "string", "county": "string", "additionalProp": {} }, "homePhone": "string", "mobilePhone": "string", "personalEmail": "string", "ssn": "string", "dateOfBirth": "string", "maritalStatus": "string", "ethnicityRace": "string", "gender": "string", "hireDate": "2025-12-09T00:51:22.580Z", "adjustedSeniorityDate": "2025-12-09T00:51:22.580Z", "eligibleforRehire": true, "supervisorCo": "string", "supervisor": "string", "isSupervisor": true, "reviewerCo": "string", "reviewer": "string", "jobTitle": "string", "eeoClass": "string", "wcc": "string", "shift": "string", "clockBadge": "string", "payGroup": "string", "otExempt": true, "tipped": "string", "minWageExempt": true, "workLocation": { "address": { "address1": "string", "address2": "string", "city": "string", "state": "string", "postalCode": "string", "country": "string", "county": "string", "additionalProp": {} }, "phone": "string", "phoneExt": "string", "mobilePhone": "string", "email": "string", "additionalProp": {} }, "additionalProp": {} }, "currentPayRate": { "baseRate": 0, "defaultHours": 0, "salary": 0, "payFrequency": "string", "payGrade": "string", "annualSalary": 0, "ratePer": "string", "effectiveDate": "2025-12-09T00:51:22.580Z", "beginCheckDate": "string", "isAutoPay": true, "payType": "string", "additionalProp": {} }, "position": { "effectiveDate": "2025-12-09T00:51:22.580Z", "changeReason": "string", "costCenter1": "string", "costCenter2": "string", "costCenter3": "string", "employeeType": "string", "positionCode": "string", "positionDescription": "string", "careerLevelCode": "string", "careerLevelDescription": "string", "positionFamilies": [ { "code": "string", "description": "string", "name": "string", "additionalProp": {} } ], "additionalProp": {} }, "futurePayRates": [ { "salary": 0, "payFrequency": "string", "changeReason": "string", "annualSalary": 0, "effectiveDate": "2025-12-09T00:51:22.580Z", "beginCheckDate": "string", "isAutoPay": true, "payType": "string", "payRateDescription": "string", "additionalProp": {} } ], "additionalProp": {} } ], "additionalProp": {} }

6. Test the import

  1. In the import configuration, click Fetch Sample to confirm the response structure and validate your mappings.

  2. Click Get Data.

  3. Open Job Logs and wait for the message: No more pending records. Data will be imported on next Import run.

  4. Click Import to import the retrieved data into JSM Assets.

  5. Review the imported Assets objects and confirm that each mapped attribute is populated as expected.

Production runs: Manual Get Data and Import actions are useful for testing. Production imports run automatically based on the schedule configured in OnLink.

7. Validate results

Paylocity connection is saved and active.
Assets import configuration points to the correct Paylocity connection.
Unique key mapping is configured with key:id=id.
Required employee fields are mapped to the correct Assets attributes.
Fetch Sample returns the expected employee response.
Get Data completes with no pending records.
Import creates or updates employee objects in JSM Assets.

Reference screenshot

image-20240318-045922.png