[ Automations ] - Branches - Expand condition operands in branching logic #17230
Description
🧩 Feature Request [Automations] - Branches - Expand condition operands in branching logic
Description
When creating automations and adding a branch condition, Budibase currently only supports equals and not equals comparisons. This is inconsistent with other areas of the platform—such as component visibility bindings—where a broader set of condition operands is available.
Per the Budibase documentation, branching conditions are limited to equality checks. This restricts automation flexibility and forces workarounds for common logic patterns.
Use case
As a systems builder designing tenant workflows and CRM automations, I often need to branch logic based on more nuanced conditions. For example:
- Check if a string starts with a prefix
- Determine if a field is empty or not
- Compare numeric values (e.g. greater than, less than)
- Match against a list of values (
is in,is not in) - Evaluate boolean flags directly
These conditions are already supported in component bindings and visibility logic. Bringing parity to automations would reduce friction and improve consistency across the builder.
Expected behavior
In the automation builder, when adding a branch condition:
- Support additional operands:
starts with,contains,is empty,is not empty,is in,is not in,greater than,less than, etc. - Allow comparisons against strings, numbers, booleans, and arrays
- Match the same condition syntax and binding flexibility available in component logic
- Ensure consistent evaluation behavior across all condition contexts
Why it matters
- Improves consistency across Budibase’s logic systems
- Reduces need for workaround flows or nested branching
- Enables more expressive and maintainable automations
- Aligns with Budibase’s low-code philosophy and builder expectations
Screenshots
Current:
Future:
