Automation Conditions and Logic

Conditions decide whether an event-driven automation should run for a particular lead.

Root group

Every rule has one root group using either:

• AND: every child condition or group must match
• OR: at least one child condition or group must match

The root group can contain individual conditions and nested child groups.

Example: source plus stage alternatives

Lead source is “Website”
AND
(Stage is “New” OR Stage is “Contacted”)

Build this with an AND root, one source condition, and a nested OR group containing the stage conditions.

Example: two independent branches

(Form is “Demo request” AND Owner is empty)
OR
(Category contains “priority” AND Value is greater than 5000)

Build this with an OR root and two nested AND groups.

Available lead context

Supported conditions include combinations of:

• Native form
• UTM and campaign fields
• Advertising platform
• Landing page and referrer
• Lead stage and value
• Lead category
• Owner and owner role
• Follow-up date and overdue-follow-up state
• Configured custom fields where supported

Billing plan, workspace capacity, remaining trial days, affiliate data, and time-since-last-activity conditions are intentionally excluded from tenant rules.

Operators

Operators change according to field type. Selection fields use operators such as Is, Is Not, Is One Of, Is Empty, or Is Not Empty. Text, number, date, and multi-value fields expose operators appropriate to their values.

Ownership safeguards

Owner assignment intentionally replaces the existing owner. Add Owner is empty when the rule should only fill unassigned leads. Add a specific owner condition before clearing or replacing ownership.

Test the logic

Use a real representative lead in the dry-run simulator. Review each branch result, not only the final pass or fail. Then verify one real event after enabling the rule.