You can build a Freshcaller app by using the following steps.
Node Version Manager (NVM) enables you to install and work with multiple versions of Node.js. You can use NVM to install Node.
- To install NVM:
- Run the following command to verify the NVM installation. $ nvm --version
- To install Node using NVM, run the following command.
$ nvm install 10.18
Note: Support for Node 8.10.x has been deprecated.
- Run the following command to verify the Node installation.
$ node --version
Note: On Windows, if the Node version is not displayed, you should run the nvm on command to enable nvm.
- Run the following command to set the default Node version. $ nvm alias default 10.18
- On Windows, to install the tools and configurations required to start using Node, use the following command. $ npm install --global --production windows-build-tools For more information, see the write-up on node-gyp.
Install the Freshworks CLI
1. Uninstall the previous CLI version by using the npm uninstall fdk -g command.
- Run the following command to install the CLI. Copied Copy
- Run the following command to verify the CLI installation. $ fdk version
|npm install https://dl.freshdev.io/cli/fdk.tgz -g|
Create an App
You can use the following steps to create an app that displays the Freshcaller logo and logged in agent’s email address, in the incoming call notification and conversation window (after a call is established).
- From the command line, navigate to the empty directory in which you want to create an app.
- Run the following command. $ fdk create A prompt to choose a product is displayed.
- Select Freshcaller and press Enter. A new app is created based on the your_first_app template.
The following directories and files are created as a result of the fdk create command.
|app/||Contains all the files required for the front-end component of an app. The JS file follows the ES5 standard.|
|app/icon.svg||Contains the product icon. If you intend to extend the app, you can replace the icon.svg file. The icon file should be of SVG type with a resolution of 64 x 64 pixels.|
|app/template.html||Contains the HTML code required for the app’s UI, which is rendered in an IFrame.|
|config/||Contains the installation parameters and OAuth configuration files.|
|config/iparams.json||Contains all the installation parameters whose values are set when the app is installed. For more information, see Installation Parameters.|
|manifest.json||Contains details about the app and its characteristics.|
|README.md||Contains additional instructions, information, and specifications.|
1. The iparam_test_data.json file has been deprecated. Before testing the app, navigate to http://localhost:10001/custom_configs and enter appropriate values for the configured installation parameters.
2. If you use React, Ember, Vue, or any other front-end framework, include the source files of your app in the src directory, to ensure quick app reviews.
Test the App
- To test your app, use the latest version of Chrome.
- Ensure to sign up for a Freshcaller account.
- From the command line, navigate to the directory that contains the app related files and run the following command. $ fdk run
- Log in to your Freshcaller account.
- To the Freshcaller account URL, append ?dev=true. Example URL: https://domain.freshcaller.com/dashboard?dev=true.
- To allow the Chrome browser to connect to the test server that runs on HTTP,
- On Chrome 79 and higher versions:
- Navigate to Settings -> Advanced -> Privacy and security -> Site settings -> Insecure content.
- In the Allow section, click Add and enter the Freshcaller account URL. Example URL: https://domain.freshcaller.com
- On Chrome 78 and lower versions:
- In the address bar, if a shield icon is displayed, click the icon. A warning message is displayed as the Support portal runs on HTTPS and the test server runs on HTTP.
- Click Load Unsafe Scripts to continue testing.
- On Chrome 79 and higher versions:
- Simulate an incoming call. If the app is successfully created, the Freshcaller icon is displayed on the incoming call notification, as shown in the image.
1. Each component in the coverage summary should be at least 80% for apps to be submitted in Freshworks Marketplace. See Code coverage for more information.
2. If you have any issues when testing your app, attach detailed logs of the output in your support ticket for quick resolution from the support team.
Validate and Pack
To check if the app is error-free and package it for submission, follow the given steps.
To validate the code, run the following command.
$ fdk validate [--app-dir DIR]
Here, DIR is the relative or absolute path to the app directory. If there are errors in the code, corresponding violations are displayed. To auto-fix certain errors and display only those that need manual fixing, use the $fdk validate --fix command. Ensure to fix all violations before packing the app.
- To pack the app for submission, run the following command. $ fdk pack [--app-dir DIR] The command generates the dist/<app_directory>.zip file.
- To publish the app to the Freshworks Marketplace, navigate to the Freshcaller developer portal and upload the packed file. For more information on the app submission process, see Types of Apps.