Conditionals > Conditionals (IF) explained
Logic operations explained
Tallyfy automations watch what users enter and adjust your workflow automatically. Simple IF-THEN rules adapt your processes to different scenarios.
Every automation follows this pattern:
IF [something is true]THEN [do this action]Conditions check what users enter and watch for specific responses.
Examples:
- IF a user selects “Urgent” in a form field
- IF a task is approved by a manager
- IF a task is completed on time, late, or early
- IF a form field contains (or doesn’t contain) a specific value
Actions change your process based on what conditions find.
Examples:
- THEN show or hide steps
- THEN assign the task to a different person or team
- THEN adjust deadlines
- THEN trigger a webhook to an external system
Tallyfy lets you combine conditions with AND or OR - just like you’d explain rules to a colleague.
AND means ALL conditions must be true.
IF [condition 1 is true] AND [condition 2 is true]THEN [do this action]Example: IF the user selects urgent priority AND the amount is over $1000 THEN show the executive approval step
OR means AT LEAST ONE condition needs to be true.
IF [condition 1 is true] OR [condition 2 is true]THEN [do this action]Example: IF the client selects VIP service OR the order amount exceeds $5000 THEN show premium processing steps
Tallyfy evaluates conditions left to right1 - in the exact order you add them.
Given this rule:
IF [condition 1] AND [condition 2] OR [condition 3]THEN [do this action]Tallyfy processes it step by step:
- Evaluate condition 1
- AND condition 2 with the result so far
- OR condition 3 with the accumulated result
The action triggers if:
- Both condition 1 AND condition 2 are true, OR
- Condition 3 is true by itself
Tallyfy doesn’t use operator precedence like programming languages (where AND would evaluate before OR). Conditions run in the order you add them. Straightforward and predictable.
Don’t cram everything into one massive rule. Break it up into multiple separate automation rules.
This keeps your logic readable, easier to troubleshoot, and avoids confusion about evaluation order. Your future self will thank you.
Empty or missing form field values can cause unexpected automation behavior. Here’s how Tallyfy treats them:
- Text fields: An empty field is “not equal” to any specific value
- Dropdowns: No selection counts as different from any option
- Numbers: Empty number fields don’t match
greater_thanorless_thanconditions - Multiselect/file fields: An empty list doesn’t match any
containsorequalscheck
Problem: A step shows up even though no conditions seem true.
Likely cause: You’re using OR logic with “not equal” conditions.
- “Field A is NOT ‘Option 1’” evaluates to TRUE when the field is empty
- “Field B is NOT ‘Option 2’” also evaluates to TRUE when empty
- With OR, if ANY condition is true, the action triggers
Fix this by:
- Making the field required so it’s never empty
- Adding an explicit “is not empty” check
- Using positive conditions (“equals”) instead of negative ones (“not equals”)
Tutorials > Create an automation
-
Processing order differs from standard programming operator precedence where AND typically evaluates before OR ↩
Was this helpful?
- 2025 Tallyfy, Inc.
- Privacy Policy
- Terms of Use
- Report Issue
- Trademarks