Visual Workflows
Rostyman includes a visual workflow editor for building multi-step API sequences as node-based graphs. Chain requests, add logic, and execute complex flows with visual feedback.
Opening the Workflow Editor
- Click + New Tab and choose Workflow
- The Workflow List shows your saved workflows — click one to edit, or click New Workflow
Canvas
The editor uses a drag-and-drop canvas (powered by React Flow). You can:
- Pan — click and drag the background
- Zoom — scroll wheel or pinch
- Select — click a node; Shift+click for multi-select
- Connect — drag from an output handle to an input handle to create an edge
- Delete — select a node or edge and press
Delete
Node Types
Drag nodes from the palette on the left onto the canvas:
| Node | Purpose |
|---|---|
| HTTP Request | Send an HTTP request. Select a saved request from a collection or configure inline. |
| Delay | Pause execution for a specified duration (ms). |
| Condition | Branch based on an expression. Has true and false output handles. |
| Loop | Repeat a sub-flow N times or over an array. |
| Transform | Manipulate data with a JavaScript expression. Input is data, output is the expression result. |
| Parallel | Execute multiple branches simultaneously and wait for all to complete. |
| Log | Write a message to the execution log. Supports variable interpolation. |
| Script | Run arbitrary JavaScript with access to previous node outputs. |
Config Panel
Click any node to open its configuration panel on the right:
- HTTP Request — method, URL, headers, body, auth, linked collection request
- Condition — expression editor (e.g.,
data.status === 200) - Loop — iteration count or source array expression
- Transform — JavaScript expression with
dataas input - Script — full code editor with
nodescontext object
Connecting Nodes
Edges define execution order and data flow. The output of one node is available as input to the next.
For Condition nodes, connect the true handle to one branch and the false handle to another.
Execution
Click Run to execute the workflow from the start node. The execution engine:
- Resolves the execution order from the graph topology
- Runs nodes sequentially
- Passes output data between connected nodes
- Evaluates conditions to choose branches
- Handles loops by re-executing sub-graphs
Flow Tracer
During execution, the Flow Tracer provides live visual feedback:
- Trace panel — shows timestamped events for each node (start, complete, error)
- Click an event to inspect node details
Persistence
Workflows are saved to the local SQLite database. The workflows table stores:
- Node positions and configurations
- Edge connections
- Canvas viewport (zoom and pan position)
Workflows persist across app restarts. Use Ctrl+S to save changes.
Tips
- Start simple: HTTP Request → Condition → two branches
- Use Transform nodes to extract fields before passing data downstream
- Use the trace panel to debug execution issues