> This page is for version Scripted.
> For other versions, use one of these documentation indexes:
> - Generative (default): https://developers.ada.cx/generative/llms.txt
> - Scripted: https://developers.ada.cx/scripted/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.ada.cx/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.ada.cx/_mcp/server.

# Create selectable menus using the List Option block

## Overview\[#UUID-7bf65d31-e795-3312-6f22-c280b410f9f4_id_360041489454_id_h_01G3BW84QX9AXEAWCDD42EECXC]

The List Option block lets your bot offer chatters a list of selectable
items. The item the chatter selects is saved as a variable to be used as
you see fit. You can create the list of options manually, or populate
the list with saved variables.

> **Note**
>
> This feature may not be included with your organization's subscription
> package. For more information, see Ada's
> [Pricing](https://www.ada.cx/pricing) page, or contact your Ada team.

![](/_fern-files/_img/c76c2ee2678a55e64af0e98c5c9adbc6516635f3b191c3c8c9c31367a48be7ac.webp)

Here are some additional use cases for the List Option block:

* Selecting a product (e.g., retail item selection)

* Selecting items from an order list (e.g., to indicate an item missing
  from a delivery)

* Identifying reasons for requesting an agent during the handoff process

> **Note**
>
> The List Option block works a bit differently on social media platforms.
> To see how each platform handles different blocks, see [Feature compatibility](/scripted/docs/integrate-ada-with-other-tools/use-ada-with-social-media-channels#UUID-add4993d-32b7-84c3-56fc-c28cb1d301a9_section-idm43361126183228).

## Use the List Option block\[#UUID-7bf65d31-e795-3312-6f22-c280b410f9f4_id_360041489454_id_h_01G3BW8C5ZZCP4BSN6SA2G3QNV]

1. On the Ada dashboard, go to **Build** > **Answers**. Then, select an Answer or create a new one.
2. If you want the options in your list to populate dynamically from an API call, do the following:
   1. Set up an [HTTP Request block](/scripted/docs/build-and-maintain-your-bot/work-with-blocks-and-apps/make-api-requests-using-the-http-request-block) in your Answer.
   2. Use a [data key](/scripted/docs/build-and-maintain-your-bot/work-with-blocks-and-apps/make-api-requests-using-the-http-request-block#UUID-e5670829-5c08-ccd9-17b6-c4be1397be71_section-idm4491529808793633386703349451.mdx) to save the required portion of the API response as a variable.
      That portion of the API response is what you’ll use to dynamically
      generate your list.
      > **Warning**
      >
      > Variables are limited to 100,000 characters. Particularly when you’re
      > saving all or part of an API response as a variable, take care that you
      > don’t exceed this limit. If you do, you may start seeing errors, because
      > your bot might not be able to correctly parse your variable content.
      >
      > Other than the variable text limit, the only limitation on how many
      > options can be in your list is that every message Ada serves must be
      > under 10KB. Messages virtually never reach this size.
3. Drag and drop the **List Option block** from the block drawer into the Answer editor.
4. In the text field at the top of the block, enter a message
   prompting the chatter to make a selection. It could be as simple as
   “Pick an option,” but should also include specific instructions when
   necessary. This bubble will appear right before the list of
   options.
5. Under **Options Source**, choose how you want to
   populate the list items. Then, depending on your choice, configure how
   you want the list items to appear under **Option
   Setup**.
   * Click **Manual** to use a static list of options.
     You can type these out yourself, or use variables.
     #### Configure manual list options
     By default, when a chatter makes a selection, your bot saves the text
     they selected as the variable value. Optionally, you can define custom
     values for each option for your bot to save, instead of the text that
     appears to chatters. When configuring manual list options, you have the
     option of managing those items separately:
     * **Label**: The text that chatters see
     * **Value**: The text that your bot saves when the chatter makes a selection
     If you choose to make custom labels and not separate values, your bot will save the label text upon chatter selection instead.
     1. Under **Label**, enter the labels you want chatters
        to see. You can type out text, use variables, or use a combination of
        the two.

        To add an option to the list, click **Add Option**. To
        delete an option, hover your cursor to the right of an option row and
        click the **Delete** button that appears.
        > **Note**
        >
        > If an option label only consists of a variable, and that variable is
        > empty, that option won’t appear to chatters.
     2. In some cases, you may need to save the chatter’s selection in
        the dashboard differently from how it appears to them. To do this,
        toggle on the **Assign different values from label** option. Then, in the **Value** column that appears, enter
        the values you want to save in your variables.
        > **Tip**
        >
        > Different values can be useful in use cases like multilingual bots
        > that have manual translations. You may want to use translated variables
        > so chatters see the options in their languages, but behind the scenes,
        > you may want the saved variable to be in English for all chatters.
        >
        > Note that if your bot uses automatically generated text, values are
        > always stored in English in the back end, regardless of the language
        > that chatters see.
   * Click **Dynamic** to use a dynamic list of options
     from an API response. In this case, you must save an array from the API
     response so you can use all instances of an attribute in the array to
     appear as your list options.
     #### Configure dynamic list options
     1. In the List Option block, beside **Data Source**, enter the variable you saved the API response portion in.
     2. Beside **Label Key Template**, enter one or more
        attributes that appear in the variable to appear in the list
        options.
        * To include an attribute, put it in curly braces: `{{item_name}}`.
        * You can include multiple attributes, and have additional text in
          the items too: `{{item_name}}, ordered on {{order_date}}`.
6. Select the **Multiple Select** checkbox to allow chatters to select more than one option.
7. Under **Error Answer**, select an Answer to appear as a fallback if an error occurs.
8. Under **Save Response as Variables**/**a
   Variable**, create or select a variable to save chatters’
   responses in, so you can use them later.
   For more information about the types of variables you can save responses
   in, see [Understand variable types](#UUID-7bf65d31-e795-3312-6f22-c280b410f9f4_id_360041489454_id_h_01G3BW8HGZQP6F8TEAMCYFD4NQ).
   > **Note**
   >
   > If you turned on Multiple Select, you must save the response in a
   > List type variable.
9. Under **Capture Settings**, choose whether you want
   to allow chatters to advance through the Answer without making a
   selection.
   * Turn on the **Response Required** toggle to ensure
     that chatters provide a response before being able to advance through
     the Answer.
     * If they don’t, and they click Never mind instead, your bot will exit the Answer flow and redirect the chatter to the Cancel Capture Answer.
     * If the Response Required toggle is off, chatters will see a Skip
       button that they can use to move on to the next block in your Answer.
   * If you turned on the Response Required toggle, a **Show
     Cancel Button** toggle appears. Turn this toggle on to show chatters a Cancel button. If a chatter clicks it, your bot will exit the Answer flow and redirect the chatter to the Cancel Capture Answer.

A completed List Option block looks like this:

![](/_fern-files/_img/66630f31852f5e0185b47edddd567524f77c9fc27e132df2b0c9f0c8765a77ae.webp)

### Understand variable types\[#UUID-7bf65d31-e795-3312-6f22-c280b410f9f4_id_360041489454_id_h_01G3BW8HGZQP6F8TEAMCYFD4NQ]

When creating a target variable for your options list, the variable type
you choose depends on whether you allow the chatter to select only one
item from the options list or multiple items. If you have multiple
select enabled, you must save the response in a List variable.

* **Text** – A Text target variable can be used with
  any type of option variable.
* **Number** – To use a Number target variable, all
  option variables in the list must be number variables.
* **Yes or No** – The Yes or No target variable can
  only be used when the option variables in the list are also yes or no
  variables.
* **List** – If you allow your chatters
  to select more than one item from the options list, you must save their
  selections as a List variable. Items collected in a List variable are
  separated by semicolons.

  Once collected using the multiple select functionality, List
  variables can be used as you would any other variable. Here are a few
  examples:
  * Added to a block to relay the information back to the user, with
    each item separated by semicolons (e.g. “The items your shipment was
    missing are: lipstick; mascara; blush.”)
  * In a Conditional block
  **Example:** When asking a chatter to
  indicate items missing from an order, assume you have separate sets of
  instructions for chatters missing one item versus those who
  are missing multiple items. You can use the Conditional block to serve
  one set of instructions if the list length equals one item, and the
  second set of instructions if the list length equals two or more
  items.

### Nesting in other blocks\[#UUID-7bf65d31-e795-3312-6f22-c280b410f9f4_id_360041489454_id_h_01G3BW8RV40FSKY52CTXDH72J1]

You can nest the List Option block in other Operations blocks, such as
the Conditional block or the Scheduled block. This is useful if you want
to provide different lists of options to the chatter based on
conditionals or a predetermined schedule.

---

Have any questions? Contact your Ada team, or email us at [](<mailto:help@ada.support%20%E2%80%9CHelp Docs inquiry%E2%80%9D>).