Automations - Conditions
Package: BASIC
1. Configure Condition
Conditions define whether actions should only be executed under certain prerequisites.
After clicking a condition in the editor, the "Condition" sidebar opens.
Condition sidebar
A condition can only be configured if it is connected to an already configured trigger!
In the condition sidebar, there are two action icons at the top right and a toggle at the bottom:
- Show actions (icon "three dots" - only displayed if the condition is configured) → after clicking, a flyout menu is displayed with the following actions:
- Edit → After clicking the action "Edit", the popup "Condition" opens, in which the condition(s), the name and description can be entered or changed. Additionally, the toggle "Abort condition" is available.
- Delete → After clicking the action "Delete", an unconfigured action is deleted without further query.
For already configured conditions: If the condition is connected to other configured nodes, a popup with the text "Would you like to create direct connections between triggers and actions?" is displayed. If no direct connection is established (button "Cancel"), another popup with the text "Should this node really be deleted? Subsequent nodes may be reset as a result if they lose the module binding of a trigger." is displayed.
- Show/hide sidebar → the sidebar can be shown/hidden by clicking the action icon "arrow with vertical bar"
- Toggle automation active/inactive → using the toggle, the trigger can be set to active/inactive
After double-clicking on a condition in the editor – alternatively via the action "Edit" in the condition's sidebar – the popup "Condition" opens.
Popup Condition
1.1. Condition Step 1 - General
The following fields are available in the popup "Condition" – in the first step:
- Action button "New condition" → After clicking the action button "New condition", the action button changes to "Select module" and a flyout menu with the modules is displayed to select the module for which the condition applies → see Step 2.
- Action icon "Delete" (icon "Trash") → The complete row of the condition is deleted.
- Button "New condition group" → An additional row (condition group) of a condition is displayed. Condition groups are connected with the logical operator "and" or "or".
- Section "General" → Display/input of general settings:
- Name * → Enter an individual name for the condition
- Description → Brief description of the condition (optional)
- Toggle "Abort condition" → If there is more than one condition for a trigger, this can be used to define whether subsequent conditions should also be executed or not.
*Required field
The following (simple) example is intended to explain the functionality of an abort condition.
The following example of an automation contains 2 triggers, 3 conditions and 3 actions.
Abort condition in condition 1a → If condition 1a applies and is configured as an abort condition, action 1a is executed. Condition 1b and action 1b are no longer checked/executed. Trigger 2 is an independent chain and is not affected by this – it is executed independently if its event occurs.
- Conditions and actions that directly follow an abort condition – i.e. those that are on the same hierarchy level – are always checked/executed, even if the abort condition applies.
- Triggers, conditions and actions that follow the abort condition within the same trigger chain are no longer checked/executed when the abort condition applies. Triggers in other chains are not affected.
- Abort conditions serve to conserve system resources, as the execution of further conditions and actions within a chain can be suppressed.
- Abort conditions are not useful if time-delayed actions follow!
1.2. Condition Step 2 - Select Module
After clicking the action button "New condition" (see Condition Step 1), the action button changes to "Select module" and a flyout menu with the modules is displayed to select the module for which the condition applies.
Popup Condition - Select module
Only modules that are already linked via a configured trigger in the automation are available for selection. Since conditions are always bound to a trigger, exclusively the modules defined there are offered – only their records and fields can be checked by a condition.
1.3. Condition Step 3 - Select Field
After selecting the module, the action button "Select field" is displayed. After clicking the action button "Select field", a flyout menu with the fields from the selected module is displayed to select the field for which the condition applies.
Popup Condition - Select field
1.4. Condition Step 4 - Select Comparison
After selecting the field, the action button "Select comparison" is displayed. After clicking the action button "Select comparison", a flyout menu with the possible types of comparison is displayed.
Popup Condition - Select comparison
The type of comparison (comparison operator) depends on the field type of the selected field!
The comparison operators are always specified by the system itself – depending on the field type!
The available comparison operators are based not only on the field type of the selected field, but also on the linked trigger. The comparison operator "was changed" is not available in conditions linked to the trigger "Record created", as at the time of triggering there is no previous state of the record with which a comparison would be possible.
The following comparison operators are available as examples:
- Text/Text area
- is
- is not
- begins with
- ends with
- contains
- does not contain
- less than
- greater than
- less than or equal
- greater than or equal
- was changed
- Selection list/Multi-selection list
- is one of
- is none of
- was changed
- Number/Currency/Percentage
- is not
- less than
- greater than
- less than or equal
- greater than or equal
- was changed
- Email/URL
- is
- is not
- begins with
- ends with
- contains
- does not contain
In the flyout menu "Select comparison", the action icon "Configure workspace" (icon "Puzzle") is available in the row of the selected comparison (comparison operator).
Flyout menu "Select comparison" - Action icon "Configure workspace"
In the input field of the comparison operator, a corresponding value can be entered directly.
Popup Condition - Example configuration of a simple condition
1.5. Condition Step 4a - Configure Workspace (optional)
Optionally, the "Configure workspace" function can also be used to configure more complex comparisons.
After clicking the action icon "Configure workspace" (icon "Puzzle"), the popup "Set value" opens.
The functionalities in the popup "Set value" are described in detail in the section Configure workspace - Set value.
1.6. Condition Step 4b - Additional Condition (optional)
Three action icons are displayed in the row of a condition:
- Delete (icon "small trash") → the row of the condition is deleted
- Insert new condition after this row (icon "Plus") → A new condition (row) is inserted after this row.
Conditions are connected with the logical operator "and" or "or". - Delete condition group (icon "large trash") → the entire condition group (which can contain multiple conditions) is deleted
Individual row of a condition
1.7. Condition Step 4c - New Condition Group (optional)
After clicking the "New condition group" button, an additional condition group is displayed, within which one or more further conditions can be inserted.
Condition groups are connected with the logical operator "and" or "or".
1.8. Condition Step 5 - Save Condition
After clicking the "Save" button in the popup "Condition", the condition is saved and displayed in the editor.
1.9. Delete Condition
By selecting a condition (by clicking, the border is displayed thick) and pressing the "Delete key", a condition can be deleted again in the automation editor.
If the condition is connected to other configured nodes, a popup with the text "Would you like to create direct connections between triggers and actions?" is displayed. If no direct connection is established (button "Cancel"), another popup with the text "Should this node really be deleted? Subsequent nodes may be reset as a result if they lose the module binding of a trigger." is displayed.
1.10. Multiple Triggers and Order
An automation can contain multiple conditions and actions that are linked to one or more triggers. The order of processing plays an important role here.
Order of conditions
If multiple conditions are assigned to a trigger, they are processed in the defined order from top to bottom. The order can be adjusted individually in the trigger's sidebar under Connections via drag & drop.
An automation checks both the lead status and the industry of a lead. If the lead status is considered more important, the corresponding condition should be in first place – it is then checked first and a classification made. The industry conditions follow only after that.
Abort condition
If a condition is marked as an abort condition, all subsequent conditions are no longer checked as soon as this condition applies and the associated action has been executed.
The abort condition is only useful when subsequent conditions are no longer relevant in the case of a match. If multiple independent conditions should always be checked, no abort condition may be set.
Order of triggers
In automations with multiple triggers, the order of the triggers themselves can also be set. The order determines which trigger is processed first, and can also be adjusted in the sidebar via drag & drop.
Activation after creation
Newly created and saved automations are inactive by default. They must be manually activated after completed configuration. This ensures that an incompletely configured automation is not inadvertently executed.
2. Practical Examples
1 – Simple status check: Only process won deals
An automation should only update a deal when it has the status Won. A single condition row is configured: field Status, operator equals, value Won. No AND or OR linking is needed. The automation only runs when this condition is met.
2 – AND link: New customer with a specific package
An invoice should only be created automatically when the organization is flagged as a new customer AND the selected package is Enterprise. Two condition rows are added within the same condition group: field New Customer = Yes AND field Package = Enterprise. Both conditions must be met simultaneously.
3 – OR link with condition groups: Two alternative paths
A notification should be sent when either the status is Overdue OR the responsible person is Support Team. A second condition group is added via Add Group. The first group contains: Status = Overdue; the second group contains: Responsible = Support Team. As soon as one of the groups is satisfied, the condition is met.
4 – Abort condition: Skip salutation for blank first name
An automation builds a salutation from first name and last name. If the first name field is empty, the salutation placeholder cannot be filled correctly. An abort condition is configured: field First Name, operator is empty. If the condition is met, the automation stops immediately without executing the subsequent action.
3. Frequently Asked Questions
Why can't I configure the condition?
A condition can only be configured if it is connected to an already configured trigger. Without a trigger connection, the configuration panel remains locked.
Why can't I select the module in the condition?
The module is automatically taken from the connected trigger. It cannot be changed directly in the condition — to use a different module, the trigger must be adjusted.
What is the difference between condition rows and condition groups?
Condition rows within the same group are always AND-linked — all rows in the group must be satisfied simultaneously. Condition groups are OR-linked — it is sufficient if all rows within any one group are satisfied.
When does it make sense to use an abort condition?
An abort condition is useful when the automation should not continue under a specific condition — for example, when a required field is empty, a specific status is already set, or a flag signals that the record has already been processed. Unlike a regular condition, the automation is completely stopped without the subsequent action being executed.
What does the operator "was changed" do?
The operator was changed checks whether the monitored field has been assigned a new value during the current save operation — regardless of what the old or new value is. This is particularly useful in combination with the trigger Record Changed to react precisely to field changes.