Contact Free trial Login

Message Property Filter

MuleSoft recommends against deployments to Mule 3.8. Standard Support for this version ended on November 16, 2018, and Mule 3.8 will reach its End of Life on November 16, 2021, when Extended Support ends.

Matches properties on a message.

Minimum Configuration: The Pattern that the filter should match on.

Use a Message Property Filter to route messages using logic based on the values of one or more message properties. Using this filter you can access the message meta-data (that is, the message properties) including transport-specific and user-defined properties. These message properties represent all the meta information about the message that is available from the underlying transport. For example, if you receive a message via a HTTP connector, you can use this filter to check HTTP header values.

The Pattern is expressed as a key/value pair, where the key is the name of the property. For example, to test the http.method is GET, you could write http.method=GET.

By default, the Case Sensitive box is checked, indicating that the comparison is case sensitive. Uncheck this box if you want the comparison to be case insensitive.

You can also limit the filter to the scope of the message. The default scope is outbound. For more information about message scopes, see Mule Concepts.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub