Freshworks Command-Line Interface (CLI) enables you to build, test, and package apps to publish them in Marketplace.

As soon as you install the CLI, type fdk to display the supported commands.

The following options are also avaliable.

• For information about a specific command, run the following command. $ fdk COMMAND (-h | --help)
• To obtain detailed logs, run the following command. $ NODE_DEBUG=fdk fdk COMMAND

Create

This command is used to create a Freshservice app. Before executing the create command, ensure that specified or current app directory is empty. $ fdk create [--app-dir DIR] [--products PRODUCT] [--template TEMPLATE]

Options	Usage
--app-dir	Specify the absolute or relative path to the project directory.
--products	Specify the product for which the app is created. If not specified, you will be prompted to select a product.
--template	Specify the template. If not specified, you will be prompted as shown:

Example 1
To create a Freshservice app in the current directory, run the following command.
$ fdk create --products freshservice --template your_first_app The current directory should be empty.

Output
A Freshservice app is created from the your_first_app template with the following files.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
<current_app_directory>
├── README.md
├── app
│   ├── index.html
│   ├── scripts
│   │   └── app.js
│   └── styles
│       ├── images
│       │   └── icon.svg
│       └── style.css
├── config
│   └── iparams.json
└── manifest.json

5 directories, 7 files

Example 2
Run any of the following commands to create default Freshservice sample app directories and files in the myfirstapp directory. $ fdk create --app-dir ./myfirstapp $ fdk create --app-dir /Users/user/myfirstapp The output will be the same as the Example 1.

Generate

This command is used to generate app files with a specific template for an existing app that was created by using the create command.

• After you create an app, run the following command. $ fdk generate The list of the following files is displayed.
• oauth_config.json: Contains the configuration parameters, such as client_id, client_secret, authorize_url, token_url, and account/agent scope, required for OAuth-based authentication.
• iparams.json: Contains the installation parameters, such as iparam name and type of iparam, whose values are set when the app is installed.
• iparams.html: Contains the html code to build the Custom Installation page. You can enter the page title, select the product css to link, and choose to add jquery, fresh_client.js, and iparam.js and iparam.css.
• server.js: Contains the event registration and callback methods. You need to enter the names of the events and callback functions.
• manifest.json: Contains app information such as version, product, location, and so on. You need to select the product and app location.
• Select a file and enter the appropriate parameter values. The corresponding file is generated based on the values.

Run

This command is used to start the local server in order to test your app.

If you are running a serverless app that contains dependencies, the packages defined in manifest.json are automatically installed.
Once you exit testing, the CLI prints a summary of how extensive your testing was. The following coverage summary shows an example of thorough testing.

1
2
3
4
5
6
======================= Coverage summary ========================
Statements   : 98.18% ( 54/55 )
Branches     : 100% ( 4/4 )
Functions    : 84.62% ( 22/26 )
Lines        : 98.18% ( 54/55 )
=================================================================

Note:
Each component in the coverage summary should be at least 80% for apps to be submitted for the App Review process.

Example 1
To run the command from the app project directory, type:

Output

Example 2
To run the command from a different directory, type:
$ fdk run --app-dir /Users/user/myfirstapp The output will be the same as the Example 1.

Example 3
To run the command for a serverless app from a different directory, type:
$ fdk run --app-dir /Users/user/myfirstapp Output $ Starting local testing server at http://*:10001/
Append "dev=true" to your reshservice support URL to start testing
e.g. https://domain.freshservice.com/helpdesk/tickets/1?dev=true
Quit the server with Control-C.

To test the serverless component of your app, visit - http://localhost:10001/web/events

Validate

This command validates whether the app code is error free. If there are errors in the code, corresponding violations are displayed after the command is run.

Pack

This command is used to pack the app project for submission.

Once you execute the pack command, a dist/<appdirectory>.zip file is generated which you need to upload in the Developer portal to publish it in Marketplace.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Sauls-Macbook-Pro:~ user$ tree myfirstapp/
myfirstapp/
├── README.md
├── app
│   ├── app.js
│   ├── freshservice_logo.png
│   ├── icon.svg
│   ├── logo.png
│   ├── style.css
│   └── template.html
├── config
│   ├── iparam_test_data.json
│   └── iparams.json
├── dist
│   └── myfirstapp.zip
└── manifest.json

3 directories, 11 files

Example 1
To run the command from the app project directory, type:$ fdk pack

Output

Example 2
To run the command from a different directory, type:$ fdk pack --app-dir /Users/user/myfirstapp The output will be the same as the Example 1.

Version

This command prints the installed and latest CLI versions.

Output