> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemreference/keywords/logic/ifelse.md).

# If Then Else

{% hint style="info" %}
The `If - Then - Else` construct can be used to make conditional parts in an expression. 

Constructs can be "nested", just as long as each "nesting" has a block of matching `If`, `Then` and `Else.`

*The Choose construct can be used as an alternative when multiple conditions need to be checked: in many cases the Choose construct will be easier to read and understand.*

This function is NOT SQL compatible. For more information about SQL compatibility, see our [documentation](/platform/wemreference/sql-compatibility.md).
{% endhint %}

{% hint style="success" %}
Returns the value after the `Then` if the condition in the `If` statement returns true. \
If the condition returns false, then the value after `Else` is returned.
{% endhint %}

<details>

<summary>Syntax</summary>

```
/* basic construction */
IF boolean_condition 
THEN value
ELSE value

/* extended construction */
IF boolean_condition THEN value
ELSE if boolean_condition THEN value
ELSE if boolean_condition THEN value
ELSE if boolean_condition THEN value
ELSE value

/* Examples: */
IF DayOfWeek ([Webshop.Orders.OrderDate]) = 1 
THEN "Monday"
ELSE "Not monday"

IF DayOfWeek ([Webshop.Orders.OrderDate]) = 2 
    THEN "Tuesday"
ELSE IF DayOfWeek ([Webshop.Orders.OrderDate]) = 3 
    THEN "Wednesday"
ELSE IF DayOfWeek ([Webshop.Orders.OrderDate]) = 4 
    THEN "Thursday"
ELSE IF DayOfWeek ([Webshop.Orders.OrderDate]) = 5 
    THEN "Friday"
ELSE IF DayOfWeek ([Webshop.Orders.OrderDate]) = 6 
    THEN "Saturday"
ELSE IF DayOfWeek ([Webshop.Orders.OrderDate]) = 7 
    THEN "Sunday"
ELSE "Monday"
```

</details>


---

# 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.wem.io/platform/wemreference/keywords/logic/ifelse.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.