Workflows: Quick Overview

Workflows Overview

Workflows is Wappler’s umbrella for visual logic builders. The first thing to understand is not every workflow belongs in the same place: server-side logic and client-side logic are separate on purpose.

Server Connect Actions run on the server and handle data, security, and reusable endpoints.

App Connect Flows run on the client and handle UI-driven logic and branching.

The fastest way to stay productive is to start in the family that matches where the logic should run.

Two Logic Areas

The core split is simple: use Server Connect Actions when the work must happen securely on the server, and use App Connect Flows when the work is driven by client-side state or interaction.

Server-side: data access, auth, protected actions.

Client-side: UI state, event flow, conditional interaction.

If you are unsure, ask where the data and trust boundary belong.

Family Entry Points

This Workflows family is an organizer, not the deepest editor guide. Its job is to send you into the correct dedicated family quickly instead of letting you mix mental models.

Use the guided path when you want help choosing.

Use the dedicated Server Connect family for server-side building.

Use the dedicated App Flows family for client-side building.

Conclusion

The beginner takeaway is simple: Workflows is the map, not the final destination. Pick the logic area that matches your task, then go deeper there.

Start with the guided path if you are still unsure.

Choose Server Connect for secure server-side logic.

Choose App Connect Flows for client-side interaction logic.