How to make a diagram from a process description with AI

• The steps, in order. Number them. A paragraph works, but numbered steps leave the AI less to guess.
• The decisions. Each point where the process splits, with its question and its answers (“Is the item under 30 days old? Yes: refund. No: reject.”).
• The people or systems. Who does each step, if more than one person or system is involved.
• The kind of diagram. On the AI Diagrams page you choose the kind and the language it’s drawn in. In a chat, or in the editor’s AI panel with Let the AI choose, the AI picks for you.

Each diagram the AI draws or changes is charged in credits at the chosen model’s price per message. A failed or empty answer costs nothing. Free accounts get 15 credits every day on the models marked free. A diagram that still doesn’t draw after the AI’s tries isn’t saved or charged.

The picker has many more kinds, grouped by subject, from UML and database design to project management. Picking the right one matters: the AI checks that the result is the kind you asked for, not just a drawing.

1. 1

   Step 1: Write the process down

   Number the steps, mark each decision with its question and answers, and say where the process starts and ends.

2. 2

   Step 2: Choose the kind and the language

   On the AI Diagrams page, choose a kind, such as Flowchart, and one of the languages that can draw it: PlantUML, Mermaid or Graphviz. Only languages that can draw the kind are offered. In a chat, ask instead: “Draw a flowchart of our refund process.”

3. 3

   Step 3: Paste the description and generate

   Paste your steps into the box, choose the AI model, and press Generate diagram. The editor opens and draws it.

4. 4

   Step 4: Let it check itself

   The AI writes the diagram as code. It is kept only when it draws without errors and is the kind you asked for; if not, the AI is told what’s wrong and tries again. If it still fails, you can open its last code and fix it by hand.

5. 5

   Step 5: Read it against your steps

   Switch between Diagram, Code and Both. Follow each path from start to end and check that every step and every decision outcome is there.

6. 6

   Step 6: Fix it by asking

   In the AI panel, choose Change this one and describe the change: “Add a step where a manager approves refunds over $100.” The old version is kept.

7. 7

   Step 7: Or edit the code yourself

   Small fixes, such as a label’s wording, are quicker by hand. The preview redraws as you type, and a line with an error is marked.

8. 8

   Step 8: Go back if you need to

   The version history keeps every AI result and the version before it, so any earlier diagram can be brought back.

9. 9

   Step 9: Download or share it

   You can download it as an SVG picture (sharp at any size), a high-resolution PNG, a PDF, or its code. In a shared project, the people you invite can open it too.

• Give the order and the branches: “Flowchart, top to bottom. 1. Customer asks for a refund. 2. Is the item under 30 days old? Yes: go to 3. No: reject and email the customer. 3. Refund to the original card.”
• Say who does what: “Show which steps the customer, the shop and the bank do.”
• Control the shape: “Left to right instead of top to bottom” or “Label every decision Yes and No.”
• Keep labels short: “No more than five words in any box.”
• Change one thing at a time: “Merge steps 4 and 5” is easier to check than a whole new description.

• Vague decisions. “Sometimes we escalate” gives the AI nothing to draw. Say when: “If the customer has asked twice.”
• Too much in one diagram. If it needs scrolling, split it: one diagram for the main path, one for each exception.
• The wrong kind. Messages between systems read better as a sequence diagram than as a flowchart.
• Not checking each path. A diagram can draw perfectly and still miss a step. Trace every branch to its end.