After saving a Trigger for tasks, budgets, and deals, you can add a Condition to fine-tune your Automation rule further.
Adding a Condition is optional, and you can choose not to include it by leaving only a trigger and an action.
β‘οΈ Example of a Trigger and Action: When a new task is created (Trigger), send a message to Slack (Action).
However, if you need to add another layer to your automation to increase its precision, learn how in this article.
β‘οΈ Example of a Trigger + Condition + Action: When a new task is created (Trigger) with Alex Taylor as the assignee (Condition), and the task status is not Closed (Condition), send a message to Slack (Action).
Before we jump into adding Conditions, let's brush up on our vocabulary π:
Triggers are actions such as creating, updating, closing, or commenting on tasks, deals, and budgets, which initiate automations in Productive (the "if" part of the if-then equation).
βActions are responsible for producing the desired outcomes once all conditions are met (the "then" part of the if-then equation).
Attributes are distinct properties linked to triggers that provide critical data for the automation.
For example, when creating a condition, selecting an attribute such as task assignee ensures that the automation is executed precisely when the task is assigned to specific individuals (assignees).
βComparators are tools that compare conditions within automations. They help with determining whether a specific attribute meets certain criteria, such as being equal to, greater than, less than, or not equal to a specified value.
Adding a Condition to an Automation
1) First you need to select and apply the Trigger. |
|
2) Then, select the "Condition" option and hit Next. | |
3) Define the condition Attribute. |
|
4) Select the attribute Comparator. |
|
5) Add another Condition rule if necessary. |
|
5) If needed, further expand the condition by adding a new Condition set, which can consist of several condition rules. |
|
6) Select "Save condition" when finished, and proceed to the next step; creating an Action. |
|
π€ A Condition is made up of sets, and each set can contain individual condition rules.
β
π€ Even when grouped into sets, a single Condition can have up to 10 individual condition rules!
Condition Attributes
Here is a list of all Attributes for each Trigger (Task, Deal, Budget).
TASK | DEAL | BUDGET |
|
|
|
Condition Comparators
Here is a list of all available Comparators.
COMPARATORS |
|
Keep in mind that not all of these comparators will be available at all times when configuring your Automation because they depend on the selected Attribute and Trigger.
β
For example, Attribute = Owner for Trigger = Deal created will only support comparators like Is, Is Not, Was, and Was Not.