Plan and modularise app use-case

We offer boiler-plate templates to quickly create your app files. The app manifest that is created as part of the app files contains app start-up and property parameters. When you build a global app, the app manifest is probably the first touch-point where you would encounter modules.

FAQs

How do you benefit from building a modularised app?

Modularising your app enables,

  • Building one app that can be deployed across multiple products based on the SKU subscription of the app user. If the SKU subscription of the app user changes, the deployment across compatible modules auto-changes, as the subscription details are fetched dynamically during runtime based on where the app is deployed.
  • Building one app whose app logic can be implemented to function differently for the different products (modules), if necessary.

You have a valid app use-case. You have identified the Freshworks product(s) for which you want to develop this use case into an app (or through this app you are trying to fix gaps in a Freshworks product that you are using). Which modules should you consider building for?

Refer to the following mapping sheet. The sheet maps a product to its functional modules. Click on any module to navigate to the Module’s introduction. The Module introduction topic gives you all the details regarding app building capabilities (whether it's possible to build a front-end app, serverless app, or full-stack SMI app) and the fundamental interfaces we provide to build the apps.

Note:We do not place any restrictions on the number of modules your app can work with or (for most part) the compatibility of modules with each other.

Freshworks productsFunctional modules

Freshdesk

support_email

support_ticket

support_portal

support_agent

support_contact

support_company

Freshservice

service_ticket

service_asset

service_change

service_user

Freshsales Classic

appointment

contact

cpq_document

deal

phone

product

sales_account

task

lead

Freshsales Suite

(Internally, Freshworks CRM)

Important:
  • This former stand-alone product has evolved into a SKU with Freshsales classic, Freshchat, and Freshcaller features bundled together. Evolving products into SKUs helps us to bundle products together without having to migrate too many customer accounts frequently.
  • This table is a mapping of only the core products to its functional modules. Hence, we are not specifying all modules that work with the SKU. We are only specifying how you can modularise the product (Freshworks CRM) features into its corresponding functional units.

appointment

contact

cpq_document

deal

phone

product

sales_account

task

Freshchat

chat_conversation

chat_user

Freshcaller

call

caller_conversation

caller_metrics

caller_agent

notification