Dropdown Default Value Doesn’t Register in Workflows/API Calls Unless Clicked

Bugs
1

Hi all,

I’ve run into a frustrating (and I believe under-documented) issue that’s breaking my API workflows — and I’ve confirmed it through debugger testing and forum reports:

:brain: Problem Summary

Dropdowns do not pass their default value into workflows unless the user manually interacts with the element.

Even when:

  • A default value is statically set in the editor (e.g. “Fantasy”)
  • The dropdown is marked as “This input should not be empty”
  • A text element shows Dropdown's value correctly on page load

…when passed into an API call or used in a conditional, the dropdown’s value is treated as empty.

:test_tube: Repro Steps

  1. Create a dropdown
  2. Set a default value (static or dynamic)
  3. Create a button → “Call API with dropdown value”
  4. Preview the app
  5. Observe debugger/API call payload

:fire_extinguisher: Result

  • UI: The dropdown shows the correct default (e.g., “Fantasy”)
  • Debugger: The value is (empty)
  • API: Receives null

Only after clicking the dropdown does the value become available to the workflow engine.

:white_check_mark: Expected Behavior

If a default is set, it should be passed into workflows/API calls on page load without needing user interaction.

:puzzle_piece: Workaround

I’ve been forced to:

  • Use custom states and assign values on page load
  • Or replace dropdowns with radio buttons or RG-based pills

…but this breaks the clean dropdown UX and feels like a hack for something that should “just work.”

:folded_hands: Request

Please confirm if this is:

  1. A known bug (and tracked)
  2. An intentional limitation (and should be documented)
  3. A candidate for engine fix (dropdown defaults → workflow context)

Thanks in advance. I’d love clarity — this is blocking a production MVP and hard to debug without insider knowledge of how Bubble binds default inputs.

2

This topic was automatically closed after 14 days. New replies are no longer allowed.