Server Connect Manager Overview

Server Connect Manager Overview

This tour focuses on the Server Connect Manager in Workflows: browsing Server Connect Actions by type, organizing with folders, searching, and opening an action in the dedicated editor.

Browse

Folders + items Project structure

Find fast

Search actions Quick access

Open editor

Edit steps Full workspace

Start with **Globals** to define shared settings (Database Connections, Mailer settings, Security Providers, and more).

Then use **API** to build your Server Connect Actions (endpoints).

Use folders + search to stay productive in large projects.

Screenshot: Server Connect Manager OverviewClick to open the larger image

Server Connect Manager: groups

The Server Connect Manager is your hub for Server Connect Actions and related server resources. Browse groups, organize with folders, and select an action to open it in the dedicated editor.

The available groups depend on your Server Model, but you’ll usually work in Globals (shared configuration) and API (your actions/endpoints).

Common groups:

• Globals: shared server-wide settings/variables (for example Database Connections, Mailer settings, Security Providers, …)
• API: Server Connect Actions that return JSON (your endpoints)
• Library: reusable modules you can call from multiple actions
• Webhooks: event-driven actions

Often Node.js-only:

• Schedule: run actions on a timer
• Sockets: realtime events
• Modules: packaged server modules/handlers

You can explore each group in the next section — the tour will auto-expand and select them for you.

API (most common)

Endpoints Return JSON

Shared

Globals Library

Node.js extras

Schedule Sockets Modules

Screenshot: Server Connect Manager: groupsClick to open the larger image

Tree groups

Let’s quickly go over the main groups in the tree. Each step auto-expands and selects the corresponding group for you.

Organize Server Connect Actions (best practices)

As projects grow, the manager becomes your navigation system. A good structure makes actions easier to find, reuse, and secure.

Practical guidelines: Use folders per feature area (for example users/, orders/, admin/). Use consistent action names (for example list, get, create, update, delete). Put shared logic in Library actions and call them from API actions.

We call API actions “endpoints” because they’re reachable by URL, but in Wappler you’ll usually think of them as Server Connect Actions.

Folders = feature boundaries

CRUD naming = predictable URLs

Library actions = reusable building blocks

Screenshot: Organize Server Connect Actions (best practices)Click to open the larger image

Search in the tree

Use search to quickly find a Server Connect Action by name, especially in large projects. This step matters because Search in the tree is part of Manager Serveractions, and understanding that context makes the next action easier to repeat in your own project.

Screenshot: Search in the treeClick to open the larger image

Refresh the tree

Use refresh to reload the list when files change (or after you add / rename actions). This step matters because Refresh the tree is part of Manager Serveractions, and understanding that context makes the next action easier to repeat in your own project.

Screenshot: Refresh the treeClick to open the larger image

Panel help

This help button can start the built-in panel tour (if available for your version/config). This step matters because Panel help is part of Manager Serveractions, and understanding that context makes the next action easier to repeat in your own project.

Screenshot: Panel helpClick to open the larger image

Selected action opens in editor

If a Server Connect Action is selected in the tree, this step opens it in the dedicated editor for focused editing of steps, inputs, and output.

Screenshot: Selected action opens in editorClick to open the larger image

Wrap-up

Review what you did and choose a next tour.

Next steps

Pick a tour to continue.