> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.12/development/flow-studio/flowscript/operators.md).

# Operators

### **Comparison operators**

The following comparison operators can be used in FlowScript. The result of these expression are always a truth (Boolean) value:

| Expression | Result                                                                                     |
| ---------- | ------------------------------------------------------------------------------------------ |
| `a = b`    | TRUE if a equals b, FALSE if a does not equal B or the types of a and b cannot be compared |
| `a != b`   | TRUE if a does not equal b or the types of a and b cannot be compared, FALSE if a equals b |
| `a > b`    | TRUE if a is greater than b, FALSE otherwise                                               |
| `a < b`    | TRUE if a is less than b, FALSE otherwise                                                  |
| `a >= b`   | TRUE if a is greater than or equal to b, FALSE otherwise                                   |
| `a <= b`   | TRUE if a is less than or equals to b, FALSE otherwise                                     |

### **Logical operators**

The following logical operators can be used in Flow Script. The result of these expressions are always a truth (Boolean) value.

| Expression | Result                                          |
| ---------- | ----------------------------------------------- |
| `a and b`  | TRUE if both a and b are true, FALSE otherwise  |
| `a or b`   | TRUE if either a or b are true, FALSE otherwise |
| `not a`    | TRUE if a is false, FALSE otherwise             |

### **The IN operators**

The IN operator allows you to compare one left hand side value (L) with several right hand side values (R) at once. The result of the statement is TRUE if L is equal to any of the values in R.

```fsharp
firstName in ('James', 'Richard', 'Danny')
```

### **Truth of non-boolean values**

Flow Script is fairly permissive when it comes to evaluating the truth of non-Boolean values. The following non-Boolean values count as true:

* All numbers except 0
* All strings except the empty string, "0" and "FALSE" (including all upper- and lowercase variants)

![](https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-sNNjKLVmonjWASMMl%2F-M-sPnK-D0cd_kARRV2d%2Fhelp_root_flow_script_functions_truth_example.png?alt=media\&token=ea3b8783-a53e-4b28-8e51-a32de123ff26)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.novacuraflow.com/6.12/development/flow-studio/flowscript/operators.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.