Request lifecycle
Follow a request from trigger to executing state, response data, and completion.
Server Connect components (data + forms)
Load data and submit forms via Server Connect components, using built-in state (executing/lastError/data).
Introduction
Section titled “Introduction”This tour introduces the App Connect components that talk to your server actions. You will see how Wappler models requests, responses, execution state, and errors in the page, and how those component outputs become the inputs for bindings, loading indicators, and follow-up actions.
Tour goals
Section titled “Tour goals”By the end, you should understand the whole client-to-server loop in Wappler: which component sends the request, where request state is exposed during execution, how returned data becomes available to the page, and where error handling fits into the same declarative workflow.
Bound server state
Use executing, data, and lastError as normal App Connect values in the UI.
Action chaining
See how request components fit into larger event and action sequences on the page.
Inspect the components that load data and submit forms
Understand how request state is exposed for loading and error UI
Reuse returned server data in bindings and follow-up actions
Where you configure it
Section titled “Where you configure it”Use App Structure to select your API Form / API Action components and Properties to bind inputs, outputs, and actions.
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.
Bind API Form inputs
Handle executing/data/lastError
Chain actions after requests