Flowcharts in Confluence

A flowchart shows the steps and decisions of a process, from the first step to every possible end.

Last updated

When to use it

Use a flowchart for a procedure people must follow: an approval, a runbook, a deployment pipeline, an onboarding path. Boxes are steps, diamonds are decisions and arrows give the order. If the question is “who talks to whom, and when”, a sequence diagram fits better.

Example

This is the code of the Simple process template: a request that is reviewed, approved or declined, then done.

flowchart LR
  Start([Request received]) --> Review[Review request]
  Review --> Approved{Approved?}
  Approved -- Yes --> Do[Do the work]
  Approved -- No --> Inform[Inform the requester]
  Do --> Done([Done])
  Inform --> Done

Vellnar Diagrams draws it like this:

Change a line and the diagram changes with it. Nobody needs the original drawing file, because there is none: the code is the diagram.

Add it to a Confluence page

  1. Edit a Confluence page and type /mermaid where the diagram should go.
  2. Select Mermaid diagram. The editor opens with the template list.
  3. Pick a template, or choose Start blank and paste the code above. The preview follows every keystroke.
  4. Choose Save. The diagram appears on the page.

The documentation covers the editor, the settings and the exports.

Templates

The Templates button in the editor has 4 flowcharts ready to use:

  • Simple process: A request that is reviewed, approved or declined, then done.
  • Decision tree: Yes or no questions that lead to the right action.
  • Deployment pipeline: Build, test, staging and production with a manual gate.
  • User onboarding: From sign-up to an active user, with an optional team invite.

Syntax

The code of a flowchart starts with flowchart. The Mermaid documentation describes every element of the syntax. Vellnar Diagrams draws it with Mermaid 12.3; if a line has an error, the editor marks the line and keeps the last valid diagram on screen.

More

  • Mermaid in Confluence: how diagrams as code work in a page, and every diagram type.
  • Security: the app asks for no permissions and sends nothing outside Atlassian.