Select Block - Flex Forms

The Select block (select) is the compact menu for choice questions — single by default, or multiple chips when enabled.

Business Use Cases

Categorization

Ask users to categorize their support ticket (e.g., Billing, Tech Support, Sales).

Role Selection

Determine a user’s job title or industry during a B2B onboarding flow.

Multi interests

Enable Multiple so respondents can pick several topics or skills as chips.

Configuration & Usage

Deploy to Canvas

Drag the Select block from the Component Catalog onto the Canvas.

Define Options

On the canvas, add option rows (label per row). Each option stores a stable value under the hood.

Single or multiple

In settings, leave Multiple off for one answer, or turn it on for multi-select chips.

Enable Search (Optional)

If your list has more than 10 items, toggle Searchable so users can filter by typing.

Default value (Optional)

In settings, turn on Default value and pick an option by its label (with Multiple, pick one or more).

Technical Configuration Schemas

Visuals & UI
Behavioral Features
Data & Validation

string

default:"md"

The visual size of the dropdown field. Available options are sm, md, and lg.

string

default:"bordered"

The aesthetic style of the dropdown wrapper. Options: bordered, flat, soft, faded, underlined.

string

default:"neutral"

Color of selected chips when Multiple is enabled.

boolean

default:"true"

Adds a clear control so the respondent can empty the field.

Data Payload Architecture

Single-select saves one Value. With Multiple enabled, the field saves an array of values.

{
  "submission_id": "sub_419",
  "data": {
    "support_department": "dept_billing",
    "interests": ["php", "react", "design"]
  }
}

[
    'support_department' => 'dept_billing',
    'interests' => ['php', 'react', 'design'],
]

Deep Dive: Labels vs. Values

When configuring a Dropdown, you must define a Label and a Value for every option.

Label: What the human user sees on the screen (e.g., “Senior Software Engineer”).
Value: The raw data saved to the database (e.g., role_eng_snr).

By separating the Label and Value, you can change the visual text at any time without breaking your database schemas, Zapier workflows, or internal reporting logic. The Value acts as an immutable primary key.

Pro Tip: Always use lowercase, snake_case strings for your Values to ensure maximum compatibility with external APIs.

Best Practices & FAQs

Single vs Multiple

Leave Multiple off when exactly one answer is required. Turn it on when respondents should pick several options — selections appear as chips.

Dropdowns vs Radio Buttons

If you have 4 or fewer options and need a single answer, use a Multiple Choice (Radio) block instead. Hiding 3 options behind a click adds unnecessary friction. Use Dropdowns when you have 5+ options, or when you need multi-select chips.

​Business Use Cases

Categorization

Role Selection

Multi interests

​Configuration & Usage

​Technical Configuration Schemas

​Data Payload Architecture

​Deep Dive: Labels vs. Values

​Best Practices & FAQs

Business Use Cases

Configuration & Usage

Technical Configuration Schemas

Data Payload Architecture

Deep Dive: Labels vs. Values

Best Practices & FAQs