Data & Variable Actions

These actions refresh data and store values. Use Trigger Data Source to re-run a data source, Control Variable to change a page or app variable, Set URL Parameters to update the page's query string, and Control Local Storage or Control Session Storage to keep values in the browser. The storage actions only write; you read the stored values through bindings.

Actions at a Glance

Adding One of These Actions

1. Select the block that starts the action, for example a Button, and open its Interactions section.

2. Click + (Add Interaction) and choose the Event, for example On Click.

3. In Action, choose the action. Its fields appear below it, as listed in the table.

4. To run more actions after it, expand Callbacks and use Add Action next to On Success or On Failure.

controlDataSource — Trigger Data Source

Re-runs a data source (a query or API binding on the page) on demand. Use it after a record is created, updated, or deleted to refresh bound blocks with fresh data, or to manually kick off a data source configured with Manual run behavior.

Parameters

Tip: Pattern: Wire controlDataSource on the success callback of a mutation action (create, update, delete) to keep the list fresh without a full page reload.

Examples

Refresh a data source after creating a record

{ "actionType": "controlDataSource", "payload": { "dataSourceId": "ds_listOrders", "method": "trigger" } }

setPageVariable — Control Variable

Writes a page variable or app variable. Blocks read the variable through bindings. Variables are reactive in-memory slots — every block or expression bound to the variable re-evaluates immediately when a write lands. The available operations depend on the variable's declared type.

Parameters

Operations by Variable Type

Note: For array variables, Add to End and Add to Beginning take an array and add its items. To add a single item, wrap it in an array, for example {{ [currentRow.productId] }}. A single value that is not an array is rejected and the variable is left unchanged.

Warning: Type gates operations. Using INCREMENT_BY on a string variable will fail silently — the value keeps its previous state. Numeric operations reject non-numeric input. Object MERGE is shallow — a nested object replaces rather than deep-merges.

Examples

Set a string variable

{ "actionType": "setPageVariable", "payload": { "variableId": "var_status", "operationDetails": { "operation": "SET", "value": "active" } } }

Toggle a boolean variable (show/hide a panel)

{ "actionType": "setPageVariable", "payload": { "variableId": "var_showPanel", "operationDetails": { "operation": "TOGGLE" } } }

Increment a counter on each click

{ "actionType": "setPageVariable", "payload": { "variableId": "var_clickCount", "operationDetails": { "operation": "INCREMENT_BY", "value": 1 } } }

Add an item to a cart array

{ "actionType": "setPageVariable", "payload": { "variableId": "var_cartItems", "operationDetails": { "operation": "APPEND", "value": "{{ [currentRow.productId] }}" } } }

Merge new fields into an object variable

{ "actionType": "setPageVariable", "payload": { "variableId": "var_filters", "operationDetails": { "operation": "MERGE", "value": { "status": "{{ select_status['value'] }}", "page": 1 } } } }

setURLParameters — Set URL Parameters

Updates the current page's query string without navigating. For its parameters and an example, see Navigation Actions.

setLocalStorage — Control Local Storage

Writes a value to the browser's localStorage. Local storage persists across browser sessions — it survives page reloads, closing the tab, and reopening the browser. Use it for user preferences or remembered state that should persist indefinitely on the device.

Parameters

Remember a user's preferred theme

{ "actionType": "setLocalStorage", "payload": { "key": "app_preferred_theme", "operation": "SET", "value": "{{ select_theme['value'] }}" } }

Read local storage value in a binding

{{ localStorage['app_preferred_theme'] }}

setInterfaceSessionStorage — Control Session Storage

Writes a value to the browser's sessionStorage. Session storage persists for the duration of the browser session — it is cleared when the tab is closed, but survives page reloads within the same session. Use it for temporary state like form drafts or wizard progress that should not persist between sessions.

Parameters

Save wizard step progress in session storage

{ "actionType": "setInterfaceSessionStorage", "payload": { "operation": "SET_IN", "path": "onboarding.step", "value": "{{ stepper_onboarding['currentStep'] }}" } }

Read a session storage value in a binding

{{ sessionStorage['onboarding']['step'] }}

A dotted path is stored as nested objects, so read onboarding.step as sessionStorage['onboarding']['step'], not sessionStorage['onboarding.step'].

Choosing the Right Storage Mechanism