From an idea to a connected flow
Place nodes from the library and draw connections between them. Make the sequence of work visible before discussing implementation.
- Flow canvas
- Node library
Pyrodit Stack / Visual flow design
Pyrodit Studio
Draw the workflow before you run it. Connect nodes, shape conditions and data mappings, and share a flow your whole team can inspect.
What you can do
- 01
Build flows on a visual canvas.
- 02
Inspect node settings, conditions and data mappings.
- 03
Import, export and preview flow definitions.
A practical example
Design a supplier-comparison flow together.
Built for · Process owners and automation teams
Procurement and engineering need to agree on the data, comparisons and decision points before the workflow is connected to real systems.
How the work moves
Draw the request, comparison and decision steps as connected nodes.
Define which fields each step receives and which condition selects the next path.
Review the local simulation, then export the definition for runtime integration work.
What this gives your team
A shared, inspectable flow design before production execution is connected.
Illustrative workflow. Connections and deployment scope are agreed for your environment.
Inside the product
Pyrodit Studio
Make each step explicit
Use the inspector to edit node configuration, edge conditions and field mappings. Review JSON configuration alongside the visual design.
- Node & edge inspector
- Condition panels
- Field mapping
Share a design your team can review
Export a versioned JSON flow definition and import it back into the editor. Use the simulation and its log to discuss the planned path before runtime integration.
- JSON import / export
- Simulation preview
Scope & availability
The visual editor includes a local simulation preview. Runtime publishing and execution integration are evaluated separately for your deployment.