Workflow Recipes

Workflow Recipes

Use these workflow how-tos when you need an immediate next action instead of a broad conceptual overview. Each path is meant to connect a real task to the right Wappler surface, so you can start from the problem you have and move into the focused tour that solves it.

Decide whether the work belongs on the server or in the client.

Start in the right family instead of mixing concepts.

Use the umbrella hub for comparison, not for deep implementation detail.

Choose Server-Side Logic

Start with Server Connect Actions when the workflow must reach protected data, enforce security, or expose a reusable endpoint for the rest of the app.

Use server-side logic for trusted data work.

Keep auth and protected business rules there.

Continue into the Server Connect family for actual building steps.

Choose Client-Side Logic

Start with App Connect Flows when the workflow reacts to user interaction, page state, or client-side branching that does not require server trust boundaries.

Use client-side flows for interaction-driven logic.

Keep UI responsiveness and page behavior there.

Continue into the App Flows family for focused editor guidance.

Switch Families Cleanly

If your first guess was wrong, switch families deliberately instead of forcing one tool to do another tool’s job. The clean handoff is part of the product’s learning model.

Stop and re-evaluate where the logic should run.

Switch families before the solution gets tangled.

Use the Workflows hub whenever you need to re-orient.

Next steps

Return to the Workflows tours menu to continue with quick orientation, workflow guidance, or concept reference.

Use Quick Overview when you want the short mental model.

Use General Usage for the umbrella workflow.

Go deeper through Server Connect or App Flows when you are ready to build.