Bit Integrations – Conditional Logic

Bit Integrations’ Conditional Logic allows you to create dynamic workflows based on specified conditions. You can apply operator conditions like Equal, Not Equal, Is Null, Is Not Null, Contain, Not Contain, Start With, and End With to fields. Logical conditions like Or and And enable combining multiple conditions for decision-making. If conditions are met, data is sent to the chosen action app, otherwise, it’s not. This empowers you to automate actions based on data attributes and relationships, streamlining your processes effectively.

Operator Conditions​

1. Equal: Checks whether the selected field is equal to the set value.

Example: suppose, the first name of the Form/Task field is Equal to “Bitcode,” the data will be sent to your chosen action app. Otherwise, it will not be sent.

2. Not Equal: Checks if the selected field is not equal to the set value.

Example: suppose, the first name of the Form/Task field is Equal to “Bitcode,” the data will be sent to your chosen action app. Otherwise, it will not be sent.

3. Is Null: Checks whether the selected field is empty.

Example: suppose, the first name of the Form/Task field Is Null, the data will be sent to your chosen action app. Otherwise, it will not be sent.

4. Is Not Null: Checks if the selected field is not empty.

Example: suppose, the first name of the Form/Task field Is Not Null, the data will be sent to your chosen action app. Otherwise, it will not be sent.

5. Contain: Checks whether there is a value in the condition of the selected field.

Example: suppose, the first name of the Form/Task field Contains “Bitcode,” the data will be sent to your chosen action app. Otherwise, it will not be sent.

6. Not Contain: Checks whether the condition of the selected field does not contain a value.

Example: suppose, the first name of the Form/Task field does Not Contain “Bitcode,” the data will be sent to your chosen action app. Otherwise, it will not be sent.

7. Start With: Checks whether the selected field starts with a given value.

Example: suppose, the first name of the Form/Task field starts with “S, D, R, T, B, J, L, P,” etc., the data will be sent to your chosen action app. Otherwise, it will not be sent.

8. End With: Checks whether the selected field ends with a given value.

Example: suppose, If the first name of the Form/Task field ends with “w c,n,g, a,o, r,” etc., the data will be sent to your chosen action app. Otherwise, it will not be sent

9. Greater Than (Number): Checks whether a number is Greater Than the given value.

Example: suppose, the Number field of the Form/Task field is Greater Than “10,” the data will be sent to your chosen action app. Otherwise, it will not be sent

10. Less Than (Number): Checks whether a number is less than the given value.

Example: If the Number field of the Form/Task field is Less Than “10,” the data will be sent to your chosen action app. Otherwise, it will not be sent.

11. Greater Than or Equal (Number): Checks whether a number is greater or equal to the given value.

Example: suppose, the Number field of the Form/Task field is Greater Than or Equal to “10,” the data will be sent to your chosen action app. Otherwise, it will not be sent.

12. Less Than or Equal (Number): Checks whether a number is less than or equal to the given value.

Example: suppose, the Number field of the Form/Task field is Less Than or Equal to “10,” the data will be sent to your chosen action app. Otherwise, it will not be sent.

Logical Conditions​

1. Or Condition: Or Condition enables you to set multiple possible conditions. If Any condition is evaluated correctly, then subsequent and previous conditions are not considered. Because the evaluation of any one of the conditions is true, the condition will work. And it depends on how you set up your rules.

Example: Suppose, the first name of the Form/Task field is Equal to “Wayes” Or Age Greater Than “18” Or Country Equal to “Bangladesh” Or city Equal to “Rajshahi.” If any of these conditions match, then the data will be sent to your chosen action app. Otherwise, it will not be sent.

2. And Condition: The purpose of AND logic is to require two or more conditions that users must meet simultaneously.

Example: Suppose, the first name of the Form/Task field is Equal to “Bitcode,” And the Last Name is Equal to “Technology,” And the City is Equal to “Rajshahi.” If these conditions are met, then the data will be sent to your chosen action app. Otherwise, it will not be sent.