Get Started with MuleSoft Direct Integrations

The integration assets are out of the box integration templates with pre-built transformations. The integration assets can be used to integrate with external systems and are built on the following TM Forum API:

The TMF620 Product Catalog Management API is used to publish a product offer from Salesforce to a target system through MuleSoft. Following REST operations are supported.

  • POST Offer
  • PATCH Offer To view the integration asset details, prequisites, and post deployment tasks, see MuleSoft Exchange.

TMF622 provides a standardized mechanism for placing a product order with all of the necessary order parameters. The API consists of a simple set of operations that interact with CRM/Order negotiation systems in a consistent manner. Currently, POST operation is supported.

To view the integration asset details, prequisites, and post deployment tasks, see MuleSoft Exchange.

This API was tested with an external system that required TMF-aligned customizations. It may not include all optional fields and may not work out-of-the-box with your systems. We recommend a thorough evaluation and implementing any necessary customizations to ensure compatibility with your setup.

The Service Order Management API provides a standardized mechanism for placing a service order with all of the necessary order parameters. It allows users to create, update & retrieve Service Orders and manages related notifications. A service order will describe a list of service order items.
To view the integration asset details, prequisites, and post deployment tasks, see MuleSoft Exchange.

The Service Qualification API checks the service availability of a configured service or a list of services at the customer location.
To view this integration asset and its details, see MuleSoft Exchange.
To check if selected products are available in all of the required locations, see Check Serviceability in Communications Cloud Agent Console.

The Geographic Address Management API is used to validate geographic address data, to be sure that it corresponds to a real geographic address.
To view this integration asset and its details, see MuleSoft Exchange.
To select and validate geographic address data using Enterprise Sales Management, see Select, Add, and Validate a Location in Enterprise Sales Management.

TMF674 Geographic Site API provides a standardized mechanism to manage sites by enabling users to create, read, and update them. These sites can be linked to customers, accounts, services, or other entities. A Site in this API represents key locations and is defined in two ways.

  • As a geographic address. For example, street name, number, and city.
  • As a geographic location. For example, coordinates on a map.

To view the integration asset details, prequisites, and post deployment tasks, see MuleSoft Exchange.

TMF675 Geographic Location API provides a standardized mechanism to manage geographic locations, including their associated accuracy and spatial references. To view the integration asset details, prequisites, and post deployment tasks, see MuleSoft Exchange.

To access and use the MuleSoft Direct:

  1. Accept terms and enable access.
  2. Deploy integration assets using Industry Integration Solutions. See Industry Integration Solutions in Salesforce Help.
  3. Extend Integration App.

To know more about the TM Forum APIs, see the Communications Cloud TM Forum API reference.