---
schema_version: "1"
id: 1e5a5adb804e7032eaf3938f6e3a4041a12817f0254e104a9b565e778412bbda
title: Notifications Configuration Reference
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/latest/notifications-configuration-reference.md
canonical_url: https://docs.mulesoft.com/mule-runtime/latest/notifications-configuration-reference
source_site: docs.mulesoft.com
content_type: documentation
content_hash: a499d441471a6d972db10c4c4b6c87f4b114c4c10444c15bf0cc9438c5e8c6d2
description: MuleSoft Documentation Site
release: "4.13"
latest: true
---
---
product: Mule Runtime
version: 4.13
is-latest-version: true
keywords: anypoint studio, esb, notifications, error messages, responses, exceptions, monitor
---

# Notifications Configuration Reference

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

This topic provides details on the elements to configure for notifications. For more information on
notifications, see [Mule Server Notifications](https://docs.mulesoft.com/mule-runtime/latest/mule-server-notifications).

## Notifications

Registers listeners for notifications, and associates interfaces with specific events.

### Attributes of Notifications

<table><colgroup><col> <col></colgroup><thead><tr><th>Name</th><th>Description</th></tr></thead><tbody><tr><td><p><code>dynamic</code></p></td><td><p>If the notification manager is dynamic, you can set up the listeners to be registered dynamically at runtime. Otherwise, some parts of Mule will cache the notification configurations for efficiency reasons and will not generate events for newly-enabled notifications or listeners.<br><strong>Type</strong>: <code>boolean</code><br><strong>Required</strong>: no<br><strong>Default</strong>: <code>false</code></p></td></tr></tbody></table>

### Child Elements of Notifications

Use the `notification` and `disable-notification` elements to configure the relationship between
interfaces and events.

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Name</th><th>Cardinality</th><th>Description</th></tr></thead><tbody><tr><td><p><code>notification</code></p></td><td><p>0..*</p></td><td><p>Associates an event with an interface. Listeners that implement the interface receive instances of the event.</p></td></tr><tr><td><p><code>disable-notification</code></p></td><td><p>0..*</p></td><td><p>Blocks the association of an event with a particular interface. This filters events after the association is made with the interface, so it takes precedence over other elements, such as <code>notification-listener</code>.</p></td></tr><tr><td><p><code>notification-listener</code></p></td><td><p>0..*</p></td><td><p>Registers a bean as a listener with the notification system. Events are dispatched by reflection, which means that the listener receives all events associated with the interfaces it implements.</p></td></tr></tbody></table>

## Notification

Associates an event with an interface. Listeners that implement the interface will receive instances
of the event.

### Attributes of Notification

<table><colgroup><col> <col></colgroup><thead><tr><th>Name</th><th>Description</th></tr></thead><tbody><tr><td><p><code>event-class</code></p></td><td><p>The class name of the notification event to deliver to the interface. You can use this instead of the <code>event</code> attribute to specify a custom class.<br><strong>Type</strong>: <code>class name</code><br><strong>Required</strong>: no<br><strong>Default</strong>: none</p></td></tr><tr><td><p><code>event</code></p></td><td><p>The notification event to deliver.<br><strong>Type</strong>: <code>notificationTypes</code><br><strong>Required</strong>: no<br><strong>Default</strong>: none</p></td></tr><tr><td><p><code>interface-class</code></p></td><td><p>The class name of the interface that receives the notification event.<br><strong>Type</strong>: <code>class name</code><br><strong>Required</strong>: no<br><strong>Default</strong>: none</p></td></tr><tr><td><p><code>interface</code></p></td><td><p>The name of the interface that receives the notification event.<br><strong>Type</strong>: <code>notificationTypes</code><br><strong>Required</strong>: no<br><strong>Default</strong>: none</p></td></tr></tbody></table>

There are no child elements for `notification`.

## Disable Notification

Blocks the association of an event with a particular interface. This filters events after the
association is made with the interface, so it takes precedence over other elements, such as
`notification-listener`.

### Attributes of disable-notification

<table><colgroup><col> <col></colgroup><thead><tr><th>Name</th><th>Description</th></tr></thead><tbody><tr><td><p><code>event-class</code></p></td><td><p>The class name of the event that is no longer delivered to an interface. You can use this instead of the <code>event</code> attribute to specify a custom class.<br><strong>Type</strong>: <code>class name</code><br><strong>Required</strong>: no<br><strong>Default</strong>: none</p></td></tr><tr><td><p><code>event</code></p></td><td><p>The event you no longer want to deliver.<br><strong>Type</strong>: <code>notificationTypes</code><br><strong>Required</strong>: no<br><strong>Default</strong>: none</p></td></tr><tr><td><p><code>interface-class</code></p></td><td><p>The class name of the interface that no longer receives the event.<br><strong>Type</strong>: <code>class name</code><br><strong>Required</strong>: no<br><strong>Default</strong>: none</p></td></tr><tr><td><p><code>interface</code></p></td><td><p>The name of the interface that no longer receives the event.<br><strong>Type</strong>: <code>notificationTypes</code><br><strong>Required</strong>: no<br><strong>Default</strong>: none</p></td></tr></tbody></table>

There are no child elements for `disable-notification`.

## Notification Listener

Registers a bean as a listener with the notification system. Events are dispatched by reflection,
which means that the listener receives all events associated with the interfaces it implements.

## Notification Types

You can specify the following types of notifications using the `event` attribute of the
`notification` and `disable-notification` elements:

- ASYNC-MESSAGE

- CONNECTION

- CONNECTOR-MESSAGE

- CONTEXT

- CUSTOM

- EXCEPTION

- EXCEPTION-STRATEGY

- MANAGEMENT

- MESSAGE-PROCESSOR

- PIPELINE-MESSAGE

- ROUTING

- SECURITY

- TRANSACTION