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

# Overview

> Condition nodes branch workflow execution by evaluating expressions against the current context.

# Condition Nodes

Condition nodes add decision logic to your workflow. They evaluate runtime values and route execution based on whether the configured rule matches.

## How To Use Condition Nodes

1. Configure comparison inputs and operators.
2. Connect explicit branch handles (`true`/`false` or case handles for switch).
3. Keep branch outcomes intentional (for example escalate vs continue).
4. Test all branch paths before enabling in production.

## Choosing The Right Condition Type

* **String/Number/Date/Boolean** for single-value checks.
* **Array** for list membership and count-based checks.
* **Switch** for multi-path routing based on ordered case matching.
* **Logical Group** for nested AND/OR expression trees.

## Condition Types

<CardGroup cols={2}>
  <Card title="String Condition" icon="pilcrow">
    Check conditions on strings and text.

    [View](./string-condition)
  </Card>

  <Card title="Number Condition" icon="hash">
    Check conditions on numbers and numeric values.

    [View](./number-condition)
  </Card>

  <Card title="Date Condition" icon="calendar">
    Check conditions on dates and times.

    [View](./date-condition)
  </Card>

  <Card title="Boolean Condition" icon="toggle-right">
    Check conditions on boolean values.

    [View](./boolean-condition)
  </Card>

  <Card title="Array Condition" icon="list">
    Check conditions on arrays and their elements.

    [View](./array-condition)
  </Card>

  <Card title="Switch" icon="git-fork">
    Create multiple branches based on different conditions.

    [View](./switch-condition)
  </Card>

  <Card title="Logical Group (AND/OR)" icon="binary">
    Combine multiple conditions with complex AND/OR logic.

    [View](./logical-group-condition)
  </Card>

  <Card title="Resource Has Tags" icon="tags">
    Check if a resource has specific tags or any tags at all.

    [View](./resource-has-tags-condition)
  </Card>
</CardGroup>

## Condition Design Best Practices

* Align operand types before comparison (string vs number vs date).
* Prefer explicit thresholds and named handles for readability.
* Always connect every branch to avoid dead-end paths.
* Add observability actions on critical false/error branches.