> ## Documentation Index
> Fetch the complete documentation index at: https://www.voiceflow.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Condition

> Route your workflow based on variable values or logic.

## What this step does

The Condition step lets you create different paths in your workflow based on whether specific conditions are met. You might use it to check if a user is logged in, verify that a form is complete, or route users differently based on their account type.

### Using the Condition step

Drag the Condition step onto the canvas and connect it to the step before it. Click on the step to set up your conditions and paths.

## Configuration

- **Paths**: Create paths that your workflow can follow. For each path, define conditions by selecting a variable, choosing a comparison operator (eg: is, contains, greater than), and entering a value to compare against. Use **Match all** for AND logic or **Match any** for OR logic when adding multiple conditions to a path.
- **Else path**: Toggle this on to add a fallback path when no conditions are met.

## How it behaves

Use **Match all** when every condition must be true; use **Match any** when one match is enough. The optional **Else path** gives you an explicit fallback for unmatched values.

## Example

To separate signed-in customers from guests, create a path that compares `is_logged_in` to the value your application uses for a signed-in customer. Enable **Else path** and connect it to your sign-in instructions. Test once with each value and check that the expected path runs.

Use a [persona](/docs/documentation/build/data/personas) to repeat those starting values. The variable and authentication behavior belong to your agent; the Condition step only evaluates the configured comparison.

## Related guides

[Workflows](/docs/documentation/build/workflows) · [Variables](/docs/documentation/build/data/variables) · [Tests](/docs/documentation/measure/tests)
