Conditions and branching (if/then) in a workflow

Make your flows take decisions and follow different paths based on each contact data.

Jun 22, 2026

Watch this step in the video · If condition: a single rule

A linear workflow always does the same thing. With conditions and branching your flow takes decisions: it evaluates a rule and, depending on the result, follows one path or another. That way a single automation handles many scenarios.

The condition node (if/then)

The condition node evaluates a rule and splits the flow into two outputs:

  • Yes (true): the nodes that run when the condition is met.
  • No (false): the nodes that run when it isn't met.

Each output can have its own sequence of actions.

What you can evaluate

Conditions usually compare data from the flow context:

  • A contact field (standard or custom): "Customer type = Wholesale?".
  • The lifecycle stage or a deal's pipeline/stage.
  • The conversation's channel or whether it has a certain tag.
  • The content of the last message (for example, that it contains a word).

How to build a branch

  1. In the editor, add a condition node after the trigger or an action.
  2. Define the rule: field, operator (equals, not equal, contains, greater than, etc.), and value.
  3. Connect the Yes output nodes with the actions for that case.
  4. Connect the No output nodes with the alternative path.

Multiple conditions (AND / OR)

For richer rules, combine several conditions:

  • With AND all must be met.
  • With OR just one needs to be met.

Best practices

  • Always cover the No path, even if just to close the flow cleanly.
  • Avoid nesting too many branches; if the flow becomes unreadable, split it into several flows.
  • Name the nodes so you can tell at a glance what each branch evaluates.

Tip: sketch the logic on paper before building it. A clear decision tree avoids orphan branches and customers who get stuck with no exit.

Was this helpful?

Related articles

Message us on WhatsApp