How to use Decision Flowchart Builder
- Add rows under Flow steps. Give every step a unique ID, a label and a start, process, decision or end type.
- Add Connections using those IDs. Label decision branches such as Yes and No when needed; unknown IDs and direct self-connections are refused.
- Choose whether to allow loops across different steps. Turn loops off if you want any cycle rejected.
- Inspect the preview and text outline. Steps keep their entered vertical order; connector numbers refer to the complete connection key below the chart. Advanced raw data edits the same nodes and edges as JSON.
- Download decision-flowchart.svg, decision-flowchart-outline.txt or decision-flowchart-project.json after checking the flow. The diagram records your rules without running them.
Example: Decision Flowchart Builder
Map an incoming order through an In stock? decision. Yes leads to packing and shipping, No to a backorder, and both paths finish at Order complete.
Options
- Node IDs
- IDs connect edges to nodes and must remain distinct. Nodes keep their entered order in a vertical column.
- Branches and loops
- Connector numbers refer to the full connection key. The legend switch removes nearby branch labels; long labels, more than eight nodes or a cycle also move them to the key automatically. A drawn loop does not establish that a process terminates.
Supported inputs and limits
- 1 to 24 nodes and up to 48 edges.
- Node labels allow 80 characters and edge labels 40.
- IDs start with a letter and use letters, digits, underscores or hyphens.
- Advanced JSON refuses unknown properties and references.
- Direct self-connections are refused.
More details
Cycles across distinct nodes require Allow loops.
Large diagrams can be tall because nodes keep their input order in one vertical column.
There is no workflow execution, automatic rule validation or optimal-layout guarantee.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
A clear drawing can still contain an unclear decision
Check that each decision has enough labeled outcomes for the actual task and that every destination is intended. The outline helps inspect connections when the drawing gets dense. The page lays out declared data rather than executing a workflow or deciding what its rules should be.
Questions about Decision Flowchart Builder
Can edges refer to missing nodes?
Unknown node IDs are refused.
Are loops allowed?
Loops across distinct nodes can be drawn when enabled. A direct connection from a node to itself is refused.
Does it execute decisions?
No. It renders your declared flow.