You can narrow down the automation using conditions from the same module.
For example:
If a text field contains, or does not contain, a specific text, or if it is filled in or empty.
If an option list field contains, or does not contain, certain options, or if it is filled in or empty.
If a numeric field is equal to, different from, higher or lower than a specific value, or if it is filled in or empty.
If a date is equal to, different from, today, yesterday, tomorrow, etc.
You can also narrow it down using conditions combining entities, for example, when a text, option list or date field is equal to, or different from, a field in another entity.
This condition evaluates whether the ‘Postcode’ of the created opportunity is different from the ‘Postcode’ of the main company linked to the opportunity.
This condition evaluates whether the ‘Expected closing date’ of the created opportunity is equal to a custom date field of the main company linked to the opportunity.
Or if a numeric field is lower, higher, or equal to one from another entity.
Or even if it is between two values, the initial and final ones, defined by mathematical calculations with variables from different entities.
This condition evaluates whether the ‘Value’ of the created opportunity is between the initial value, such as the sum of 2 custom fields from the main company and the intermediary company linked to the opportunity; and the final value, such as the multiplication of 2 custom fields from the main company and the created opportunity.
In summary
You can create conditions that combine fields from different entities.
These conditions can compare:
Text fields, option lists, numbers or dates with specific values.
Fields with each other, even when they belong to different entities (for example, comparing the postcode of an opportunity with that of the linked company).
Numeric values within ranges calculated from fields of several entities.
You can cross information between modules to create advanced and very precise conditions within your automations