Overview

The Condition step branches workflow logic. Use Condition to direct flows down different paths based on data values, Agent outputs, or other criteria.

Use Condition when different workflow paths are needed based on specific conditions.

Use When

• Different actions are needed based on contract terms

• You want to route based on Agent analysis (high-risk vs. low-risk)

• Approval requirements vary based on contract value

• You need to skip steps based on specific criteria

• Different notification paths are needed based on outcomes

Configuration Options

Logical Expressions

Define conditions using:

• Variable comparisons (`@Intake.ContractValue > 100000`)

• Text matching (`@Agent.RiskLevel == "high"`)

• Boolean logic (AND, OR, NOT)

• Multiple conditions with complex logic

True / False Branches

Configure two paths:

• True branch: Steps that execute when the condition is met

• False branch: Steps that execute when the condition is not met

Each branch can contain any combination of downstream steps.

Example

Risk-Based Routing

Configuration:

Condition: @Agent.RiskLevel == "high"

True Branch (High Risk):

• Route to VP approval

• Send notification to Legal team

• Escalate deadlines

False Branch (Low Risk):

• Route to standard approval

• Send standard notification

• Normal deadlines apply

When the Agent step determines high risk, the flow follows the True branch. For low-risk determinations, the False branch executes.

Another Example

Value-Based Approval

Configuration:

Condition: @Intake.ContractValue > 500000

True Branch (High Value):

• Requires CFO approval

• Send executive notification

• Generate detailed report

False Branch (Standard Value):

• Requires manager approval

• Send standard notification

Notes

• Conditions can be nested or chained

• Multiple conditions can be combined with AND/OR logic

• Each branch maintains full workflow capabilities

• Conditions should be specific and clear