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

# Basic Condition

> Branch the workflow into TRUE and FALSE paths based on field conditions

Splits your workflow into two branches - **True** and **False** - based on whether records match the configured conditions. Use it to route records down different paths for different processing.

## Configuration

| Setting        | Description                                                          |
| -------------- | -------------------------------------------------------------------- |
| **Conditions** | One or more conditions comparing a field to a static value           |
| **Logical**    | **OR** (any condition matches - default) or **AND** (all must match) |

Each condition specifies:

| Setting      | Description                                                                     |
| ------------ | ------------------------------------------------------------------------------- |
| **Field**    | The field to evaluate                                                           |
| **Operator** | Comparison operator (equals, not equals, greater than, contains, is null, etc.) |
| **Value**    | The static value to compare against                                             |

## How It Works

<Steps>
  <Step title="Define conditions">
    Add one or more conditions that compare field values against static values.
  </Step>

  <Step title="Choose logic">
    Select **OR** to branch on any matching condition, or **AND** to require all conditions.
  </Step>

  <Step title="Connect downstream nodes">
    Connect nodes to the **True** output for matching records, and to the **False** output for non-matching records.
  </Step>
</Steps>

## Output

| Output    | Description                                    |
| --------- | ---------------------------------------------- |
| **True**  | Records where the conditions evaluate to true  |
| **False** | Records where the conditions evaluate to false |

Both outputs can connect to any downstream node, creating independent processing paths.

## Example

Route high-value accounts to a different enrichment path:

* Condition: Revenue **greater than** 100000
* **True path** → AI Enrichment → Update Record
* **False path** → Export to CSV for review

## Best Practices

* Use clear, specific conditions to avoid ambiguous routing
* Always connect both True and False outputs - unconnected branches mean lost records
* For field-to-field comparisons, use [Field Comparison Condition](/guide/nodes/condition/field-comparison-condition-node) instead
* For routing to more than two paths, use [Router Condition](/guide/nodes/condition/router-condition-node)

## Related Nodes

* **[Field Comparison Condition](/guide/nodes/condition/field-comparison-condition-node)** - branches by comparing two fields instead of field vs. static value
* **[Router Condition](/guide/nodes/condition/router-condition-node)** - routes records to multiple named paths, not just True/False
* **[Simple Filter](/guide/nodes/filter/simple-filter-node)** - removes non-matching records instead of branching