Freshservice Fields and Entities Available for Synchronization

    This page describes the reference of the entities and fields supported for synchronization from the Freshservice instance.

    Fields Supported in Ticket Entity



    #FieldVariableType in Freshservice
    1Summaryentity.summaryString
    2Descriptionentity.descriptionString
    3Typeentity.typeType
    4Statusentity.statusStatus
    5Priorityentity.priorityPriority
    6Labelsentity.labelsSet<Label>
    7Reporterentity.reporterContact
    8Commentsentity.commentsSet<Comments>
    9Attachmentsentity.attachmentsSet<Attachment>
    10Assigneeentity.assigneeContact

    Custom Fields

    Exalate supports the synchronization of the following Freshservice custom fields:

    • Single-line text
    • Multi-line text
    • Multi-line dropdown
    • Checkbox
    • Dropdown
    • Date
    • Number
    • Decimal
    • Dependent fields

    Please note that while Date, Dropdown, and Checkbox custom fields are supported for initial synchronization via replica.customFields.{key}, updates to these fields on the FS side are not reflected on the remote side (e.g., Jcloud). Updating these fields after initial sync does not propagate changes due to limitations in how field key-based mappings handle updates.


    Internal Fields

    Using the entity internal map, any field that is part of the Freshservice REST API can be used for synchronization.

    Example Usage:

    entity.source = 9 entity.group_id = 1070000240345 entity.responder_id = 1070033043760 entity.company_id = 1070000553430

    Any field that is part of the Freshservice REST API can be used in entity internal fields. For a complete list of Freshservice attributes and their descriptions, refer to: Freshservice API Documentation.