First Server Connect Action
First Server Connect action: add steps, test the API response, and use it in a page or component.
First Server Connect Action (mental model)
Server Connect Actions are server-side workflows that return JSON. They’re your safe boundary to the database and private services.
IMPORTANT: If it must be secure, validate input, or touch the database: do it in Server Connect Actions (not in the browser).
API group
Server Connect Actions live under the API group. Click Next to select it automatically.
Add + name API Action
Next will add a new API Action under API. This step matters because Add + name API Action is part of Manager Serverconnectmanager Tree, and understanding that context makes the next action easier to repeat in your own project.
Name the new API Action
Next will rename the new action to a friendly starter name. This step matters because Name the new API Action is part of Manager Serverconnectmanager Tree, and understanding that context makes the next action easier to repeat in your own project.
The new action opens in the editor
The manager hands off to the dedicated Server Connect editor so the new action can be configured there.
The Server Connect editor is ready
The new action is now open in the dedicated editor, so the next steps can focus on its inputs and workflow steps.
Orient yourself in Server Connect editor
Start with the wider context in the Server Connect editor so the next control makes sense in the full workflow. In the next step, you will focus on Define Input Variables and see how it fits into this area.
Define Input Variables
Define inputs under Globals (GET/POST/Route/Session). These become available as dynamic data when configuring steps.
Add Steps
Add steps (DB Query, Insert/Update/Delete, Mailer, File Upload, etc.). Steps run top-to-bottom, so keep validation near the top.
Global Settings
Global Settings is where you configure shared items like database connections and security providers for the project.
Next steps
Run the action and inspect the JSON output. If something fails, work top-to-bottom: inputs → step config → step output.