Skip to content

Resolve conditions

This plugin returns results with a resolved condition set, designed to evaluate specific conditions within a workflow and provide outcomes based on these evaluations.




The Resolve conditions plugin operates by taking a set of user-defined conditions and evaluating them against provided data. Each condition is assessed to determine if it is true or false. For instance, you might want to check if a profile has given marketing consent or if the current weather condition is rain. The plugin processes these conditions and returns an object indicating the outcome of each condition.

The plugin achieves this by using the Condition class to evaluate each condition against the provided payload. The payload is accessed using a DotAccessor, allowing the plugin to extract specific data points based on dot notation, like Each condition is defined in the plugin's configuration and is checked against the payload. The results are then compiled into an object, with each key representing a condition and its evaluated Boolean value.

Inputs and Outputs

  • Input: The plugin accepts any type of payload as input. This input is used to evaluate the specified conditions.
  • Output: The plugin outputs an object where each key corresponds to a condition, and the value is a Boolean indicating whether the condition was met (true) or not (false).

Example Output:

  "marketing-consent": true,
  "is-it-raining": false


  • Conditions: Key-value pairs where the key is a custom name for a condition and the value is the condition to be evaluated. For example, checking if marketing consent is not empty in a profile ( EMPTY). For the syntax of condition see Tracardi documentation.

JSON Configuration

Example Configuration:

  "conditions": {
    "marketing-consent": " EXISTS",
    "is-it-raining": "lowercase(payload@weather.condition) == 'rain'"

Required resources

This plugin does not require external resources to be configured.


  • "Could not parse the condition {value}. Got error: {str(e)}": This error occurs when the plugin encounters an issue in parsing or evaluating a condition. It might happen if the condition is incorrectly formatted or if the required data is not present in the payload.