> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/utils/controls/switch.md).

# Switch

### Overview

The **Switch** component allows conditional branching of messages based on predefined expressions. It evaluates up to five conditions (`out1` to `out5`) and routes messages accordingly. If none of the conditions match, the message is sent to the `else` output.

### Usage

#### Input Parameters

| Parameter                     | Type         | Description                                                        |
| ----------------------------- | ------------ | ------------------------------------------------------------------ |
| `expression1` - `expression5` | `expression` | Conditional expressions for respective outputs (`out1` to `out5`). |
| `else`                        | `default`    | Messages that do not match any condition are sent here.            |

Each expression supports **AND/OR logic**, allowing complex conditions.

#### Supported Operators

| Operator   | Description                                      |
| ---------- | ------------------------------------------------ |
| `=`        | Equal to                                         |
| `!=`       | Not equal to                                     |
| `>`        | Greater than                                     |
| `>=`       | Greater than or equal to                         |
| `<`        | Less than                                        |
| `<=`       | Less than or equal to                            |
| `%`        | Modulo operation (divisibility check)            |
| `empty`    | Checks if the value is empty                     |
| `notEmpty` | Checks if the value is not empty                 |
| `contains` | Checks if a value contains a substring           |
| `range`    | Checks if a value falls within a specified range |
| `regex`    | Matches a value against a regular expression     |

#### Output Parameters

| Output          | Description                                                       |
| --------------- | ----------------------------------------------------------------- |
| `out1` - `out5` | Message is sent to the first matching output based on conditions. |
| `else`          | If no conditions are met, the message is sent to this output.     |

### Instructions

1. **Define Conditions**
   * Configure up to 5 expressions (`expression1` to `expression5`) for routing messages.
2. **Set Operators**
   * Use supported operators to define comparison logic.
3. **Handle Default Cases**
   * If none of the conditions match, the message is sent to `else`.

***


---

# 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.appmixer.com/connector-configuration/utils/controls/switch.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.