# Boolean

A simple on/off or true/false input, displayed as a switch in the **Email Editor**.

Works great for:

* **Show/hide** specific elements, i.e. making a CTA button optional.
* **Toggle direction**, i.e. in a component showing an image on the left, and a text on the right, you can make a toggle to allow the marketeer to switch the direction, so text shows on the left and image on the right.

### Template Editor

<div align="left"><figure><img src="/files/2p9l8IMj66wMHp2hI2m1" alt=""><figcaption><p>This is how it looks in the Template Editor</p></figcaption></figure></div>

<figure><img src="/files/Y3Nqp4gRoB9fVGH8mikk" alt=""><figcaption><p>This is how it can be applied in the code. Notice the {% if statement %} wrapping around the TD's</p></figcaption></figure>

Notice how with **Boolean** we can wrap other code bits into a Liquid statement like so:

```liquid
{% if my_input_group_name.my_text_align %}
  <td align="left">
   {% else %}
   <td align="center">
    {% endif %}
```

### Email Editor

<div align="left"><figure><img src="/files/VJQ4L4fdYcU2hSfuSPRC" alt=""><figcaption><p>This is how it looks in the Email Editor</p></figcaption></figure></div>


---

# Agent Instructions: 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:

```
GET https://documentation.alpaco.email/template/input-groups/input-types/boolean.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.