Worked example: from a paragraph to a flowchart
Here is a refund policy written the way procedures usually are, as one paragraph:
When a customer asks for a refund, support checks the order. If the order is older than 30 days, support explains the policy and offers store credit. Otherwise support checks whether the item was returned; if not, email a return label and wait for the parcel. The warehouse inspects the item. Damaged items go to a manager; everything else is refunded to the original payment method and the customer gets a confirmation email.
Converted to a flowchart, the same text becomes thirteen shapes: one start, six steps, three decisions and three ends.
This page draws the example with its own renderer. Generating it in flow-chart.io gives you an editable version; its layout and wording can differ, so review the draft.
Look at the "Damaged?" branch. The paragraph says damaged items go to a manager but never says what happens next, so the diagram has to stop there. Finding gaps like this is the most useful thing about turning text into a flowchart: a paragraph can skip a step without anyone noticing, a diagram can't.
How sentences become flowchart symbols
| In the text | On the flowchart | From the example |
|---|---|---|
| A trigger ("When…", "Once…") | Start oval | Customer asks for a refund |
| A sentence with a verb and an object | Process rectangle | Support checks the order |
| "If…", "whether…" | Decision diamond with two labeled exits | Older than 30 days? |
| "Otherwise", "if not", "everything else" | The other exit of that diamond | No → item returned? |
| "Wait for…", "until…", "again" | A step, or an arrow looping back | Wait for the parcel |
| Something sent or received | Input/output parallelogram | Send confirmation email |
| Role names (support, warehouse, manager) | Owner labels, or swimlanes | Warehouse inspects the item |
The flowchart symbols guide covers every shape in more detail.
How to convert text to a flowchart in flow-chart.io
- Paste or type the description. Use the box below or the box on the homepage. The free preview needs no sign-up and drafts up to 8 main steps; the full editor handles longer processes and every branch.
- Check the decisions. Every diamond should have two labeled exits, and every path should reach an end. Missing branches usually mean the text skipped something.
- Refine in words or by hand. Click any shape to rename or move it, or describe the change, for example "add manager approval for refunds over $200".
- Save, share or export. A free account saves one diagram and shares it as a read-only link. Pro adds downloads, including Mermaid source if your docs render Mermaid.
Write text that converts cleanly
- One action per sentence. "Support checks the order and refunds it" hides a decision.
- Name who does each step. Role names become owners or swimlanes.
- Write decisions as yes/no questions and say where both answers go.
- Say when work loops back ("ask again", "until it passes").
- Stay at one level of detail. Move a detailed sub-process into its own diagram.
Plain language or diagram code?
Code-based tools such as Mermaid and PlantUML also turn text into diagrams, but the text is a syntax (A --> B) rather than a description. That works well when the diagram lives next to code in a repository and developers maintain it. Plain-language conversion suits policies, SOPs and anyone who does not want to learn a syntax.
You do not have to choose one forever: flow-chart.io Pro exports Mermaid, and the Mermaid source for this page's example is below.
Mermaid source for this diagram
flowchart TD
s(["Customer asks for a refund"])
chk["Support checks the order"]
d1{"Older than 30 days?"}
credit(["Explain policy, offer store credit"])
d2{"Item returned?"}
lbl["Email a return label"]
wait["Wait for the parcel"]
insp["Warehouse inspects the item"]
d3{"Damaged?"}
mgr(["Manager reviews (outcome not stated)"])
ref["Refund the original payment method"]
conf[/"Send confirmation email"/]
e(["Refund complete"])
s --> chk
chk --> d1
d1 -->|Yes| credit
d1 -->|No| d2
d2 -->|No| lbl
lbl --> wait
wait --> insp
d2 -->|Yes| insp
insp --> d3
d3 -->|Yes| mgr
d3 -->|No| ref
ref --> conf
conf --> ePaste into any Markdown tool that renders Mermaid, such as GitHub.
Frequently asked questions
- Can AI turn text into a flowchart?
- Yes. A text-to-flowchart tool reads the description, picks out triggers, steps, decisions and loops, and lays them out as connected shapes. The result is a draft: check that every decision has both outcomes and that nothing in the text was skipped.
- Is text to flowchart free?
- You can generate a preview free without signing up. A free account gives 4 AI credits a month (one standard diagram), saves 1 diagram and shares it as a read-only link. Downloads and unlimited diagrams are part of Pro at $9/month; see the pricing page for details.
- Can I convert a whole document or SOP?
- Paste the part of the document that describes one process. Long documents usually describe several processes, and one diagram per process is easier to read and review.
- Can it make a swimlane diagram from text?
- Yes. Name who does each step in the text and ask for lanes by role. See the swimlane diagram maker guide for examples.
- Can I get Mermaid code from my text?
- Pro exports any diagram as Mermaid (.mmd), as well as SVG, PNG, PDF, PowerPoint and JSON.
Related
Last reviewed 9 November 2026.