Decision point
Learn when a single event action is enough and when the workflow needs its own staged flow.
Flows (multi-step client workflows)
Learn when App Connect flows are worth introducing, how they differ from a single event → action handler, and how to think about multi-step client workflows before building them.
Introduction
Section titled “Introduction”This introduction sets the decision rule for flows before you start building one. You will compare a simple event handler with a staged workflow, identify the kinds of UI tasks that benefit from multiple ordered steps, and see how flows keep that logic readable as it grows.
Tour goals
Section titled “Tour goals”By the end of this tour, you should be able to decide whether a feature needs a flow at all, describe the sequence of steps the flow must coordinate, and recognize the parts of the Wappler UI where you inspect and maintain that workflow.
Sequence
Break a client workflow into clear ordered steps so side effects stay readable.
Maintenance
See where flows stay easier to reason about as conditions, async work, and branching grow.
Compare a simple event handler with a true multi-step workflow
Identify the steps, decisions, and side effects the client flow must coordinate
Use that mental model to choose the right App Connect tool before implementation
When to use flows
Section titled “When to use flows”Flows are useful for multi-step UI workflows where you want a clear sequence; simple interactions can stay as a single event → action.
Wrap-up
Section titled “Wrap-up”Review what you did and choose a next tour.
Next steps
Section titled “Next steps”Pick a related tour to continue.