Product events

Product events are events such as creating a change, updating a change, and so on, that occur in the product on which your app is deployed. You can enable product events to trigger your app, call a corresponding callback function, and execute the app logic.

To do this,

  1. From your app’s root directory, navigate to the manifest.json file.

  2. Subscribe to an event by configuring an event listener: Include the events attribute, specifying the product-event's name and the corresponding callback methods as follows:

    manifest.json
     "events": {
       "<productEventName>": {
           "handler": "<eventCallbackMethod>"
       }
     }

    When the event occurs, the corresponding event listener invokes the callback method and passes a standard payload to the method.

  3. Navigate to the server.js file. In the exports block, enter the callback function definition as follows:

    Sample server.js
     exports = {
       // args is a JSON block containing the payload information
       // args["iparam"] will contain the installation parameter values
       //eventCallbackMethod is the call-back function name specified in manifest.json
       eventCallbackMethod: function(args) {
         console.log("Logging arguments from the event: " + JSON.stringify(payload));
       }};
Notes:
  • The serverless component of the app is executed in a sandbox mode where some methods, such as setTimeout and setInterval, cannot be used.
  • The default app execution timeout is 20 seconds. If the request timeout is increased to 20, 25, or 30 seconds, the app execution timeout is extended to 40 seconds.
  • The payload passed to the severless component should not exceed 256 KB.
  • To know all the platform restrictions and constraints, see Rate limits and constraints.
  • Avoid using symbols, such as arrows, in the code when defining the event, as they may cause errors.

Payload attributes

When a product event occurs, an event-specific payload is passed to the callback method.

The payload is a JSON object with the following attributes.

  • app_settingsobject

    Information pertaining to the app settings as a JSON object of key-value pairs.


    If your app does not use the app settings functionality, an empty JSON object is returned.

  • currentHostobject

    A global app, with module-specific app logic, can be deployed on various Freshworks products.


    currentHost contains information pertaining to the Freshworks product on which the app is currently running.

    • subscribed_modulesarray of strings

      All modules that the app user has subscribed to and present in the app manifest.

    • endpoint_urlsobject

      Product name and account url (domain name) of the host where the app can access the product resources, specified as a key (product name) - value (account URL) pairs.


      You can use the domain name to construct api calls that can access product resources.

    • workspacesobject

      Information pertaining to the workspace for which the app is installed. When you specify installation scope in your app manifest, this attribute will be retrieved as a part of the currentHost object in the payload. To learn more about the workspace or client level installation, see Configure app installation scope.

      • freshserviceobject

        Information pertaining to the product for which the workspace is available.

        • idinteger

          Identifier of the workspace or client for which the app is installed.

          Note:This attribute is returned as a part of the currentHost payload at runtime and also in product events, external events, scheduled events, app setup events, and SMI payloads.

  • dataobject

    Event-specific data, specified as a JSON object of key:value pairs.

  • eventstring

    Name of the product event.

  • iparamsobject

    Installation parameters specified as a JSON object of <parameter name>: <parameter value> pairs.

  • regionstring

    Region where the account is deployed.

    Possible values: US, EUN, EUC, AUS, IND, and MEC.

  • timestampnumber

    Timestamp of when the product event occurs, specified in the epoch format.