Understanding User Input Block configurations

User Input blocks are designed to efficiently collect responses from users during a workflow. Each block type handles a specific data format, allowing for structured and seamless interactions.

Types of user input blocks

• Customer Details
• Direct Inputs
• Selection Inputs
  • Button Inputs
  • Drop-down Inputs

Collecting contact information (Customer Details)

Admins can choose to collect one or more customer details through this block. The Email field is mandatory, while Name and Phone Number are optional.

For each selected field, the admin can define:

• Message (Required): A custom prompt shown to the customer.

  Example: “Please enter your email”

• Placeholder (Optional): A hint displayed inside the input box.

  Example: “example@example.com”

Data collection sequence

Customer details are always collected in a fixed predefined order based on the fields selected by the admin. This ensures a consistent and logical flow for customers.

Direct Inputs

These blocks gather structured information from the user by allowing them to type directly into input fields. Below are the supported input types available for direct entry.

Selection Inputs

These blocks present predefined choices so users can select rather than type, ensuring consistency in the captured data.

• Button Inputs
  • These blocks allow users to respond by clicking buttons instead of typing, providing a quick and intuitive way to gather input.
  • Get Choice via Yes/No: Displays fixed Yes and No buttons. This input can only be mapped to Boolean type chat fields.
  • Get Choice via Buttons: Displays multiple buttons. This input supports mapping to various chat field types.
• Drop-down Inputs
  • These blocks provide dropdown menus for selecting one or more options.
  • Get Choice via Drop-down: Displays a single-select dropdown that allows selecting one option.
  • Get Choice via Multi-select: Displays a multi-select dropdown that allows selecting multiple options.

Basic configuration for input blocks

All user input blocks except Customer Details support the following shared configuration options:

Defining data for selection input blocks (buttons and drop-downs blocks)

When configuring Button or Drop-down input blocks, you must define the set of options that will be presented to users.

You can define each option by specifying:

• Label: The text shown to the end user (e.g., button text or dropdown item).
• Value: A unique internal identifier that must match a valid option defined for the selected Chat Field.

Load Options from API
A flexible way to load all predefined options configured for the selected API Field Name. After loading, these options can also be manually edited to fit specific needs.

Note:

• Duplicate values are not allowed in options.
• Load options from API is not applicable when Use Temporary Fields is enabled

Dynamically define options with saved API data

As an alternative to manually defining options or loading them from a field’s API configuration, you can dynamically populate selection inputs using data captured earlier in the workflow. This is achieved with the Use Saved API Data option.

Enabling Use Saved API Data allows you to populate Dropdown, Multi-select, or Button choices from a temporary field that holds an array of values returned by a “Trigger Webhook” action.

How to Configure

1. Enable the Feature
   Toggle on the Use Saved API Data option.

2. Select a Temporary Field
   Choose the temporary field that contains your array of data from the Temporary Field Name dropdown.

3. Map the Option Properties
   How you define the options depends on the structure of the array in your temporary field.

   • If your field contains an array of objects: You must map the properties of the objects to the Label and Value for the options.

     • Label: Enter the object property name that will be shown to the user.
     • Value: Enter the object property name that will serve as the unique internal identifier.

     Example: If your temporary field contains [ { "name": "High Priority", "id": 1 }, { "name": "Medium Priority", "id": 2 } ], you would set Label to name and Value to id.

   • If your field contains an array of primitive types: No mapping is needed. The system automatically uses each value for both the Label and the Value.

     Example: If your temporary field contains [ "Open", "Closed" ], the system will create an “Open” option with the value “Open”, and a “Closed” option with the value “Closed”.

Use API in drop-downs

It allows dynamic loading of options for the selected chat field by making an API call at runtime. This ensures that dropdown options are always up-to-date without manual configuration.

Note: Use API is not applicable when Use Temporary Fields is enabled. When Use API is enabled, you do not need to define options, as they will be fetched automatically during workflow execution.

Validations supported in input blocks