Conditional Rule Improvements (CSV Automations → Data to API)

We introduced several enhancements to the Conditional Rule system inside Automations → CSV → Data to API, improving how conditions are configured and how values are transformed before being sent in the callback.

1. UI Adjustments for Conditional Rule

  • “Value compare” now appears before “Conditional Word”.

  • “Conditional Word” is now a free-text input instead of a dropdown.

  • The required asterisk was removed since the field is optional.

  • The Paragraph (Optional) field was removed entirely.

2. New Output Transformation Logic

A new optional field was added:

 Output Value (Optional)

This field defines what value will be sent in the callback when the condition is TRUE.

Example:
If CSV value = 320 and condition evaluates TRUE → send "chilena" instead of 320.

If the condition is NOT met → always send the original CSV value.

3. Behavior Fix

Previously, when a conditional rule was active, all other CSV fields were incorrectly transformed to true.

This has now been corrected:

  • Only the field with the conditional rule should change its output.

  • All other CSV fields must retain their original values.

  • If Output Value is empty → the field still returns its original CSV value.

4. Supported Logic Operators

The conditional evaluation now supports:

= , != , > , < , >= , <= , contain , not contain , empty , fill

Leave a Comment

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

Scroll to Top

Contact Us

contact with an agent

Use this form to reach our agent quickly. We're here to assist you.


Learn how we handle your information in our Privacy Policy.