Wappler documentation
Data Flow and APIs
Start here for data flow in Wappler: server-side actions, client-side bindings, and your first dynamic data flow.
Use this hub when you want to understand how data moves through Wappler. Start with the mental model, then branch into Server Connect, App Connect, and page binding.
Start with the mental model
App Connect and Server ConnectDecide whether a piece of a feature belongs in the browser, the server action or the database.Load an action on your pageThe complete connection from a saved API action to a visible text binding in App Connect.Workflows: Quick OverviewGet a quick overview of Workflows: the split between Server Connect Actions and App Connect Flows, and how to choose the right starting point.
Server-side APIs and responses
Server Connect actionsCreate API actions, define inputs, query databases and return data to pages.Create your first Server Connect actionA small API action that returns one greeting, with an exact response you can test before connecting a page.Web and Database Server OutputsInspect a database-backed Server Connect action to see where database results become the JSON output your web UI binds to.Using Session VariablesUse session-backed values inside Server Connect actions so identity, permissions, and other secure state stay on the server.Database ManagerConnect a database, design tables and relationships, and inspect records.
Client-side bindings and rendering
App ConnectYour guided index of App Connect tours: reactive model, data components, bindings, events/actions, and common workflows — explained visually in Wappler’s panels and pickers.App Connect Quick OverviewA hands-on intro to App Connect in Wappler: review key components, configure Properties, and attach an event action.Reactive basics (data → UI)A beginner-friendly mental model for App Connect: how data, bindings, events, actions, and Dynamic Attributes combine into reactive UI updates.JSON DataLearn when to use JSON files as a simple data source in Wappler, wire one into a page, and pass that data into components and bindings.Caching API DataSometimes data APIs have restrictions like limits for requests per IP or hourly request limits. In cases like these, it's useful to have data cached for your user. You can do this by using the state mPages and LayoutsStart here to learn how pages and layouts fit in your workflow, then move into Pages Manager, the HTML Editor, and concrete page patterns.