Building Team Rules
This article covers setting up rules for a team in Distributely
Open a team and select Configure Rules. That opens the Team Rules screen for that team.
A team can have several rules. A rule is a named group of conditions, and it matches when its conditions pass. A team matches the record when any one of its rules matches (rules are separated by an "or" no an "and."
Creating a ruleSelect Add Rule. You get two fields:
- Rule Name — a label for you. It does not affect routing.
- Match Type — Match ALL Conditions requires every condition in the rule to pass. Match ANY Condition requires at least one. With a single condition the two behave identically.
Expand a rule and select Add Condition. A condition has three parts:
- Field Name — the HubSpot property to test, chosen from the properties on the team's object type. The list shows each property's label and internal name.
- Operator — how to compare. The choices change with the property's type.
- Value — what to compare against. Dropdown properties get a picker of their own options; everything else gets a text box. Value disappears for is empty and is not empty, which take no value.
Which operators appear depends on the type of property you picked in Field Name.
Text properties
- is equal to / is not equal to
- contains / does not contain
- is empty / is not empty
Number properties
- is equal to / is not equal to
- is greater than / is greater than or equal to
- is less than / is less than or equal to
- is empty / is not empty
Dropdown properties
- is equal to / is not equal to
- is in / is not in
- contains / does not contain
- is empty / is not empty
Checkbox properties
- is equal to / is not equal to
- is empty / is not empty
Date properties
- is equal to / is not equal to
- is empty / is not empty
Before-and-after comparisons on dates are not currently offered in the Operator list. To route on a date window, use a HubSpot workflow branch or a calculated property to reduce the date to a value the operators above can test.