In this article, you will learn about what to expect when using conditions in your automations in Workiz.
Workiz Automations is an add-on designed to send automatic notifications to your team and clients based on certain criteria you define. This feature is designed to save you time, prevent job cancellations, and help scale your business with less effort.
You can also refine these rules even further to ensure they only trigger under specific circumstances using conditions. For example, you may only want to trigger a specific automation when the job has a specific tag, or when a job takes place in a specific service area.
To learn more about adding conditions to your automations, please see this article.
Applying multiple conditions
Workiz Automations allows you to add multiple conditions to a single automation, giving you precise control over when it should (and should not) trigger. You can add multiple conditions to your automation rule to create hyper-specific scenarios (“and” conditions) or to broaden the reach (“or” conditions).
Here, we will use truth tables to explain what to expect when applying multiple conditions to a single automation. A truth table is a chart that helps explain all the possible outcomes or results of a logical situation (like conditions within an automation).
Using 'or' conditions
When "or" conditions are applied, only one of the conditions must be true in order for the automation to trigger. Logically, to prevent the automation from triggering, all of the conditions must be false.
Here is how we will identify the conditions from the example above:
- Condition A: Job tag = Part pickup
- Condition B: Job tag = Service plan
Condition A | Condition B | Automation triggered |
---|---|---|
True | True | True |
True | False | True |
False | True | True |
False | False | False |
Using 'and' conditions
When "and" conditions are applied, all of the conditions must be true in order for the automation to trigger. Logically, to prevent the automation from triggering, only one of the conditions must be false.
Here is how we will identify the conditions from the example above:
- Condition A: Job tag = Part pickup
- Condition B: Job tag = Estimate
Condition A | Condition B | Automation triggered |
---|---|---|
True | True | True |
True | False | False |
False | True | False |
False | False | False |
Using both 'and' & 'or' conditions
You can also apply "and" conditions alongside "or" conditions within the same automation rule. Understanding when these automations will/won't be triggered will vary depending on the rule itself.
Here is how we will identify the conditions from the example above:
- Condition A: Job tag = Part pickup
- Condition B: Job tag = Service Plan
- Condition C: Job type = Inspection
Condition A | Condition B | Condition C | Automation triggered |
---|---|---|---|
True | True | True | True |
True | True | False | False |
True | False | True | True |
True | False | False | False |
False | True | True | True |
False | True | False | False |
False | False | True | False |
False | False | False | False |
Understanding 'is not' (≠) logic
With Workiz Automations, you can create conditions around "is not equal to" logic. The phrasing of "is not equal to" may occasionally make it confusing about what to expect, but all of the logic from the previous truth tables still applies.
Here is how we will identify the conditions from the examples below:
- Condition A: Job tag = No review
- Condition B: Job tag = Do not serve again
'Or' truth table
Because the example above is an "or" condition, only one of the conditions needs to be true for the automation to trigger. Logically, the only way to prevent the automation from triggering is for both of the conditions to be false.
Condition A | Condition B | Automation triggered |
---|---|---|
True | True | True |
True | False | True |
False | True | True |
False | False | False |
If you want to prevent the automation from triggering when only one of these conditions is true, set it up as an "and" condition instead.
'And' truth table
Because the example above is an "and" condition, both of the conditions need to be true for the automation to trigger. Logically, to prevent the automation from triggering, only one of the conditions must be false.
Condition A | Condition B | Automation triggered |
---|---|---|
True | True | True |
True | False | False |
False | True | False |
False | False | False |