Freshservice Integration

Integrating Freshservice with Asset Panda allows your teams to sync asset data between both platforms. This connection helps streamline IT service management by ensuring asset records in Asset Panda are reflected in Freshservice, improving visibility and reducing manual data entry across systems.

Prerequisites

To enable the Freshservice integration in Asset Panda, you’ll first need to gather some information from your Freshservice account. This includes your Freshservice domain and your API key, which are required to establish a secure connection between the two systems.

Important: You must be an administrator in Freshservice to access the API key and domain settings required for this integration.


Freshservice Tasks

Sign in to Freshservice

  1. Go to Freshservice and log in with your credentials.

  2. In the top-right corner, click your profile icon and select Profile Settings from the dropdown menu.


Copy Your API Key

  1. On the Profile Settings page, locate your API Key near the top of the page.

  2. Click the Copy icon to copy your API key to your clipboard.

  3. Paste the API key into a secure location—you’ll need it later when connecting Freshservice to Asset Panda.

Note: This API key acts as your personal authentication token.


Find Your Freshservice Domain

  1. Your Freshservice domain is the URL you use to access your account.

  2. The URL typically follows the format: https://yourcompany.freshservice.com

  3. Copy this domain exactly as it appears in your browser's address bar.


Asset Panda Tasks

Setup Freshservice Integration

  1. Log in to Asset Panda.

  2. Navigate to Settings > Account Management.

  3. Under the appropriate module, click Manage under Integrations.

  4. Open the Integrations Store for the desired account.

  5. In the Integration Store, find the Freshservice tile and click Add.

  6. Switch to the Integrations in this module tab.

  7. Locate the Freshservice tile and click Configure.

  8. In the URL field, enter the full Freshservice URL (e.g., https://yourcompany.freshservice.com).

  9. In the API Key field, paste the Freshservice API key you copied earlier.

  10. Click Test and save connection to verify the credentials.

  11. Once verified, click Continue with mapping to proceed.

Note: If the connection is valid, you should see a success message and a green checkmark above the Authentication tab.


Create Mapping

Once the connection is authenticated, you’ll be taken to the Mapping List screen. This is where you define how data flows between Freshservice and Asset Panda.

  1. Click Add mapping option to create a new mapping.

  2. Mapping Name

    • Enter a descriptive name for the mapping.

    • Example: Freshservice → AP Assets

  3. External Entity

    • Select the Freshservice data type you want to sync from the dropdown.

    • These entities represent specific record types stored in your Freshservice account:

    • Available External Entities

  4. AWS / Azure / GCP (Disk, Image, LB, Security Group)

    • Cloud-based infrastructure assets (disks, images, load balancers, security settings).

  5. Backup Service / Hosting Service / Cloud / Email Service

    • Services tracked in Freshservice related to IT support or infrastructure.

  6. Business Service / IT Service / Sales Service / Support Service

    • Internal or customer-facing service offerings aligned with departments or teams.

  7. Services

    • Generic service records from the Freshservice CMDB.

  8. Datacenter / Datastore / Volume / Load Balancer

    • Infrastructure resources—either physical or virtual—used for operations.

  9. Ticket

    • Any Freshservice issue, incident, or service request submitted by users.

  10. VMware VCenter (Datacenter, Datastore, Disk, Image)

    • VMware-specific components pulled in via CMDB or integrations.

  11. Collection

    • Choose the target Asset Panda collection where the synced records will appear.

    • Example: Select the Assets collection to push incoming data into your asset inventory.

  12. Sync Direction

    • Select Push to Asset Panda. This means Freshservice is the data source, and updates are pushed into Asset Panda.

  13. Filters (optional)

    • Click the filter icon next to the external entity dropdown to define filtering conditions.

    • Filters allow you to limit which records are synced—for example, only syncing assets from a specific workspace, or tickets tagged with a certain priority.

    • Use filters to reduce noise and avoid syncing unnecessary data.


Unique Identifier Mapping Table

The unique identifier is a field used to match records between Freshservice and Asset Panda. 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 will use this field to determine whether to update an existing record or create a new one.

Platform
Recommended Unique Identifier

Freshservice

Asset Tag or ID

Asset Panda

Asset Tag (must be unique)

Recommendation: 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. Fields must be of compatible data types to sync successfully.

Field Name
Description
Mapping Guidance

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

Once your field mapping is complete, click Save to activate the integration.

Last updated