# Condition node reference

Use a Condition node to send visitors down a Yes or No path. You'll find its settings, rule options, and branch behavior here.

Available on the Grow, Scale, and Pro plans.

A **Condition** node lets you show different steps depending on what you know about a visitor. It checks a rule and follows either **Yes** or **No**, without asking a question.

## When to use it

Use a Condition when the next step depends on a page, an answer, a segment, or other visitor data. For example, [WorkForge](https://workforge.rightmessage.com) could ask visitors on its consultants page a question, while the **No** path uses **Exit Flow** to stop the flow on other pages.

## Settings

![Flow condition node in the Blog visitor journey](https://rightmessage.com/help/screens/builders-node-condition.light.webp)

| Setting               | What it does                                                                                                      |
| --------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Note**              | Adds an optional multiline explanation for your team. It doesn't change the rule or appear as a visitor question. |
| Condition builder     | Defines the visitor data and comparisons that determine a match.                                                  |
| **All groups match**  | Requires every top-level group to match.                                                                          |
| **Any group matches** | Requires at least one top-level group to match.                                                                   |
| **Add group**         | Adds a nested condition group.                                                                                    |
| **Done**              | Saves pending editor changes and closes the condition editor. It doesn't publish.                                 |

You can use page and visitor data, segments, and supported flow data. Each source has its own comparisons and value controls. The [condition reference](https://rightmessage.com/help/condition-builder-reference) explains each source.

![Flow condition matching a current page path starting with /blog](https://rightmessage.com/help/screens/builders-page-condition.light.webp)

### Combine requirements

Suppose WorkForge wants to ask a question on its consultants page, but only for visitors who aren't customers. The current-page rule and customer-exclusion rule belong in one group. **Add AND condition** joins them so both must match for the **Yes** path.

To allow two page paths, give each path its own group with the same customer exclusion. **Any group matches** lets visitors through when either complete group matches. Neither page rule bypasses the exclusion. Inside nested rules, the builder calls AND and OR combinations **All of these** and **Any of these**.

### Add a note for your team

The **Note** explains the rule. It doesn't create one. Writing "Consultants page only" without adding a page rule won't restrict the node.

When AI generates a complex condition, the editor can fill an empty **Note** with the instruction that produced it. Check the rules themselves before you publish.

## How visitors move through it

A matching condition takes **Yes**. A condition that doesn't match takes **No**. After a branch finishes, visitors can continue to shared steps below the Condition unless a node in that branch ends the path.

A new Condition starts with an empty OR rule and empty **Yes** and **No** paths. That rule matches nobody, so visitors take **No** until you configure it. An empty AND rule is different. It matches without requiring a rule.

An empty branch doesn't dismiss the widget. For example, an empty **Yes** branch can skip an optional question under **No**, then reach a shared form below the Condition. A form inside **Yes** is available only to matching visitors. **Exit Flow** stops the route entirely.

## Things to know

- Conditions use the data available in the visitor's browser. Connecting a CRM doesn't make its fields known for an unidentified visitor.
- A current-page rule checks the page they're on, not their visit history.
- A score condition needs to come after the steps that set the score.
- Removing a populated Condition removes its nested paths after confirmation. It doesn't delete the library questions, forms, or offers those paths use.

If visitors take the wrong path, use [flow routing troubleshooting](https://rightmessage.com/help/troubleshoot-flow-routing) to find the decision that's sending them there. For help arranging the steps, see [plan your questions and branches](https://rightmessage.com/help/mapping-out-visitor-journeys).