Create workflows that adapt to user responses by using conditions on connections between entities. Instead of showing the same questions to everyone, your flows can branch and show relevant content based on what users have entered.
Smart Connections Connections between entities can include conditions that control when users follow specific paths, creating personalized experiences within a single workflow.

​
How It Works

​
Connections (Edges)

Connections represent the pathways between components in your flow. They link entities and determine the sequence in which components appear to users during a conversation.

Linear Flow

Simple Sequence Connect entities in order for straightforward, step-by-step workflows

Branching Flow

Multiple Paths A single entity can connect to multiple destinations with different conditions

​
Adding Conditions

Each connection can include a condition. When a condition is applied to a connection, that pathway will only be followed if the condition evaluates as true, enabling personalized conversation experiences based on user responses. Example:
  • Age question connects to two different paths
  • If Age < 25 → Show student insurance options
  • If Age ≥ 25 → Show standard insurance options

​
Available Conditions

Based on the Wizflow platform, these condition types are available:

eq (equals)

Check if a response equals a specific value

cmp (compare)

Compare values (greater than, less than, etc.)

range

Check if a value falls within a specified range

has

Verify if an entity has a specific value or property

​
Simple Examples

​
Basic Age Routing

Age Question: "How old are you?"
├─ If age < 18 → "You must be 18 or older"
├─ If age >= 18 AND age <= 65 → Standard Application
└─ If age > 65 → Senior Application with Additional Questions

​
Choice-Based Routing

Insurance Type Question: "What type of insurance do you need?"
├─ If choice = "Life Insurance" → Life Insurance Questions
├─ If choice = "Home Insurance" → Property Details
└─ If choice = "Auto Insurance" → Vehicle Information

​
Danish Services Integration

User Authentication Check
├─ If isUserAuthenticated = true → Skip basic info, load from systems
└─ If isUserAuthenticated = false → Collect basic information manually

Property Information
├─ If houseExists = true → Load property details automatically  
└─ If houseExists = false → Manual property entry form

​
Building Conditional Flows

1

Plan Your Branches

Identify where your workflow needs to split based on different user responses or data
2

Connect Entities

Create connections between entities in the visual flow builder
3

Add Conditions

Click on connections to add conditions that determine when users follow each path
4

Test Your Logic

Use the preview feature to test different user paths through your workflow

​
Best Practices

Keep It Simple

Start with basic conditions before building complex branching logic

Test All Paths

Make sure every possible user journey has a valid path through your flow

Provide Fallbacks

Always include default paths for unexpected conditions or missing data

Use Clear Logic

Make your conditions easy to understand and maintain for your team

​
Common Use Cases