Namely to JSM Assets
Import Namely Data into JSM Assets with OnLink
Use OnLink to import employee profile data and related attributes from Namely into Jira Service Management (JSM) Assets.
Overview
This guide explains how to configure an OnLink import from Namely to JSM Assets. You will connect OnLink to Namely, create an Assets import configuration, define field mappings, test the import, and optionally filter the Namely data returned by the API.
Prerequisites
OnLink is installed and available in Jira from Manage your apps.
You have access to the target JSM Assets schema and object type.
You have a Namely company subdomain for the API URL, for example
https://{company}.namely.com/.You have a Namely personal access token to use as the API key.
Connect OnLink to Namely
Create the Namely connection before configuring the Assets import.
Open OnLink from Jira.
Go to the Connections tab.
Click Add a connection.
Select Namely.
Enter the Namely API URL in this format:
https://{company}.namely.com/.Enter the Namely personal access token as the API key.
Save the connection.
Set up the Assets import configuration
First, create the base Assets import configuration. Review the setup guide: Assets import configuration.
After the base configuration is created, open OnLink from Manage your apps and configure the Namely source and field-level mappings.
Configure the Namely importer
Use the following procedure to configure the importer.
Enter a descriptive name for the mapping.
Set Source system to Namely.
Confirm the Asset Schema. OnLink pre-fills this value from the JSM Assets schema where you started the configuration.
Select the target Object Type within the schema.
Select the schedule frequency for automated production runs.
Add the attribute mappings. Use the mapping examples below as a starting point.
Mapping examples
Profile mapping
Use this mapping to import Namely profiles into a JSM Assets employee or user object type.
key:id=ID
map:first_name=First Name
map:last_name=Last Name
map:email=EmailMapping reference
Use the following reference to understand each mapping entry.
Mapping item | Purpose | Notes |
|---|---|---|
| Uses the Namely | Required. This lets OnLink update existing records instead of creating duplicates. |
| Maps the Namely | The target Assets attribute should be a text attribute. |
| Maps the Namely | The target Assets attribute should be a text attribute. |
| Maps the Namely | Use this value to identify users or support additional user lookup mappings where applicable. |
| Changes the Namely API data source that OnLink pulls from. | Optional. For example, set this to |
| Filters the profiles returned by Namely. | For example, use |
Optional configuration parameters
Parameter | Description |
|---|---|
| Sets the Namely API resource to import. By default, OnLink pulls profiles. Use another supported Namely API keyword, such as |
| Filters profile data so the import only processes records that match the specified key and value. |
Test and validate the import
OnLink processes data in two separate steps: Get Data and Import Data.
Click Get Data to pull records from Namely into OnLink staging.
Open the job logs and wait for the message: No more pending records. Data will be imported on next Import run.
Click Import Data to create or update objects in JSM Assets.
Review the target object type in JSM Assets and confirm that objects and attributes were imported as expected.
Production runs are fully automated based on the schedule selected in the importer configuration.