Feature request - Flows

Feature Request: Structured User Input Options in Quick Flows

Feature Summary

Add drop-down menus and multiple-choice check-boxes as user input step types in Quick Flows, allowing Flow creators to define a fixed set of selectable options rather than relying solely on free-text input.

Problem Statement

Currently, the User Input step in Quick Flows only supports free-text entry. When multiple users run the same Flow, they may phrase their inputs differently — even when they mean the same thing. This inconsistency can lead to varied or unreliable AI outputs, since the model interprets each phrasing differently.

Example: A Flow designed to extract specific data from an uploaded document might ask the user “What type of data do you want to pull?” One user might type “headcount numbers,” another might type “HC data,” and another might type “staffing counts” — all meaning the same thing but potentially producing different results.

Proposed Solution

Allow Flow creators to add structured input steps with:

  • Drop-down menus — A single-select list of predefined options (e.g., “Select report type: Headcount | Volume | Quality | Safety”)
  • Multiple-choice check-boxes — A multi-select list where users can choose one or more predefined options (e.g., “Select data points to extract: ☐ Headcount ☐ Rate ☐ Idle Time ☐ Volume”)

Benefits

  • Consistency — Every user selects from the same set of options, eliminating variation in phrasing
  • Accuracy — The AI receives a standardized input, producing more reliable and aligned outputs across users
  • Ease of use — Reduces cognitive load on the user; they don’t have to guess what to type
  • Scalability — Makes Flows more shareable across teams since anyone can run them without needing to know the “right” way to phrase inputs

Use Case

As a manager running a Flow that processes uploaded documents (e.g., associate feedback, shift reports), I want to select from predefined categories so that the AI extracts the correct data every time — regardless of who runs the Flow.

Hi @austfarr

Welcome to the Quick community!

Thank you for bringing this to our attention. At AWS, our roadmap is primarily driven by our customers, and your feedback plays an important role in helping us build a better service. I’ve tagged this as a feature request to ensure visibility with the product team. We truly appreciate you taking the time to share this. It’s suggestions like yours that help us improve!

Hi @austfarr,

Just wanted to inform you that I will leave this post marked as a Feature Request and archive it so that someone from the AWS Team may address it in the future.

Thank you!