Boolean Conditions
Intro
The condition node allows you to make decision based on the result of a boolean expression.
The conditions node can be used to control your endpoint's path and it's basically used to triggered other nodes.
How this node works
this node is will run a boolean expression on the operator and the two operands you give it. it will trigger the next trigger if the expression result is true and the falseTrigger if the expression result is false.
Node properties
- name: Node names should be unique and can't be changed. 
- Configuration: - #1 value (first operand): See valid operands. 
- Operator: See valid operators. 
- #2 value (second operand): See valid operands. 
 
- Next: The action that will be triggered if the expression is - true. click on the- next inputto get a list of available triggers.
- False trigger: The action that will be triggered if the expression is - false. click on the- falseTrigger inputto get a list of available triggers.
Valid operands
Operands can be any type of data a boolean expression could take including numbers, strings, and boolean values.
You can use Dynamic variables as operands too. see Dynamic variables.
Valid operators
- =will be turned to- ===
- ==equal
- ===strict equal
- !=not equal
- <less than
- >greater than
Example
In this example We will check if 1 is equal to 3 (and it will return false obviously).
So first you need to give your node a name, in this example We will name it cond1.
Now let's set our configurations:
- We will set the - #1 Valueinput as- 1.
- We will set the - operatorinput as- ===.
- We will set the - #2 Valueinput as- 3.
It's time to set our triggers:
- We will set the - nexttrigger as- "node2"so the node with the name- node2will be called if the expression is true.
- We will set the - falseTriggeras- stopso the flow stops here.
Dynamic variables support
You can use Dynamic variables in the following properties:
- operands (#1 Valueand#2 Value).