> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/formula-syntax/logical-functions/in.md).
# IN
Checks if a value matches the values within a given list or array of values and returns TRUE if it matches.
The **IN** function returns TRUE if the specified value matches any of the values in the list or array. It returns FALSE if the value does not correspond to any item in the list. It is frequently used alongside IF and other conditional functions to simplify multiple OR conditions.
### Syntax
```javascript
IN(value,[item1,item2,...])
```
### Arguments
value - The value to check. Required.
\[item1, item2,...] - A list (array) of values to compare against. Required.
### **Return value**
Either TRUE or FALSE.
### **Example**
In this example, values are assigned to the *2027 Plan* using the **IN** function within an [IF](/formula-syntax/conditional-statements/if.md) statement.
The **IN** function checks the 'Sub Category' value and returns TRUE only when it matches any one in the specified list - *Juices*, *Soda,* and *Mineral Water.* The formula returns 30.5m for records where the *Sub Category* is *Juices*, *Soda*, or *Mineral Water* and 0 for all other subcategories.
Applying IN function
---
# 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://docs.inforiver.com/formula-syntax/logical-functions/in.md?ask=&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.
