Skip to main content
App builderWeb

Build a visual workflow

Connect actions on the workflow canvas for the element that starts the flow.

1 min readBuild at your own paceOpen Apps

A workflow describes what happens after an event on a particular element. Use it to connect navigation, data operations, conditions, and feedback.

Open the correct flow​

  1. Select the button or other element that starts the interaction.
  2. Scroll its settings to Actions and choose Add action.
  3. Choose More actions... to open that element's workflow canvas.
  4. Add an action from the action menu and configure its settings.
  5. Connect the next operation and test the sequence in Preview.

The canvas opens for a specific element. If you are editing the wrong flow, return to the editor and select the intended trigger first.

Follow a small example​

FOLLOW ALONGFrom a button to a workflow

Open the right flow, add an action, and configure its result.

Example project
Add action menu in the selected element’s settings, with More actions... at the bottom.
Full interface

Select a trigger element, scroll its settings to Actions, and choose Add action. Scroll to find More actions... at the end of the menu.

Web interface captured on 5 Nov 2026 with example content. Choose a numbered note to take a closer look.

Open the flowAppStruct web interface · example project
Add action menu in the selected element’s settings, with More actions... at the bottom.

The visual example runs Show toast → Go to screen on Submit request. Add and configure a data action separately when the form must save a record. A toast by itself does not persist the inputs.

Choose an event​

The element's event selector exposes On Click and On Page Load. Configure the next operations as part of the same action chain.

Keep the result clear​

For a request form, a useful small flow is: read inputs, create a row, then show confirmation or navigate to a detail screen. Configure the actual action fields; a node's label alone does not determine its data or destination.

Test the first event, conditions, saved result, and final screen. Handle an unsuccessful request without presenting it as a successful save.

Have a question?Find an answer in the FAQ