> For the complete documentation index, see [llms.txt](https://limechatai.gitbook.io/limechat-product-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://limechatai.gitbook.io/limechat-product-guide/whatsapp-marketing/flows/action-nodes/update-freshdesk-ticket-field-with-system-field.md).

# Update Freshdesk Ticket Field with System Field

**Node Name:**\
Update Freshdesk Ticket Field with System Field

***

**What it does:**\
Updates a custom field in an existing Freshdesk ticket by mapping it to a system field value captured within the flow.

***

**When to Use:**

* When you want to sync chatbot/system data into Freshdesk tickets<br>
* To update ticket metadata like order ID, user inputs, or conversation attributes<br>
* When enriching Freshdesk tickets for better agent context<br>
* After ticket creation or during ticket updates in a flow<br>

***

**UI Inputs:**

* **Freshdesk Integration**
  * Type: Fixed (pre-configured)<br>
  * Required: Yes<br>
  * Description: Specifies the Freshdesk account to use<br>
  * Special Behavior: Pre-filled and not editable<br>
* **Field**
  * Type: Dropdown (dynamic, server-fetched)<br>
  * Required: Yes<br>
  * Description: Select the Freshdesk ticket field you want to update<br>
  * Special Behavior:
    * Fetches available ticket fields from Freshdesk<br>
    * Refresh option to reload latest fields<br>
* **Value**
  * Type: Dropdown / Dynamic field mapping<br>
  * Required: Yes<br>
  * Description: Select the system field whose value will be pushed into the selected Freshdesk field<br>
  * Special Behavior:
    * Fetches available system/custom fields (CVF fields)<br>
    * Filtered for WhatsApp inbox context<br>

***

**Outputs:**

* **successful**
  * Type: Boolean<br>
  * Meaning:
    * `true` → Field updated successfully in Freshdesk<br>
    * `false` → Update failed<br>

***

**Requirements:**

* **Supported Events:**
  * freshdesk\_ticket\_created<br>
  * freshdesk\_ticket\_updated<br>
* **Required Integrations:**
  * Freshdesk<br>

***

**Notes:**

* Works only if a Freshdesk ticket already exists in the flow context<br>
* Both field and value must be compatible (e.g., correct data type mapping)<br>
* Commonly used after ticket creation to enrich ticket data dynamically<br>
* Relies on proper configuration of Freshdesk custom fields and system fields beforehand