Wire events to actions
Run ordered interactions, refresh data, update state, notify users, and navigate.
Components declare events such as onClick, onChange, onSubmit, or selection events. The available events are specific to the component. Use Properties' event controls to attach an ordered list of actions to a declared event.
Add an action
- Select a component and find its event list.
- Choose + Add action beside the intended event.
- Select the action type and fill in its fields.
- Add an optional condition if the action should run only for a particular state.
- Inspect Preview, save, and test real execution in the app.
| Action | What it does |
|---|---|
| triggerDataSource | Fetch records, run an eligible workflow, or watch upload-correlated work. |
| setStateValue | Set an app-state key, including a supported dot path. |
| setComponentValue | Set the target component's published value. |
| showNotification | Display an info, success, warning, or error message. |
| navigate | Open a relative or HTTP/HTTPS address in the same view or a new tab. |
Actions execute sequentially and await each action before continuing. A false condition skips that action. The first executor or expression error aborts the rest of the chain and reports the failure. A newer operation can supersede an older run/watch and stop the stale chain; a polling deadline also prevents later actions from claiming results were observed.
Fetch, run, or watch
fetch rereads the source. run starts its bound workflow and requires Allow run trigger; app-output sources cannot be run. watch follows a background run for a particular upload correlation id and requires a non-empty ingestId binding, such as the uploader's lastIngestId. Remove ingestId when changing away from watch.
When watching is unavailable in a preview or host, watch falls back to a records fetch rather than starting work. Preview does not support real run triggers.
Keep messages truthful
Place success notifications after the action whose completion they describe. Navigation accepts relative addresses and HTTP/HTTPS, not script or opaque schemes. Changing an action's type replaces its type-specific configuration, so recheck every required field.
Use the Action reference for required settings, defaults, examples, conditions, and exact execution limits. A record-read error is exposed on the source and can allow a chain to continue; guard follow-up messages with the source error state.
See Workflow sources, Bindings, and Preview.