---
title: Carousel user input control
description: Use the Carousel user input control in a Virtual Agent topic to present a prompt and a horizontal series of labeled images. The user can select a single item from the carousel.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/conversational-interfaces/virtual-agent/va-carousel-input.html
release: brazil
product: Virtual Agent
classification: virtual-agent
topic_type: reference
last_updated: "2026-09-10"
reading_time_minutes: 4
keywords: [Carousel, user input, control, node, Virtual Agent, designer, images, photos]
breadcrumb: [Assistant Designer user input controls, Assistant Designer interface reference, Reference, Virtual Agent, Conversational Interfaces]
---

# Carousel user input control

Use the Carousel user input control in a Virtual Agent topic to present a prompt and a horizontal series of labeled images. The user can select a single item from the carousel.

**Tip:** If you want to change the default number of listed items per page, you can modify the **com.glide.cs.picker\_page\_limit** system property. The default value is 10.

## Carousel input control properties

**Note:** The Carousel user input control is not supported in ServiceNow Otto in Virtual Agent.

<table id="table_qmh_lgk_h1c"><thead><tr><th>

Property

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Node name

</td><td>

Name that identifies this node in the topic flow.

</td></tr><tr><td>

Variable name

</td><td>

Name of the variable that stores the user response to this prompt. The variable name is automatically created from the **Node name** property.

</td></tr><tr><td>

Allow automatic slot-filling

</td><td>

Toggle to allow this node’s value to be automatically set by other nodes, as well as during topic discovery. When this toggle is activated, the Detail description field changes from dynamic Data Pill Picker and script options to a static text field.

</td></tr><tr><td>

Detail description

</td><td>

Description of the information that you need from users. If the **Allow automatic slot filling** toggle is deactivated, you can create a dynamic detail description by selecting the Data Pill Picker icon \[Omitted image "variable-reference-picker.png"\] Alt text: to define conditions, or select the Open Editor icon \[Omitted image "icon-script.png"\] Alt text: to enter a script. If the **Allow automatic slot filling** toggle is activated, you can only enter a static description.

 \[Omitted image "LLM-input-discoverable-toggle.png"\] Alt text: When the Allow automatic slot-filling toggle is inactive, the detail description includes Data Pill Picker and script dynamic options. When the toggle is active, the Detail description field becomes static.

</td></tr><tr><td>

Define carousel items

</td><td>

Use a script to create items for selection in your carousel. The script should return an array containing one or more items. See the Example carousel item expression section in this topic.

</td></tr><tr><td class="sub-head" colspan="2">

Advanced \(optional\)

</td></tr><tr><td class="sub-head" colspan="2">

Enforce user prompt

</td></tr><tr><td>

Enforce user prompt

</td><td>

Toggle to open a field for a custom message shown to the user instead of the message generated by the large language model \(LLM\). You can create custom messages in plain language, input a script, or define conditions with the data pill picker.

</td></tr><tr><td>

Validation

</td><td>

Add a script to validate the user input. For example, check if the user entered a valid email address.

</td></tr><tr><td>

Additional instructions for LLM

</td><td>

Further instructions to the LLM, such as adding data formats, restrictions, or default values for user responses. You can create additional instructions in plain language, input a script, or define conditions with the data pill picker.

</td></tr><tr><td class="sub-head" colspan="2">

Hide or skip this node

</td></tr><tr><td>

Conditionally show this node if

</td><td>

No-code condition statement or low-code script that specifies a condition for presenting this node in the conversation. The condition must evaluate to true. This field is not applicable when the Carousel node is used within the Input Collector node.

</td></tr><tr><td>

Allow user to skip this node if

</td><td>

No-code condition statement or low-code script that specifies a condition for letting users skip this node in the conversation. The condition must evaluate to true. You can set this field using either the condition builder or a script.

 If users enter a value such as `skip this step` when the conditions do not allow skipping, they receive a message saying the node cannot be skipped and are re-prompted to provide an answer.

</td></tr></tbody>
</table>## Example Carousel input control

<table id="table_tzy_zc2_d1c"><thead><tr><th>

Carousel properties

</th><th>

Carousel prompt

</th></tr></thead><tbody><tr><td>

\[Omitted image "va-carousel-llm-3.png"\] Alt text: All basic Carousel user input fields are openly available. Select any of the advanced options to toggle them open individually.

</td><td>

\[Omitted image "va-carousel-native.png"\] Alt text: An example chat in which the prompt asks, "Please select an image from the carousel."

</td></tr></tbody>
</table>## Example carousel item expression

```
(function execute() {
    var options = [];
       options.push(
            {
                'Name': 'Item 1',
                'Value': 'item_1',
                'Description': 'Acme keyboard model 200',
                'Body': 'https://images.pexels.com/photos/688666/pexels-photo-688666.jpeg'
                'Card_name': 'AcmeCard'
                'Card_data': {"identifier":"IT hardware and software","header":"Acme keyboard model 200","description":"The model 200 keyboard is a ten-key-less keyboard."}
            }
       );
       options.push(
            {
                'Name': 'Item 2',
                'Value': 'item_2',
                'Description': 'Acme keyboard model 300',
                'Body': 'https://images.pexels.com/photos/916472/pexels-photo-916472.jpeg'
                'Card_name': 'AcmeCard'
                'Card_data': {"identifier":"IT hardware and software","header":"Acme keyboard model 300","description":"The model 300 keyboard is a full-size keyboard with a ten-key pad."}
            }
       );
       return options;

})()
```

The script in the Carousel Item Expression property defines and returns an array containing the items that appear in your carousel. The elements of this array must contain `name`, `value`, and `body` keys. In the example, the script creates an array called `options` and adds two elements, each with the required keys. The images here are hard-coded as an example.

|Key|Description|
|---|-----------|
|Name|Name of the carousel item. This name is shown below the image on the carousel.|
|Value|Value for the item. When a user selects a carousel item, this value is stored in the variable named in the Variable name property.|
|Description|Text string that describes the carousel item. The description is shown below the image name. A carousel with more than three items displays left and right arrows for scrolling through the images and a **Select** button under each item. If a description is over 140 characters, users can expand the content.|
|Body|Image used in the carousel item. The value is a URL for an image file.|
|Card\_name|Text string header identifying the card shown in the carousel.|
|Card\_data|Array containing text strings to be presented on the card. Values include identifier, header, and description.|

## Channel support

|Channel|LLM support|Constraints|
|-------|-----------|-----------|
|Microsoft Teams|Not Supported|None. If the carousel contains more than 10 items, users must select **Next** to review the remaining items.|
|Slack|Not Supported|None|
|SMS Twilio|Not Supported|Not applicable|
|WhatsApp|Not Supported|None|
|Google Chat|Supported|None|

**Parent Topic:**[Assistant Designer user input controls](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/conversational-interfaces/virtual-agent/va-user-inputs.md)