Workflows Reference

Reference tour for Workflows: taxonomy of server-side and client-side workflows, where each family fits in Wappler, and how they connect.

Introduction

Think of this reference tour as a workflow map across the main Wappler areas you revisit while building and shipping an app. It helps you recognize where common tasks begin, how one area hands off to another, and which follow-up tours deepen the part of the workflow you need next.

Workflows is the umbrella family, not the only editor guide.

Server Connect Actions and App Connect Flows solve different classes of problems.

The clean split is what keeps the manual and onboarding understandable.

Umbrella Family

Use this family when you need orientation across workflow types, cross-links into the right area, or a compact explanation of the server-side versus client-side split.

Navigation and comparison live here.

Detailed building steps live in the sub-families.

This is the reference layer for the overall model.

Server Versus Client

The core reference distinction is execution model: Server Connect Actions execute on the server, while App Connect Flows execute in the client context.

Server execution supports protected data and reusable endpoints.

Client execution supports interface-driven flow and state transitions.

The distinction is architectural, not cosmetic.

Dedicated Families

Use the dedicated families for depth: Server Connect Actions for server-side workflows, and App Connect Flows for client-side flow design and editor usage.

Dedicated families carry the implementation detail.

This family carries the cross-family map.

That separation keeps both docs and onboarding easier to grasp.

Next steps

Continue with the Workflows hub for guided entry points, or move into the dedicated Server Connect or App Flows families for deeper detail.

Return to the Workflows hub.

Use Server Connect for server-side workflow detail.

Use App Flows for client-side workflow detail.