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
In Jira, go to Manage your apps.
Open OnLink, then go to Connections.
Select Add System.
Choose Paylocity from the connection options.
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
Open the OnLink app from Manage your apps.
Create or open the JSM Assets import configuration that will receive Paylocity employee data.
Select the Paylocity connection you configured earlier.
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 DateMapping reference
Configuration | Description |
|---|---|
| Uses the Paylocity employee |
| Maps the employee first name from Paylocity to the First Name text attribute in Assets. |
| Maps the employee last name from Paylocity to the Last Name text attribute in Assets. |
| Maps the employee email address from Paylocity to the Email attribute in Assets. |
| Maps the employee job title from Paylocity to the Job Title attribute in Assets. |
| Maps the Paylocity supervisor value to the Manager Name attribute in Assets. |
| 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 |
|---|---|
| Limits the import to active employees. |
| Sets the maximum number of pagination loops that OnLink should process during the data retrieval step. |
| Changes the Paylocity API endpoint used by the configuration. If this setting is not provided, the default API is To get cost centers
To get work locations
|
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.
6. Test the import
In the import configuration, click Fetch Sample to confirm the response structure and validate your mappings.
Click Get Data.
Open Job Logs and wait for the message: No more pending records. Data will be imported on next Import run.
Click Import to import the retrieved data into JSM Assets.
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
key:id=id.