> For the complete documentation index, see [llms.txt](https://docs.agenticflow.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agenticflow.ai/workflows/workflow-inputs/multi-select.md).

# Multi-Select

The **Multi Select** control is an input component that allows a user to select one or more options from a list of predefined choices, typically presented as checkboxes.

## When to Use

Use the Multi Select control when you want to allow the user to choose any number of options from a list. This is useful for:

* Selecting multiple features to include in a report.
* Choosing several topics to write about.
* Tagging an item with multiple categories.
* Specifying a list of recipients for a notification.

## How to Add

1. From your workflow's **Build** page, click on **+ Add Input**.
2. Select **Multi Select** from the list of available controls.

## Configuration

* **Title:** The main label for the group of choices.
* **Description:** Optional helper text to provide more context.
* **Options:** This is where you define the items that will appear as choices. Add one option per line.
* **Variable Name:** The name used to access the list of the user's selected values.
* **Optional/Required:** A toggle to specify if the user must make at least one selection.

## Setting Default Values

You can pre-select any number of options as the default:

1. Add all your desired options to the **Options** list.
2. Check the boxes next to the options you want to be selected by default.
3. Click the settings icon (⚙️) at the bottom right of the control.
4. Select **Set Current Value as Default**.

## Accessing the Value

The Multi Select control outputs a **list (or array) of strings**, where each string is one of the selected options. You access this list using its variable name in double curly braces `{{}}`.

For example, if the variable name is `features`:

* The value of `{{features}}` would look like `["SEO Analysis", "Competitor Tracking"]`.
* You can pass this directly to an LLM, which can iterate through the list in its response.
* In a **Map Node**, you can use this list as the input to run a sub-workflow for each selected feature.

### Example

**Goal:** Allow a user to select multiple social media platforms and then draft a post for each one.

1. **Add a Multi Select Control:**
   * Title: "Select Platforms"
   * Variable Name: `platforms`
   * Options:

     ```
     Twitter
     LinkedIn
     Facebook
     ```
2. **Add a Long Text Input:**
   * Title: "Core Message"
   * Variable Name: `message`
3. **Add a Map Node:**
   * **Input List:** `{{platforms}}`
   * **Sub-Workflow:**
     * **Sub-Node 1: OpenAI MCP**
       * **Action:** `Chat`
       * **Prompt:** \`Rewrite the following message to be appropriate for the {{item}} platform:

         {{message}}\`
       * **Note:** `{{item}}` refers to the individual platform name for each iteration (e.g., "Twitter").
4. **Add a Save to File Node:**
   * **Content:** The collected list of drafted posts will be saved: `{{map_1.output}}`


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.agenticflow.ai/workflows/workflow-inputs/multi-select.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.