Server Connect Actions Editor

Introduction

This tour opens a sample Server Connect Action in the dedicated editor so you can explore the editor workspace, view modes, and panels in context.

Focused

Bigger workspace Less UI

Same concepts

Inputs + steps Output

Great for

Large actions Complex logic

Use the manager panel to browse; use the editor to focus.

Everything still runs server-side and returns JSON.

You can always jump back to the Server Connect Actions hub.

Editor workspace

This is the dedicated Server Connect Actions editor. This workspace is optimized for editing a single action: steps on the left/center, properties on the side, and quick toggles in the header toolbars.

Screenshot: Editor workspaceClick to open the larger image

View mode and panels

In the steps header area you can:

• Switch between Tree and Flow view
• Show/hide the Actions panel (when available)
• Show/hide the Properties panel

These controls help you focus when actions get large.

Screenshot: View mode and panelsClick to open the larger image

Properties panel

Select a step in the tree, then use the Properties panel to configure its inputs and options.

Tip: if you don’t see Properties, use the header toggle to show it.

Screenshot: Properties panelClick to open the larger image

Properties panel (compact layout)

On smaller windows or compact layouts, Properties may appear in a different panel.

If you don’t see it on the right, look for it in the secondary panel area.

Screenshot: Properties panel (compact layout)Click to open the larger image

Actions panel (inserting steps)

When the Actions panel is available, it’s your catalog of step types.

Typical workflow:

• Open the Actions panel
• Find a step (Database, HTTP, Files, Auth, …)
• Insert it into your action flow/tree

Screenshot: Actions panel (inserting steps)Click to open the larger image

Inserting steps

There are a few common ways to add steps: via the Actions panel (when available), via the tree context menu (right‑click), or by duplicating an existing step and tweaking it.

Next, continue with the Server Connect Actions hub for a guided path and practical recipes.

Prefer smaller steps that do one job well.

Use output steps deliberately (they shape your JSON response).

Use folders/naming consistently for long-term maintenance.

Next Steps

Next: continue with the deep dives for adding steps, understanding action structure, and working with properties.

Go back to the Server Connect Actions hub for recipes and reference.

Use the Workflows Index to browse other Workflows areas.

Use the Server Connect Actions guided path if you want a linear sequence.