> For the complete documentation index, see [llms.txt](https://prohelp.assetpanda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prohelp.assetpanda.com/integrations-store/device-management/hexnode-integration.md).

# Hexnode Integration

You can integrate Hexnode with Asset Panda Pro to import and synchronize data such as devices, users, device or user groups, and policies into Asset Panda Pro. You can map fields for flexible data transfer and filter the transfer to limit the data synchronization. Updates can be synchronized manually or on a schedule.

{% hint style="info" %}

* This integration is only one-way (Hexnode → Asset Panda Pro). Asset Panda Pro changes are not transferred to Hexnode.
* Data is fetched from Hexnode and created or updated in Asset Panda Pro based on defined mappings.
  * Records are created if they do not exist.
  * Records are updated if a matching record is found using the unique identifier.
* If a record is removed from Hexnode, it remains unchanged in Asset Panda Pro.
* Sync performance depends on dataset size and API limits.
  {% endhint %}

***

## Prerequisites <a href="#prerequisites" id="prerequisites"></a>

* Admin access to the Asset Panda Pro web application and the Integration Store
* Hexnode **Portal URL**
* Hexnode **API Key / Token**
* Permissions in Hexnode to access entities (for example, devices and users)

***

## Add the Hexnode integration <a href="#adding-the-integration" id="adding-the-integration"></a>

1. Log into Asset Panda Pro with an administrator account.
2. Navigate to <img src="/files/dLHka5YWbUR3zisHLua6" alt="Settings icon" data-size="line"> **Settings** > **Account Management**.
3. Expand the appropriate account and module.
4. Click **Manage** in the **Integrations** card.
5. In the **Hexnode** tile, click **Add**, and then click **Edit**.&#x20;
6. Enter the following details:
   * **Portal URL**: Web address of the system to which you are connecting. This identifies the location of the service.
   * **API Key**: Paste the Hexnode API key.
7. Click **Test and save connection** to verify the credentials. If the connection is valid, a success message is displayed and a green check is displayed above the **Authentication** tab.&#x20;
8. Click **Continue with mapping**. The **Mapping List** page is displayed.
9. Create a mapping to define how data flows between Hexnode and Asset Panda:

   1. Click **Add mapping option**.
   2. Enter the **Mapping Name** (for example, `Hexnode Device Import`).
   3. Select the appropriate **External Entity**, (for example, `Devices` , `Device Groups` , or `Users` ).
   4. Select your respective **Collection** in Asset Panda Pro (for example, ITAM).
   5. In the **Mapping & Sync Direction** section, select a **Unique Identifier** from Hexnode and then map it to a unique field in your Asset Panda Pro collection.&#x20;
   6. To map additional fields, select **Add more** and repeat step e.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><ul><li>Each external entity must be configured separately.</li><li>Only fields marked as unique in Asset Panda Pro are available for mapping as a Unique Identifier.</li></ul></div>
10. To filter the records that are updated, click **Filter** <i class="fa-filter">:filter:</i> and specify the filter details. For example, you can filter the integration based on device type.
11. Once your field mapping is complete, click **Save** to activate the integration.

***

## Create an automation in Asset Panda Pro

1. Create an automation for the integration. For **Using**, select **Hexnode**.
2. Configure the sync schedule (optional) and **Trigger type**.

{% hint style="info" %}

* You can schedule the sync to run on a configured schedule or choose **Run now** for the automation to trigger the sync manually.&#x20;
* You can view Automation Logs to review the sync status, records processed, and any errors or failures. See [Activity Stream](/tools/activity-stream.md).
  {% endhint %}

***

## External entities and fields <a href="#external-entities-and-fields" id="external-entities-and-fields"></a>

{% hint style="info" %}
Each external entity must be configured separately.
{% endhint %}

### Device (Primary Entity) fields

Hexnode includes extensive device-level data, including the following fields:

* Device ID, Name, Type
* Serial Number, IMEI, UDID
* OS Name, Version, Platform
* Enrollment details
* Status and compliance
* User association
* Location data

### Other supported entities

Each remaining entity includes its own set of fields available for mapping.

* Device Groups
* Users
* User Groups
* Policies

***

## Troubleshooting <a href="#troubleshooting" id="troubleshooting"></a>

<table><thead><tr><th width="247.77734375" valign="top">Issue</th><th valign="top">Resolution</th></tr></thead><tbody><tr><td valign="top">Sync does not work</td><td valign="top"><ul><li>Verify the <strong>Portal URL</strong> and <strong>API Key</strong>.</li><li>Revalidate the connection.</li><li>Check the field mappings.</li></ul></td></tr><tr><td valign="top">Data is not updated</td><td valign="top"><ul><li>Ensure the correct unique identifier is selected.</li><li>Confirm mapping is aligned with Hexnode fields.</li></ul></td></tr><tr><td valign="top">Unexpected data</td><td valign="top"><ul><li>Review the filters applied to the integration.</li><li>Validate the source data in Hexnode.</li></ul></td></tr></tbody></table>