Freshservice Integration
You can integrate Freshservice with Asset Panda Pro to enable your teams to sync asset data between both platforms. This connection streamlines IT service management by ensuring asset records in Asset Panda Pro are reflected in Freshservice, improving visibility and reducing manual data entry across systems.
Prerequisites
Active Asset Panda Pro subscription with Administrator access
Administrator permissions in Freshservice to access the API key and domain settings
Freshservice domain and API key, to establish a secure connection between the two systems
Freshservice tasks
Copy your Freshservice API Key
Go to Freshservice and log in with your credentials.
In the upper-right corner, click your profile icon and select Profile Settings. The Profile Settings page is displayed.
Locate your API Key and click the Copy icon to copy the API key. This API key acts as your personal authentication token.
Paste the API key into a secure location. You’ll need it later when connecting Freshservice to Asset Panda Pro.
Find your Freshservice Domain
Your Freshservice domain is the URL you use to access your account. The URL typically follows the format: https://yourcompany.freshservice.com
Copy this domain exactly as it is displayed in your browser's address bar.
Asset Panda tasks
Set up the Freshservice integration
Log into Asset Panda Pro with an administrator account
Navigate to
Settings > Account Management.Expand the appropriate account and module.
Click Manage in the Integrations card.
Select Integrations Store.
In the Freshservice tile, click Add. The Integrations in this module tab is displayed.
In the Freshservice tile, click Configure.
In the URL field, enter the full Freshservice URL (for example,
https://yourcompany.freshservice.com).In the API Key field, paste the Freshservice API key you copied earlier.
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.
Once verified, click Continue with mapping. The Mapping List page is displayed.
Create mappings to define how data flows between Freshservice and Asset Panda Pro:
Click Add mapping option.
For Mapping Name, enter a descriptive name for the mapping. For example:
Freshservice → AP AssetsFor External Entity, select the Freshservice data type you want to sync. See External entities. These entities represent specific record types stored in your Freshservice account.
Select the target Asset Panda Pro Collection where the synced records will be displayed. For example, select Assets to push incoming data into your asset inventory.
Select the Unique Identifier fields to be mapped between Freshservice and Asset Panda Pro. See Unique identifiers.
For Sync Direction, select Push to Asset Panda. This labels Freshservice as the data source, and pushes updates into Asset Panda Pro.
To map additional fields, click Add more and then select the field mappings. See Field mapping and identifier reference.
If needed, click next to External Entity to define filtering conditions. You can limit the records that are synced (for example, only syncing assets from a specific workspace, or tickets tagged with a certain priority) to avoid syncing unnecessary data.
Click Save.
External entities
AWS / Azure / GCP (Disk, Image, LB, Security Group)
Cloud-based infrastructure assets (disks, images, load balancers, security settings)
Backup Service / Hosting Service / Cloud / Email Service
Services tracked in Freshservice related to IT support or infrastructure
Business Service / IT Service / Sales Service / Support Service
Internal or customer-facing service offerings aligned with departments or teams
Services
Generic service records from the Freshservice CMDB
Datacenter / Datastore / Volume / Load Balancer
Infrastructure resources—either physical or virtual—used for operations
Ticket
Freshservice issue, incident, or service request submitted by users
VMware VCenter (Datacenter, Datastore, Disk, Image)
VMware-specific components pulled in via CMDB or integrations
Unique identifiers
A unique identifier is a field used to match records between Freshservice and Asset Panda Pro. It ensures that records are updated rather than duplicated during each sync.
At least one field must be marked as unique in both platforms. Asset Panda Pro will use this field to determine whether to update an existing record or create a new one. For best results, use Asset Tag as the unique identifier in both systems. This field is typically standardized, required, and unique across your asset records.
Field mapping and identifier reference
Use the field mapping section to match fields from Freshservice to fields in Asset Panda Pro.
Fields must be of compatible data types to sync successfully.
Asset Tag
Unique identifier for the asset
Recommended for unique ID if used consistently
Display Name
The name assigned to the asset
Map for display or identification purposes
Asset Type
Category or classification of the asset
Map to differentiate asset groups
Model
Manufacturer-defined model of the asset
Map to track model-specific inventory
Manufacturer
Vendor or OEM of the asset
Map for vendor-based reporting
Serial Number
Manufacturer-assigned serial number
Recommended for device-level uniqueness
Status
Lifecycle status (In Use, Retired, etc.)
Map for asset availability or compliance tracking
Assigned To
User currently assigned to the asset
Map for ownership reference
Department
Owning or using the department
Map for department-based filtering or reporting
Location
Asset’s physical or organizational location
Map for inventory audits
Purchase Date
Date of asset acquisition
Map for lifecycle and depreciation tracking
Warranty Expiry
Warranty end date
Map for warranty renewal or expiration tracking
Created At
Date the asset record was created
Map for auditing or reporting
Updated At
Date of last update to the asset record
Map for last activity tracking
Custom Fields
Organization-specific fields defined in Freshservice
Map where custom business logic is required
Last updated