Skip to main content

Automation Conditions

A Condition step filters the automation โ€” if the condition evaluates to false for a lead, the automation stops for that lead. Conditions are purely evaluative; they do not modify any data.


Adding a Condition Stepโ€‹

In the automation form, in the Steps section:

  1. Click Add Step.
  2. Set Step Type to Condition.
  3. Select the Condition Type from the dropdown.
  4. Fill in the required values for that condition type.

Condition Types Referenceโ€‹

Lead Source Isโ€‹

Checks if the lead's source matches the selected value.

  • Source โ€” select from the available lead sources

Example: continue only if source is "Facebook"


Lead Source Is Notโ€‹

Checks if the lead's source does NOT match the selected value.

  • Source โ€” select from the available lead sources

Example: skip leads from "Manual Entry"


Lead Has Tagโ€‹

Checks if the lead currently has a specific tag.

  • Tag Name โ€” the exact tag name to check

Example: continue only if lead has tag "vip"


Lead Does Not Have Tagโ€‹

Checks if the lead does NOT have a specific tag.

  • Tag Name โ€” the exact tag name to check

Example: only send welcome email if "already-welcomed" tag is absent


Lead Field Equalsโ€‹

Checks if a specific lead field has an exact value.

  • Field Name โ€” the field key (e.g. status, email, or a custom field key)
  • Value โ€” the exact value to compare against

Example: continue only if status equals qualified


Lead Field Containsโ€‹

Checks if a specific lead field contains a substring.

  • Field Name โ€” the field key
  • Value โ€” the substring to look for

Example: continue only if email contains @gmail.com


Lead Field Is Emptyโ€‹

Checks if a specific lead field has no value.

  • Field Name โ€” the field key

Example: stop if the lead has no phone number


Lead Score Greater Thanโ€‹

Checks if the lead score is above a threshold.

  • Score โ€” the threshold value

Example: continue only if score > 50


Lead Score Less Thanโ€‹

Checks if the lead score is below a threshold.

  • Score โ€” the threshold value

Example: continue only if score < 20 (low-quality leads)


Assigned to Userโ€‹

Checks if the lead is currently assigned to a specific user.

  • User โ€” select from your workspace users

Example: send a different email depending on who owns the lead


Unassignedโ€‹

Checks if the lead has no assigned user (no configuration needed).

Example: if unassigned, assign via round-robin before emailing


Time of Dayโ€‹

Checks if the current time is within a specified time range.

  • Time Range โ€” enter in HH:MM-HH:MM format (e.g. 09:00-17:00)

Example: only send SMS during business hours (even without the global business hours setting)


Day of Weekโ€‹

Checks if today is one of the specified days.

  • Day(s) โ€” comma-separated day names (e.g. Monday,Tuesday,Wednesday)

Example: only assign to the weekend team on Saturday,Sunday


Tipsโ€‹

  • Use conditions after a trigger to narrow down which leads proceed through the automation.
  • Stack multiple conditions to build complex filters (each must pass for the automation to continue).
  • The Lead Has Tag / Does Not Have Tag combination is powerful for preventing duplicate emails.