Preview: https://get-element-value.bubbleapps.io/version-test/index?debug_mode=true
Editor: Get Element Value | Bubble Editor
Plugin Page: Get Element Value Plugin | Bubble
How to Use the GetValuePlugin (clear, consistent steps)
Prerequisites (do this once)
Step 1 — Enable ID attributes in Bubble
-
Go to Settings → General.
-
Scroll to the bottom → click Advanced options.
-
Check Expose the option to add an ID attribute to HTML elements.
Use inside a Repeating Group (primary use case)
Step 1 — Add a Repeating Group (RG)
-
Drag a Repeating Group onto the page.
-
Set Type of content (e.g., Thing).
-
Set Data source (e.g., Do a search for…).
Step 2 — Add elements into the RG cell
-
Inside the cell, add:
-
an Input element (the one whose value you want), and
-
the GetValuePlugin element.
-
Step 3 — Give the Input an ID attribute
Choose one pattern depending on what you want:
-
Collect all cell inputs (one ID for every cell)
Set the Input’s ID attribute (static text) to something like:
input
(Every visible cell will contain an Input with the same ID.) -
Isolate the current cell’s input (unique ID per cell)
Set the Input’s ID attribute to a dynamic value using the cell index, e.g.:
input-
+ Current cell’s index
(This renders asinput-1
,input-2
, … so each cell is unique.)
Step 4 — Configure the GetValuePlugin’s Target Input ID
Match exactly what you set on the Input:
-
To collect all values across visible cells:
target_input_id = input
(the same static text as the Input ID) -
To isolate the current cell’s value:
target_input_id = input-
+ Current cell’s index -
To read a different cell (relative lookups):
-
Next cell:
input-
+ (Current cell’s index + 1) -
Previous cell:
input-
+ (Current cell’s index − 1)
-
Tip: In Bubble, build these with the dynamic expression editor:
- Type
input-
, then insert Current cell’s index, and (optionally) add+ 1
or- 1
.
Step 5 — Use the exposed state in Bubble
-
The plugin currently exposes
InputsValueList
(a list of texts).-
If you used a static ID (e.g.,
input
), the list contains one item per matching visible Input across cells. -
If you used a unique ID per cell (e.g.,
input-Current cell's index
), the list will typically have one item (the current cell’s value). You can refer to it as:first item
if needed.
-
Step 6 — Behavior notes (so it “just works”)
-
Values update automatically on typing / change and when elements appear/disappear.
-
Only visible elements are included (because the selector uses
:visible
). Hidden cells/inputs won’t contribute to the list.
Use outside a Repeating Group (simple page-level use)
Step 1 — Add your Input
-
Place an Input anywhere on the page.
-
Set its ID attribute (e.g.,
email-input
).
Step 2 — Add the GetValuePlugin
-
Place the GetValuePlugin element anywhere on the page.
-
Set Target input ID to match exactly (e.g.,
email-input
).
Step 3 — Read the exposed state
- Use
InputsValueList
. Since there’s usually just one matching element, it will be a list with one item. Use:first item
where a single text is expected.
Quick reference: what the plugin “sees”
-
It does not split values by commas/spaces/newlines.
-
It creates a list by aggregating across all visible elements whose ID equals your Target input ID.
-
INPUT
→ uses the input’s full.value
as-is. -
SELECT
(single-select) → uses the selected option’s text. -
SELECT[multiple]
, checkboxes, radios are not specially handled (they contribute one item only).
Troubleshooting & gotchas
-
IDs must match exactly (case-sensitive, no extra spaces).
-
Duplicate IDs across cells are intentional for “collect all values”; if you intended one value, give each cell a unique ID and set the plugin’s target to that unique value.
-
Hidden cells/inputs won’t appear in the list (
:visible
). -
If your app expects a single text, but you’re using the current list-based plugin, use
:first item
(or switch the plugin to expose a single text as discussed previously).