> For the complete documentation index, see [llms.txt](https://docs.arcee.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcee.ai/arcee-orchestra/workflows/workflow-components/conditional-node.md).

# Conditional Node

The conditional node enables dynamic decision-making and branching logic within workflows. It allows workflows to evaluate specific conditions or rules and execute different paths based on the outcome.

<figure><img src="/files/EEYsvo87nc3jyoeaUb4t" alt="" width="563"><figcaption><p>Conditional Node Workflow</p></figcaption></figure>

In the risk analysis example above, the workflow input is passed to a senior analyst model. Based on the determined risk and reward, different actions are taken. If the risk is low enough, a draft proposal is be generated. If the risk is too high, more analysis can be run. If the risk to reward ratio is in the middle, more research can be done with integrations. If the ratio falls outside expected boundaries, company policies can be searched to determine the right course of action. &#x20;

### Setting Up Conditionals

<figure><img src="/files/wu7mZasJK8bV9c3C9GW1" alt="" width="393"><figcaption><p>Condition</p></figcaption></figure>

Each condition has a name and the set of criteria which define it. You specify a variable from an earlier step in the workflow, the condition, and the value to compare it against. Values can be strings or integers/floats depending on which condition is selected. For a single condition, you can specify multiple criteria using `and` or `or` .&#x20;

<figure><img src="/files/TDVn66nd77OOD8piTe0X" alt="" width="304"><figcaption></figcaption></figure>

Once the conditions have been defined, the action which occurs for each condition can be specified within the conditional node, by setting `Then:` or you can drag a connection line to your next node.

#### Supported Operators

* `==`  checks if the selected variable is equal to the provided value
* &#x20;`!=` checks if the selected variable is not equal to the provided value
* `>` checks if the selected variable is greater than the provided value
* `<` checks if the selected variable is less than the provided value
* `>=` checks if the selected variable is greater than or equal to the provided value
* `<=` checks if the selected variable is less than or equal to the provided value
* `in` checks if the selected variable contains the provided value/text
* `not in` checks if the selected variable does not contains the provided value/text


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.arcee.ai/arcee-orchestra/workflows/workflow-components/conditional-node.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
