# Hexnode Integration

Integrate Asset Panda with Hexnode to sync device and directory data into Asset Panda for centralized asset management.

***

### **Overview**

The Hexnode integration allows you to import and sync data such as devices, users, groups, and policies from Hexnode into Asset Panda.

This is a **one-way integration (Hexnode → Asset Panda)** where data is fetched from Hexnode and created or updated in Asset Panda based on defined mappings.

***

### **Key Features**

* One-way sync from Hexnode to Asset Panda
* Supports multiple external entities:
  * Devices
  * Device Groups
  * Users
  * User Groups
  * Policies
* Field mapping for flexible data transformation
* Optional filtering for targeted data sync
* Manual and scheduled sync supported
* Detailed sync logs available in Automation Logs

***

### **Prerequisites**

Ensure the following before setup:

* Access to the Asset Panda web application
* Admin access to the Integration Store
* Hexnode **Portal URL**
* Hexnode **API Key / Token**
* Required permissions in Hexnode to access entities (devices, users, etc.)

***

### **Adding the Integration**

#### **Step 1: Install from Integration Store**

* Navigate to the **Integration Store** in Asset Panda
* Search for **Hexnode Integration**
* Add the integration to your module

***

### **Configuring the Integration**

#### **Step 2: Enter Connection Details**

* Open the integration configuration
* Provide:
  * **Portal URL**
  * **API Key / Token**
* Validate the connection
* Continue with mapping

***

#### **Step 3: Create Mapping & Select External Entity**

Choose the data type you want to sync from Hexnode:

* Devices (most commonly used)
* Device Groups
* Users
* User Groups
* Policies

***

#### **Step 4: Configure Field Mapping**

Map Hexnode fields to Asset Panda fields.

**Example (Devices)**

You can map fields such as:

* Device Name
* Device ID
* Serial Number
* Model / Model Name
* OS Name / OS Version
* Platform
* User Email / User Name
* Status
* IMEI, UDID, MAC addresses
* Location details (Latitude, Longitude)

***

#### **Step 5: Set Unique Identifier**

Define a unique identifier to prevent duplicate records.

* Recommended:
  * Devices → **Device ID**
  * Other entities → Corresponding **Entity ID** (e.g., User ID, Policy ID)

***

#### **Step 6: Apply Filters (Optional)**

You can filter data before syncing.

For **Devices**, supported filters include:

* Active Status
* Device Type
* Enrollment Status
* Model Name
* OS Name
* Platform

***

#### **Step 7: Save Mapping and Create Automation**

* Save your field mappings
* Create an automation for the integration
* Configure:
  * Sync schedule (optional)
  * Trigger type

***

### **Running Syncs**

#### **Manual Sync**

* Trigger sync manually from the automation list screen

#### **Automated Sync**

* Sync runs based on the configured schedule

***

### **Sync Behavior**

* Data is synced from **Hexnode to Asset Panda only**
* Records are:
  * **Created** if they do not exist
  * **Updated** if a matching record is found using the unique identifier
* If a record is removed from Hexnode:
  * It remains unchanged in Asset Panda

***

### **External Entities and Fields**

#### **Devices (Primary Entity)**

Includes extensive device-level data such as:

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

#### **Other Supported Entities**

* Device Groups
* Users
* User Groups
* Policies

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

***

### **Troubleshooting**

#### **Sync Not Working**

* Verify Portal URL and API Key
* Revalidate connection
* Check field mappings

#### **Data Not Updating**

* Ensure correct unique identifier is selected
* Confirm mapping is aligned with Hexnode fields

#### **Unexpected Data**

* Review filters applied
* Validate source data in Hexnode

***

### **Logs and Monitoring**

* Detailed logs are available in **Automation Logs**
* Logs include:
  * Sync status
  * Records processed
  * Errors and failures

***

### **Notes**

* This is a **one-way integration**; changes in Asset Panda do not sync back to Hexnode
* Filtering is optional and helps limit data volume
* Each external entity must be configured separately
* Sync performance depends on dataset size and API limits


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://prohelp.assetpanda.com/integrations-store/device-management/hexnode-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.