We do not place any restrictions on the number of modules your app can work with or the compatibility of modules with each other. In your app manifest, along with this module, you can include any module that you deem fit for your use case.
Important:Currently, only the service_ticket and service_user modules are supported in the MSP variant of Freshservice.
Note:This module is available only for Freshservice new signups after the 31 March, 2026 release. If you have a Freshservice account that signed up before the 31 March, 2026 release, refer to the service_asset module documentation.
What kind of apps can you build for this module?
| App building capabilities (For this module, can you build…) | ||
| ... a front-end app? | ... a serverless app? | ... a full-stack SMI app? |
Yes The app is deployed on the supported product’s left-navigation pane. The app cannot be deployed on any other pages of the product. | Yes The app reacts to app set-up events, external events, or scheduled events. The app cannot react to product-specific events such as, creating a ticket, updating a ticket, creating a conversation, and so on. | Yes The app’s front-end component is accessible from the product’s left-navigation pane. The front-end component cannot be deployed on any other pages of the product. |
Who can access an app built for this module?
An app user with any of the following:
- A stand-alone Freshservice subscription.
- A subscription to any SKU that has Freshservice as one of the products.
For more information, see the SKUs and SKU subscriptions section.
Fundamental interfaces
From our Developer toolkit, what are the fundamental tools that you can use to build an app for this module?
To build an app for this module, you can use the following front-end interfaces and serverless events.