Mulesoft Creating Custom Notifications in MuleSoft with CloudHub Connector

Creating Custom Notifications in MuleSoft with CloudHub Connector

In the realm of integration, efficient communication is the key to success. MuleSoft, a renowned integration platform, not only facilitates seamless interactions between systems but also empowers users to send personalized notifications through its CloudHub Connector. What’s more, even if you lack access to an external email hosting service, MuleSoft’s CloudHub Alerts feature can come to your rescue. In this comprehensive guide, we will take you through the process of dispatching tailor-made email notifications to user groups, covering everything from general information to critical error alerts. So, let’s dive into this step-by-step journey.

The Custom Notification Process:

Creating custom notifications in MuleSoft using the CloudHub Connector involves two fundamental steps:

Step 1: Define the Alerts in Anypoint Platform’s Runtime Manager

Link: Anypoint Platform – Runtime Manager Alerts

Step 2: Configuration in Your Mule Application

Step i: Access Anypoint Platform’s Runtime Manager

To start the process, log in to your Anypoint Platform account and navigate to the Alerts section in the Runtime Manager. This is where you’ll set up the alerts that will trigger your custom notifications.

Step ii: Configure Alert Details

In this step, you’ll provide essential details to configure your custom alert:

a) Alert Name: Give your alert a descriptive name. This name will help you identify the purpose of the alert.

b) Severity Level: Choose the appropriate severity level for your alert, whether it’s Critical, Info, or Warning.

c) Source: Decide whether the alert should apply at the application or server level.

d) Application Type: Select the type of application where your alert should be applied. Options include CloudHub Application, Hybrid Application, or CloudHub 2.0 Application.

e) Applications: Choose the target application(s) for your alert. You can select all applications or specify individual application names.

f) Condition: To trigger a custom notification, select “Custom Application Notification” as the condition.

g) Priority: Define the priority for your alert. You can set it to Any, Info, Warn, or Error, based on specific conditions. For instance, you might trigger an alert when errors occur.

h) Subject and Message: Specify the subject and message content for your custom notification. This is what recipients will see in their email alerts.

i) Recipients: Enter the email addresses or group email IDs of the people you want to notify. You can set multiple recipients or a group email address for convenience.

Step iii: Save the Alert Configuration

After filling in all the required details, make sure to save your custom alert configuration. This completes the alert setup in the Anypoint Platform.

Step iv: Configuration in Your Mule Application

Now that you’ve configured your custom alert in the Anypoint Platform, it’s time to set up your Mule application to send notifications using the CloudHub Connector.

Step v: Configure CloudHub Connector

Inside your Mule application, configure the CloudHub Connector with the following parameters:

Username and Password: Provide the necessary credentials for authentication.

Environment: Specify the environment for CloudHub.

Step vi: Test Connection

Before proceeding, it’s essential to ensure that the CloudHub Connector successfully connects to the platform. Test the connection to verify its functionality.

Step vii: Create a Flow

Set up a flow within your Mule application where you want to trigger the custom notification. This flow will contain the logic that initiates the notification.

Step viii: Configure Create-Notification Connector

Within your flow, use the Create-Notification Connector to send custom notifications. Configure the following parameters:

a) Domain: Specify the name of the application against which the alert will be triggered. This should match the application you selected in the Anypoint Platform

b) Message: Define the custom message you want to send as part of the notification.

c) Custom Properties (optional): If needed, you can add custom properties such as IDs or other relevant details.

d) Priority: Set the priority of the alert, such as WARN, ERROR, or INFO, depending on the nature of the event that triggers the notification.

e) Transaction Id: Assign a unique identifier, like a correlation ID, to the notification trigger event.

Step ix: Trigger the Flow

Now, whenever the designated flow in your Mule application is activated or triggered, it will initiate the custom notification process. This means that when specific conditions are met, your custom notification will be sent.

Step x: Notification

The custom notification you’ve configured will be sent to the email addresses specified in the alert setup on the Anypoint Platform. Recipients will receive the notification containing the subject and message you defined.

By following these meticulously outlined steps, you can create highly customized alerts and notifications within your MuleSoft integration. This process enhances communication and ensures that you and your team can respond promptly to critical events, ultimately leading to the smooth operation of your integrations.


In conclusion, MuleSoft’s CloudHub Connector and the Anypoint Platform’s alerting system provide a robust framework for managing and customizing notifications in your integration projects. Effective communication within your integration architecture is now more accessible than ever. Happy integrating!

Leave a Reply

Your email address will not be published. Required fields are marked *