Build if/then branches

What an If/then branch does

Add an If/then branch when not every enrolled record should receive the same next action.

Each branch contains a condition group. For example, a Ticket workflow might route high-priority tickets down one path and let all other tickets continue down a fallback path.

Actions can then be added independently to each branch path.

Branch order matters

When multiple branches could match the same record, the first matching branch wins.

Order your branches from the most specific or highest-priority case to the broader cases when overlap is possible.

A record does not continue down every matching branch in the current branch model.

Use the fallback path

The fallback path is the equivalent of an "otherwise" or "else" path.

Use it for records that do not match any of the explicit branch criteria.

Do not leave important outcomes dependent on a condition you have not accounted for—consider whether the fallback should contain an action, simply continue, or intentionally do nothing.

Build branch criteria

Choose the relevant record/property and configure the operator/value rules.

Condition groups can require:

• all rows to match; or
• any row to match.

Available operators depend on the HubSpot property's type, so text, number, choice and date properties expose different comparisons.

Add actions to each path

Use the workflow canvas to add steps beneath the branch outputs.

Each path can have its own tasks, property changes, owner assignment, delays, record creation or additional branches.

Keep the graph readable: if branches become difficult to reason about, review the conditions and path order before publishing.

---