Freshworks Developer Docs | Use interface methods

Interface-methods is a mechanism that the developer platform provides, to enable your app to trigger certain actions on the Freshworks product UI.

Using interface methods an app can, on the product UI,

Display certain UI elements such as Modals, Dialog boxes, Confirmation boxes, and Notifications.
Mimic click actions - such as starting or stopping a timer or navigating to specific pages.
Show/Hide certain fields, field values, and elements (such as icons or other relevant information).
Enable/Disable certain buttons.
Set the values of certain fields.

Common interfaces

Your app can trigger these interface actions irrespective of the placeholder where the app is deployed.

Display modals or dialog boxes

From your project’s root, navigate to the app directory and create a <modal or dialog or any-reasonable-name>.html file. In this file, enter the code to render the (front-end of the) .
Navigate to the app.js file. Subscribe to the app.initialized event, through an event listener. When the app is initialized, the parent application (the product on which the app is deployed) passes a client reference to the app.

After app initialization, to display a , use the following method:

Sample app.js

client.interface.trigger("<method-name>", {
  title: "<Dialog box name>",
  template: "<path to the dialog.html file>"
})

<method-name> is showModal or showDialog

The method displays a Modal in an IFrame. Events methods and Interface methods are not supported in a Modal - your app cannot react to click, change, or update events that occur inside a Modal and your app cannot trigger actions on the product UI from the Modal.

Installation parameters, Request method, Data method, and Data storage are supported in modals. If your app uses these methods from modals, in the modal.html file (or in any other equivalent file that you have added), ensure to include the following appclient resource.

<script src="{{{appclient}}}"></script>

ImportantThe modal without backdrop is a beta feature and not available for all Freshdesk accounts.

Modal with backdrop

Modal without backdrop

Use the sample code shown on the right pane, to enable your app to display a Modal, as part of the app logic.

You can retrieve the contextual information pertaining to the parent location from where a modal is triggered by using Instance method - Context. You can use the Instance methods - Send and Receive to enable communication between modals and any other app instance.

Sample app.js

Modal with backdrop

Modal without backdrop

try {
  let data = client.interface.trigger('showModal', {
  title: 'Sample App Form',
  backdrop: true,
  template: './views/modal.html' });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

Notes:

title is optional. Max characters: 30; value is truncated beyond 30. Default value: Modal dialog.

template is mandatory. Specify the path to the HTML file where the code to render the modal’s front-end is present. If no value is specified, an error message is displayed at run time.

nobackdrop is optional. To display a modal without a backdrop, specify the nobackdrop attribute value as true. A modal with a backdrop is displayed if no value is specified for the nobackdrop attribute or if the value is specified as false. The modal without backdrop is only supported for the ticket_sidebar, ticket_requester_info, ticket_top_navigation placeholders.
The modal without backdrop can also be customised with background colors and linked texts. For the displaying linked text in the modal, both linkText and linkUrl attributes should be defined.

showDialog method

The method displays a Dialog box in an IFrame. Events methods and Interface methods are not supported in a Dialog box - your app cannot react to click, change, or update front-end events that occur inside a Dialog box and your app cannot trigger actions on the product UI from the Dialog box.

Installation parameters, Request method, Data method, and Data storage are supported in modals. If your app uses these methods from modals, in the dialog.html file (or in any other equivalent file that you have added), ensure to include the following appclient resource.

<script src="{{{appclient}}}"></script>

Dialog box

Use the sample code shown on the right pane, to enable your app to display a Dialog box, as part of the app logic.

You can retrieve the contextual information pertaining to the parent location from where a Dialog box is triggered by using Instance method - Context. You can use the Instance methods - Send and Receive to enable communication between modals and any other app instance.

Sample app.js

try {
  let data = client.interface.trigger('showDialog', {
  title: 'Sample Dialog',
  template: 'dialog.html' });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

Notes:

title is optional. Max characters: 30; value is truncated beyond 30.
template is mandatory. Specify the path to the HTML file where the code to render the Dialog box is present. If no value is specified, an error message is displayed at run time.

Display confirmation messages

To enable your app to display standard confirmation-message boxes,

Navigate to the app.js file. Subscribe to the app.initialized event, through an event listener. When the app is initialized, the parent application (the product on which the app is deployed) passes a client reference to the app.
After app initialization, to display a confirmation message with default buttons, use the following method:

Sample app.js

 client.interface.trigger("showConfirm", {
   title: "<Confirmation box name>",
   message: "<text message to be displayed seeking confirmation>"
 })

showConfirm method

The method displays a confirmation message box with a title, a message, and the save and cancel buttons. By default, the message box displays the SAVE and CANCEL buttons. You can customize the button names.

Time-out information:Timeout for Confirmation message box is 10 seconds.

Use the sample code shown on the right pane > Default buttons tab, to enable your app to display a Confirmation message box (with SAVE and CANCEL buttons), as part of the app logic.

Confirmation message box - Default

Confirmation message box - Custom

Confirmation message box - Default buttons

Sample app.js

Default buttons

Custom buttons

try {
  let result = await client.interface.trigger("showConfirm", {
    title: "Confim", // plain text
    message: "Are you sure you want to save the details?" // plain text
  });
  console.log(result);
    /* "result" will be either "Save" or "Cancel" */
} catch (error) {
    // failure operation
  console.error(error);
}

Notes:

title is optional. Max characters: 30; value is truncated beyond 30.
message is mandatory. Max characters: 100; value is truncated beyond 100. If no value is specified, an error message is displayed at run time.
saveLabel and cancelLabel are optional. Max characters: 11

Display notifications

To enable your app to display notifications,

Navigate to the app.js file. Subscribe to the app.initialized event, through an event listener. When the app is initialized, the parent application (the product on which the app is deployed) passes a client reference to the app.

After app initialization, to display a notification, use the following method:

Sample app.js

 client.interface.trigger("showNotify", {
   type: “<Possible values: info, success, warning, danger, alert>”,
   title: "<Display name>",
   message: "<text message to be displayed in the notification box>"
 }
)

showNotify method

The method displays a notification box with a title and notification message (can be which, if ignored, can fail the system).

Use the sample code shown on the right pane, to enable your app to display various notification messages, as part of the app logic.

info

success

warning

danger

alert

Notification box with an info message

Sample app.js

info

success

warning

danger

alert

try {
  let data = await client.interface.trigger("showNotify", {
    type: "info",
    title: "Notice!!",
    message: "Notice!! This ticket has been escalated."
    /* The "message" should be plain text */
  });
    console.log(data); // success message
} catch (error) {
    // failure operation
    console.error(error);
}

Notes:

type is mandatory. Possible values: . If an incorrect value is entered or if no value is specified, an error message is displayed at run time.
title is optional. Max characters: 30; value is truncated beyond 30.
message is mandatory. Max characters: 100; value is truncated beyond 100. If no value is specified, an error message is displayed at run time.

Open ticket or contact details page

To enable your app to open the ticket or contact details pages,

Navigate to the app.js file. Subscribe to the app.initialized event, through an event listener. When the app is initialized, the parent application (product on which the app is deployed) passes a client reference to the app.
After app initialization, to open specific pages, use the following method:
Sample app.js
```
client.interface.trigger("click", {
  id: "<ticket or contact>",
  value: <id of the ticket to be opened>
})
```
id: “ticket” opens the Ticket details page of the ticket whose ticket-id is specified in value.
id: “contact” opens the Contact details page of the contact whose contact-id is specified in value.

click method

The method opens the ticket or contact details page of a specific ticket or contact. Use the sample code shown on the right pane, to enable your app to open the ticket or contact details page.

Sample app.js

Open ticket page

Open contact page

try {
  let data = await client.interface.trigger("click", {
    id: "ticket",
    value: 1
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

Display or hide CTI dialler

To enable an app deployed at the cti_global_sidebar to open or hide a phone dialler,

Navigate to the app.js file. Subscribe to the app.initialized event, through an event listener. When the app is initialized, the parent application (product on which the app is deployed) passes a client reference to the app.
After app initialization, to open or hide the dialler in an iFrame, use the following method:
Sample app.js
```
client.interface.trigger("<show or hide>", {
  id: "softphone"
})
```

show or hide method - for dialler

Use the sample codes shown on the right pane, to enable your CTI app to open or hide the phone dialler in an iFrame.

Sample app.js

Show dialler

Hide dialler

try {
  let data = await client.interface.trigger("show", {
    id: "softphone"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

Display or hide missed calls

To enable an app deployed at the cti_global_sidebar to display or hide the number of missed calls on the CTI widget,

Navigate to the app.js file. Subscribe to the app.initialized event, through an event listener. When the app is initialized, the parent application (product on which the app is deployed) passes a client reference to the app.
After app initialization, to display or hide the number of missed calls, use the following method:
Sample app.js
```
client.interface.trigger("<show or hide>", {
  id: "missedCall"
})
```

Use the sample codes shown on the right pane, to enable your CTI app to display or hide the number of missed calls on the CTI widget.

Sample app.js

Show missed calls

Hide missed calls

try {
  let data = await client.interface.trigger("show", {
    id: "missedCall"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

Ticket details page - possible app actions

Hide/display or enable/disable UI elements

To enable your app to hide an UI element, display a hidden element, disable a UI button, or enable a disabled button,

Navigate to the app.js file. Subscribe to the app.initialized event, through an event listener. When the app is initialized, the parent application (the product on which the app is deployed) passes a client reference to the app.
After app initialization, to a hide/display or enable/disable UI element, use the following method:
app.js
```
client.interface.trigger("<method-name>", {
  id: "<element-name>"
})
```
<method-name> is the action to be performed. Possible values: hide, show, enable, disable
<element-name> is the element to be hidden or displayed; disabled or enabled.

Set the value of a field

To enable your app to set the value of a UI field,

Navigate to the app.js file. Subscribe to the app.initialized event, through an event listener. When the app is initialized, the parent application (the product on which the app is deployed) passes a client reference to the app.
After app initialization, use the following method:
app.js
```
client.interface.trigger("setValue", {
  id: "<element-name>",
  value: "<value to be set>"
})
```
<element-name> is the element whose value is to be set.

Set the options of a drop-down field

To enable your app to set the options of a drop-down UI field,

Navigate to the app.js file. Subscribe to the app.initialized event, through an event listener. When the app is initialized, the parent application (the product on which the app is deployed) passes a client reference to the app.
After app initialization, use the following method:
app.js
```
client.interface.trigger("setOptions", {
  id: "<element-name>",
  value: [value1, value2]
})
```
<element-name> is the element whose drop-down list is to be populated.
[value1, value2] are the drop-down options, specified as an array.

Mimic click actions

A button click on the product UI, performs an action. For example, button clicks can start a timer, stop a timer, expand a collapsed item, open a window, and so on. Your app can mimic certain button clicks and perform the subsequent actions. To enable your app to do this,

Navigate to the app.js file. Subscribe to the app.initialized event, through an event listener. When the app is initialized, the parent application (the product on which the app is deployed) passes a client reference to the app.
After app initialization, to mimic a click action, use the following method:
app.js
```
client.interface.trigger("click", {
  id: "<action to be performed>"
})
```

To start a timer, use the following method:

app.js

client.interface.trigger("start", {
  id: "timer",
  value: {<payload needed for the timer action, specified as an
      object of key:value pairs}})

To stop a timer, use the following method:

app.js

client.interface.trigger("stop", {
  id: "timer"
})

UI elements that the app can act on

attachments

Use the sample code on the right pane, to hide attachments or display already hidden attachments.

This image highlights the element the app can act on

Sample app.js

Show attachments

Hide attachments

try {
  let data = await client.interface.trigger("show", {
    id: "attachments"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

attachmentsDelete

Use the sample code on the right pane, to hide or display the delete icon that helps to remove attachments.

This image highlights the element the app can act on

Sample app.js

Show delete icon

Hide delete icon

try {
  let data = await client.interface.trigger("show", {
    id: "attachmentsDelete"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

ticketSpam

Use the sample code on the right pane, to hide the Spam menu-option from the menu shown in the following image.

This image highlights the element the app can act on

Sample app.js

Show Spam option

Hide Spam option

try {
  let data = await client.interface.trigger("show", {
    id: "ticketSpam"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

ticketEdit

Use the sample code on the right pane, to hide, display, disable, or enable the (ticket) Edit icon.

This image highlights the element the app can act on

Sample app.js

Show Edit icon

Hide Edit icon

try {
  let data = await client.interface.trigger("show", {
    id: "ticketEdit"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

Enable Edit icon

Disable Edit icon

try {
  let data = await client.interface.trigger("enable", {
    id: "ticketEdit"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

ticketDelete

Use the sample code on the right pane, to hide or display the Delete menu-option from the menu shown in the following image.

This image highlights the element the app can act on

Sample app.js

Show Delete option

Hide Delete option

try {
  let data = await client.interface.trigger("show", {
    id: "ticketDelete"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

ticketDueBy

The product UI has an Edit link that enables editing the Resolution due by date associated with a ticket. The link is highlighted in the following image. Use the sample code on the right pane, to enable your app to hide or display this link.

This image highlights the element the app can act on

Sample app.js

Show Edit link

Hide Edit link

try {
  let data = await client.interface.trigger("show", {
    id: "ticketDueBy"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

reply

Use the sample code on the right pane, to hide/display or disable/enable the Reply button in the top and bottom tool bar of the conversation window.

This image highlights the element the app can act on

Sample app.js

Show Reply button

Hide Reply button

try {
  let data = await client.interface.trigger("show", {
    id: "reply"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

Disable Reply button

Enable Reply button

try {
  let data = await client.interface.trigger("show", {
    id: "reply"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

note

Use the sample code on the right pane, to hide/display or disable/enable the Add note button in the top and bottom tool bar of the conversation window.

This image highlights the element the app can act on

Sample app.js

Show Add note button

Hide Add note button

try {
  let data = await client.interface.trigger("show", {
    id: "note"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

Enable Add note button

Disable Add note button

try {
  let data = await client.interface.trigger("enable", {
    id: "note"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

forward

Use the sample code on the right pane, to hide/display or disable/enable the Forward button in the top and bottom tool bar of the conversation window.

This image highlights the element the app can act on

Sample app.js

Show Forward button

Hide Forward button

try {
  let data = await client.interface.trigger("show", {
    id: "forward"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

Enable Forward button

Disable Forward button

try {
  let data = await client.interface.trigger("enable", {
    id: "forward"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

noteEdit

For a conversation on the Ticket Details page, an Edit icon is displayed for all notes added to the conversation. Use the sample code on the right pane, to enable your app to hide/display this icon (for all notes).

This image highlights the element the app can act on

Sample app.js

Show Note Edit icon

Hide Note Edit icon

try {
  let data = await client.interface.trigger("show", {
    id: "noteEdit"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

timer

An agent working on a ticket can choose to record the time spent on the ticket. The agent can use the timer available on the product UI, to do this. Your app can mimic the agent’s actions, and start or stop a running timer. If the app starts a timer when a timer is already running, the running timer is stopped and a new timer is started.

Use the sample code on the right pane, to enable your app to start or stop a timer.

This image highlights the element the app can act on

Sample app.js

Start timer

Stop timer

try {
  let data = await client.interface.trigger("start",
  {
    id: "timer",
    value: {
      agent: user_id,
      billable: true,
      note: "text"
    }
  })
  .then(function(data) {
    // data - success message
  }).catch(function(error) {
    // error - error object
  });
}

Note:value is the payload needed for the timer, specified as an object of key:value pairs.

expandConversation

In a ticket thread, if the number of replies and notes exceed a certain limit, the older replies and notes are in collapsed format. Use the sample code on the right pane, to enable your app to expand the collapsed items and let an agent view the entire conversation.

Sample app.js

try {
  let data = await client.interface.trigger("click", {
    id: "expandConversation"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

The product UI displays all ticket properties in the PROPERTIES widget of the Ticket details page. The PROPERTIES widget is highlighted in the image.

This image highlights the Properties widget

An app can act on the following elements (fields) of the PROPERTIES widget.

Field (default display) name	Element name to be used in app.js
Status	status
Priority	priority
Type	ticket_type
Group	group
Product	product
Custom field	cf_custom_field
Tags	tag

Use the sample code on the right pane, with the appropriate element name, to hide, display, disable, or enable these fields.

Sample app.js

Show field

Hide field

Enable Field

Disable Field

try {
  let data = await client.interface.trigger("show", {
    id: "<element-name>"
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

Note:Possible values of <element-name>: status, priority, ticket_type, group, product, cf_custom_field, tag

setValue: Your app can set a value for a PROPERTIES widget field. Use the sample code on the right pane with the appropriate element name, to set a field’s value.

Sample app.js

client.interface.trigger("setValue", {
  id: "<element-name>",
  value: "<value to be set>"
  })
  .then(function(data) {
    // data - success message
  }).catch(function(error) {
    // error - error object
});

Note:Possible values of <element-name>: status, priority, ticket_type, group, agent, product, cf_custom_field

setOptions: All PROPERTIES widget fields are drop-down fields. Your app can set all the options of a drop-down field. Use the sample code on the right pane with the appropriate element name, to do this.

Sample app.js

try {
  let data = await client.interface.trigger("setOptions", {
    id: "<element-name>",
    value: [value1, value2]
  });
  console.log(data); // success message
} catch (error) {
    // failure operation
  console.error(error);
}

Notes:

Possible values of <element-name>: status, priority, ticket_type, group, agent, product, cf_custom_field
[value1, value2] are the drop-down options, specified as an array.

Log time window fields

An agent working on a ticket can choose to record the time spent on the ticket. The agent can do this by navigating to the Ticket Details page > TIME LOGS widget > Log time window. An app can act on the following elements (fields) of the Log time window.

Field (default display) name	Element name to be used in app.js
Billable	timerBillable
Agent	timerAgentId
Note	timerNote
HH:MM	timerSetTime
On	timerExecuteAt

This image highlights the Log time window fields that the app can act on.

Important: Only an app deployed at the time_entry_backgroud placeholder can act on the Log time window fields. Use the sample code on the right pane, with the appropriate element name, to enable your app to hide/display or disable/enable the Log time window fields.

Sample app.js

Show field

Hide field

Enable field

Disable field

client.interface.trigger ("show", {id: "<element-name>"})
.then(function(data) {
  // data - success message
}).catch(function(error) {
  // error - error object
});

Note:Possible values of <element-name>: timerBillable, timerAgentId, timerNote, timerSetTime, timerExecuteAt

setValue: Your app can set a value for a Log time window field. Use the sample code on the right pane with the appropriate element name, to set a field’s value.

Sample app.js

client.interface.trigger("setValue", {
  id: "<element-name>",
  value: "<value to be set>"})
  .then(function(data) {
    // data - success message
  }).catch(function(error) {
    // error - error object
});

<element-name> can be one of the following:

timerBillable boolean
timerAgentIdinteger
timerNotestring
timerSetTimestring
Examples: “1”, “1.5” If this value is blank, timerExecuteAt is auto set to the current date and your app cannot modify the timerExecuteAt value.
timerExecuteAtdate
Format: DD/MMM/YYYY or DD-MMM-YYYY

Editor window fields

When an agent replies or adds a note to a ticket, the Reply or Note editor is displayed. The app can act on the following elements of the Editor window.

Field (default display) name	Element name to be used in app.js
From	from
To	to
Cc	cc
Bcc	bcc

This image highlights the Editor window elements that the app can act on.

Use the sample code on the right pane, with the appropriate element name, to hide, display, disable, or enable these fields.

Sample app.js

Show field

Hide field

Enable field

Disable field

client.interface.trigger ("show", {id: "<element-name>"})
.then(function(data) {
  // data - success message
}).catch(function(error) {
  // error - error object
});

Note:Possible values of <element-name>: from, to, cc, bcc

setValue: Your app can set a value (or multiple values) for an Editor window field. Use the sample code on the right pane with the appropriate element name, to set a field’s value.

Sample app.js

client.interface.trigger("setValue", {
  id: "<element-name>",
  value: ["value"]})
    .then(function(data) {
      // data - success message
  }).catch(function(error) {
      // error - error object
});

    // For multiple values
client.interface.trigger("setValue", {
  id: "<element-name>",
  value: ["value_1", "value_2"..]})
    .then(function(data) {
        // data - success message
    }).catch(function(error) {
        // error - error object
});

Note:Possible values of <element-name>: from, to, cc, bcc

Open the reply editor window with a text insert

Use the sample code on the right pane, to enable your app to mimic a click action on the Reply button and open the reply editor window with a text inserted in the window. If the window has an existing text by default, this app action replaces the text.

Note:If the ticket.replyClick event method is used in app.js, this interface method triggers the event method and invokes the associated callback.

This image shows the reply editor with a text insert

This image highlights the reply editor with a text insert

Sample app.js

client.interface.trigger("click", {
  id: "reply",
  text: "Text to be inserted"})
  .then(function(data) {
    // data - success message
}).catch(function(error) {
    // error - error object
});
client.interface.trigger("click", {
  id: "reply"
})

Reply without the show-quoted-text link

Use the sample code on the right pane, to enable your app to remove the show-quoted-text element from a reply. If this interface method is triggered before the Reply Editor window is opened, the Reply Editor window does not contain the show-quoted-text element. If this method is triggered after the Reply Editor window is opened, the window has the element but it is removed from the reply sent.

Note:If the ticket.replyClick event method is used in app.js, this interface method triggers the event method and invokes the associated callback.

This image highlights the show-quoted-text element that the app acts on

Sample app.js

client.interface.trigger("click", {
  id: "deleteQuotedText"
  })
  .then(function(data) {
    // data - success message
  }).catch(function(error) {
    // error - error object
});
client.interface.trigger("click", {
  id: "reply"
})

Open the note editor window with a text insert

Use the sample code on the right pane, to enable your app to open the note editor window with a text inserted in the window. If the window has an existing text by default, this app action replaces the text.

Note:If the ticket.notesClick event method is used in app.js, this interface method triggers the event method and invokes the associated callback.

This image highlights the note editor with a text insert

Sample app.js

client.interface.trigger("click", {
  id: "note",
  text: "<Text to be inserted>",
  isPublic: true
  }).then(function(data) {
      // data - success message
  }).catch(function(error) {
      // error - error object
});

setValue of noteType - A note added to a conversation can be a public or private note. These are the note’s types. Your app can set a value for the note type in the Note Editor window. Use the sample code on the right pane, to enable your app to set a note’s type. The app user can modify the set note-type as the other type is also available for app user’s consumption.

This image highlights the note type options

Sample app.js

client.interface.trigger("setValue", {
  id: "noteType",
  value: "<public or private>"
    }).then(function(data) {
      // data - success message
    }).catch(function(error) {
      // error - error object
});
client.interface.trigger("click", {
  id: "note"
})

setOptions of noteType - A note added to a conversation can be a public or private note. These are the note’s types. Your app can set options for the note type in the Note Editor window. Use the sample code on the right pane, to enable your app to do this. If only one option is set, the app user cannot modify the set note-type as the other type is hidden.

This image highlights the note type options

Sample app.js

//set one option and hide the other
client.interface.trigger("setOptions", {
  id: "note",
  value: ["<public or private>"]})
  .then(function(data) {
    // data - success message
  }).catch(function(error) {
      // error - error object
});

setValue of Notify to - When an agent adds a note to a conversation, the agent can add the email-id(s) to which a notification is sent. Your app can set the value(s) of this Notify to field. Use the sample code on the right pane, to enable your app to set the value(s) of the Notify field.

This image highlights the Notify field whose value the app can set

Sample app.js

client.interface.trigger("setValue", {id: "note", toAddress: "value"})
  .then(function(data) {
    // data - success message
  }).catch(function(error) {
    // error - error object
  });

// For multiple values
client.interface.trigger("setValue", {id: "note", toAddress: "value_1, value_2"})
  .then(function(data) {
    // data - success message
  }).catch(function(error) {
    // error - error object
  });

// To clear the field
client.interface.trigger("setValue", {id: "note", toAddress: ""})
  .then(function(data) {
    // data - success message
   }).catch(function(error) {
    // error - error object
   });

setValue of the text box in an already open Editor window - Use the sample code on the right pane, to enable your app to add to or replace the existing text in an already open Editor window. The Editor window can be a Reply, Note, or Forward Editor window. The app can also add attachments.

Important:Only an app deployed at the ticket_conversation_editor placeholder can setValue of an already open editor.

Sample app.js

client.interface.trigger("setValue", {
  id: "editor",
  text: "<Text to be inserted>",
  replace: false, position: "end"
  }).then(function(data) {
    // data - success message
  }).catch(function(error) {
    // error - error object
});

Notes:

replace is optional, boolean. Specifies whether to add to or replace the existing text.
Default value: false.
position is optional. Specified whether to place the new text at the end or at the start of the existing text. Possible values: end, start. Default value: start.

The product UI displays the contact details, of the contact associated with a ticket, in the CONTACT DETAILS widget of the Ticket details page.

This image highlights the CONTACT DETAILS widget

An agent can use the Edit icon, in the expanded widget and view the Edit contact details window.

Edit contact icon

Edit contact details window

This image highlights the Edit contact option.

An app can act on the following elements (fields) of the CONTACT DETAILS widget and the Edit contact details window. The app can also act on the company details associated with the contact.

Important:

If an app hides/shows or disables/enables an element in the Edit contact details window, it is unavailable/available in the CONTACT DETAILS widget too.
The CONTACT DETAILS widget contains fields with contact information and company information. To identify the appropriate field, specify the context when specifying the element names, in the interface methods. The field context can be contact.<element-name> or company.<element-name>. If no context is passed and only <element-name> is used in the interface method definition, the method acts on the fields with the same name on the Ticket Details page > PROPERTIES widget.

Field (default display) name	Context and element name to be used in app.js
Contact fields
Tags	contact.tags
Unique external ID	contact.unique_external_id
Mobile Phone	contact.mobile
Email	contact.email
Twitter	contact.twitter_id
Address	contact.address
Phone Number	contact.phone
Language	contact.language
About	contact.description
Time zone	contact.time_zone
Any custom field (Corresponding element name: element_name)	contact.element_name
Company fields
Description	company.description
Notes	company.note
Domains for this company	company.domains
Health Score	company.health_score
Account Tier	company.twitter_id
Renewal Date	company.renewal_date
Industry	company.industry
Any custom field (Corresponding element name: element_name)	company.element_name

Use the sample code on the right pane, with the appropriate element name, to hide, display, disable, or enable these fields.

Sample app.js

Show field

Hide field

Enable field

Disable field

client.interface.trigger("show", {id: "<contact or company>.<element-name>"})
  .then(function(data) {
    // data - success message
}).catch(function(error) {
    // error - error object
});

Notes:

Possible values of <element-name> for contact fields: tags, unique_external_id, mobile, email, twitter_id, address, phone, language, description, time_zone
Possible values of <element-name> for company fields: description, note, domains, health_score, twitter_id, renewal_date, industry

Tutorials

Sample apps

Guides

Blogs

Assist catalog

Events

Use interface methodsOn this page

Common interfaces

Display modals or dialog boxes

showModal method

showDialog method

Display confirmation messages

showConfirm method

Display notifications

showNotify method

Open ticket or contact details page

click method

Display or hide CTI dialler

show or hide method - for dialler

Display or hide missed calls

show or hide method - for the number of missed calls on the CTI widget

Ticket details page - possible app actions

Hide/display or enable/disable UI elements

Set the value of a field

Set the options of a drop-down field

Mimic click actions

UI elements that the app can act on

attachments

attachmentsDelete

ticketSpam

ticketEdit

ticketDelete

ticketDueBy

reply

note

forward

noteEdit

timer

expandConversation

PROPERTIES widget fields

Log time window fields

Editor window fields

Open the reply editor window with a text insert

Reply without the show-quoted-text link

Open the note editor window with a text insert

CONTACT DETAILS widget and Edit contact details window fields

Use interface methods