Documentation · Process
Flowchart
Declare every box once, then wire them with arrows. Spacing and routing are worked out for you.
When to use it
Explain a procedure, decision path or algorithm with a small set of steps and branches.
Give decision branches explicit labels such as Yes and No. IDs identify boxes; quoted labels are what readers see.
Working example
Copy this complete example into the Source tab, then press Generate. Change its labels or values to make your first version.
flow "Chart Title" {
start S1 "Start Process"
io I1 "Read Input Data"
process P1 "Execute Algorithm"
decision D1 "Is Valid?"
end E1 "Finish"
S1 -> I1 -> P1 -> D1
D1 [Yes] -> E1
D1 [No] -> P1
}Syntax reference
The same reference used by the editor and AI briefing. Syntax is notation-specific; use the keywords listed here.
Diagram
| Syntax | Meaning |
|---|---|
flow "Title" { | open a flowchart; close it with } |
Nodes
| Syntax | Meaning |
|---|---|
start ID "Label" | terminator (ellipse) |
process ID "Label" | process step; alias: task |
decision ID "Label" | branch point (diamond) |
io ID "Label" | input / output; alias: data |
end ID "Label" | terminator (ellipse) |
Edges
| Syntax | Meaning |
|---|---|
A -> B | directed edge |
A [Yes] -> B | edge with a caption |
A -> B -> C | chain |
# comment | line comment (also //) |
Language rules
- The file is one flow "Title" { ... } block. Nothing may sit outside it.
- An element is <keyword> <ID> "Label", one per line. The ID is short, unique, and never quoted.
- Every ID used in an arrow must be declared above it.
- A decision usually has two outgoing arrows, each with its own caption: D1 [Yes] -> E1.
Edit on the canvas
- Move boxes and rename captions directly on the canvas. Linked arrows follow their endpoints.
- Choose a flow or annotation connector from the rail. Branch captions belong on the connector.
Generate replaces the drawing from source. Save before generating again if you want to preserve manual finishing touches.
Read Saving & exportingWrite it with an assistant
Tingraph AI already knows this notation. For another assistant, copy the tutorial below, describe your diagram under MY DIAGRAM, then paste the returned source into the editor. This prompt includes every syntax row, rule and working example above.
Read the complete prompt
You are writing Tingraph source. Tingraph is a small text language that draws a flowchart. Answer with Tingraph source only.
SYNTAX
Diagram
flow "Title" { open a flowchart; close it with }
Nodes
start ID "Label" terminator (ellipse)
process ID "Label" process step; alias: task
decision ID "Label" branch point (diamond)
io ID "Label" input / output; alias: data
end ID "Label" terminator (ellipse)
Edges
A -> B directed edge
A [Yes] -> B edge with a caption
A -> B -> C chain
# comment line comment (also //)
RULES
- The file is one `flow "Title" { ... }` block. Nothing may sit outside it.
- An element is `<keyword> <ID> "Label"`, one per line. The ID is short, unique, and never quoted.
- Every ID used in an arrow must be declared above it.
- A decision usually has two outgoing arrows, each with its own caption: `D1 [Yes] -> E1`.
WORKED EXAMPLE
flow "Chart Title" {
start S1 "Start Process"
io I1 "Read Input Data"
process P1 "Execute Algorithm"
decision D1 "Is Valid?"
end E1 "Finish"
S1 -> I1 -> P1 -> D1
D1 [Yes] -> E1
D1 [No] -> P1
}
OUTPUT
- Reply with one fenced code block and nothing else.
- The block starts with `flow "…" {` and ends with `}`.
- Do not invent keywords: use only the ones listed above.
- Keep labels short enough to read inside a box, and keep every ID unique.
MY DIAGRAM
Describe what you want here, then send this message.Something unclear? Contact support or read the Privacy Policy.