Sovereign Platform is in pre-launch alpha.
Not yet available to purchase. Sign up for our mailing list for upcoming launch dates.
Sovereign Platform is in pre-launch alpha.
Not yet available to purchase. Sign up for our mailing list for upcoming launch dates.
The Studio is where you build, test, and refine your workflows. It is a visual editor — you work by dragging, connecting, and configuring rather than writing code.
When you open the Studio (by creating a new workflow or editing an existing one), you see three main areas:
The canvas is the large central workspace. This is where your workflow takes shape. Nodes appear as cards on the canvas, and connections between them appear as arrows showing the flow of execution.
You can zoom in and out, pan around, and rearrange nodes by dragging them. The canvas automatically adjusts to accommodate workflows of any size.
The Node Palette is on the left side. It lists every action available to you, organized by connector. Expand a connector to see its actions, then drag any action onto the canvas to add it to your workflow.
The palette includes:
Search for Actions
If you know what you are looking for, use the search bar at the top of the Node Palette to filter actions by name or connector. This is faster than scrolling through the full list.
When you select a node on the canvas, the Properties Panel opens on the right side. This is where you configure what that step does — its parameters, expressions, and behavior.
The Properties Panel shows:
Connections define the execution order of your workflow. To create a connection:
An arrow appears showing the direction of flow. By default, connections fire on success — the target node runs when the source node succeeds.
You can also create failure connections that only fire when a step fails. This lets you build error-handling paths alongside your main flow.
Each action has its own set of configuration fields. When you select a node and open the Properties Panel, you will see the fields for that action.
Many fields support expressions — template syntax that lets you reference data from previous steps. For example, you might configure a step to use the output of a previous step as its input. See Expressions and Data Flow for details.
The Studio includes a Run Panel for testing:
This feedback loop lets you iterate quickly — make a change, run it, see the result, and adjust.
When your workflow is ready for production use, you can Publish it. Publishing creates a versioned snapshot of your workflow definition. This is the version that runs when triggered by schedules or webhooks.
You can continue editing the draft version without affecting the published version. When you are ready to deploy your changes, publish again to create a new version.
Before publishing, the Studio validates your workflow to catch common issues:
Validation errors appear with clear descriptions of what needs to be fixed.