Namely to JSM Assets

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.

image-20250328-173155.png
  1. Open OnLink from Jira.

  2. Go to the Connections tab.

  3. Click Add a connection.

  4. Select Namely.

  5. Enter the Namely API URL in this format: https://{company}.namely.com/.

  6. Enter the Namely personal access token as the API key.

  7. 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.

  1. Enter a descriptive name for the mapping.

  2. Set Source system to Namely.

  3. Confirm the Asset Schema. OnLink pre-fills this value from the JSM Assets schema where you started the configuration.

  4. Select the target Object Type within the schema.

  5. Select the schedule frequency for automated production runs.

  6. 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=Email

Mapping reference

Use the following reference to understand each mapping entry.

Mapping item

Purpose

Notes

Mapping item

Purpose

Notes

key:id=ID

Uses the Namely id value as the unique key for the Assets object.

Required. This lets OnLink update existing records instead of creating duplicates.

map:first_name=First Name

Maps the Namely first_name field to the JSM Assets attribute First Name.

The target Assets attribute should be a text attribute.

map:last_name=Last Name

Maps the Namely last_name field to the JSM Assets attribute Last Name.

The target Assets attribute should be a text attribute.

map:email=Email

Maps the Namely email field to the JSM Assets attribute Email.

Use this value to identify users or support additional user lookup mappings where applicable.

config:data_source=<api name>

Changes the Namely API data source that OnLink pulls from.

Optional. For example, set this to groups to pull groups. By default, OnLink pulls profiles.

config:filterKey
config:filterValue

Filters the profiles returned by Namely.

For example, use config:filterKey=user_status and config:filterValue=active to pull active users.

Optional configuration parameters

Parameter

Description

Parameter

Description

config:data_source=<api name>

Sets the Namely API resource to import. By default, OnLink pulls profiles. Use another supported Namely API keyword, such as groups, when importing a different data set.

config:filterKey=user_status
config:filterValue=active

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.

  1. Click Get Data to pull records from Namely into OnLink staging.

  2. Open the job logs and wait for the message: No more pending records. Data will be imported on next Import run.

  3. Click Import Data to create or update objects in JSM Assets.

  4. 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.

image-20240318-045922.png