BPMN Diagrams

Choose BPMN when creating a diagram in your workspace. Add events, tasks and gateways from the palette, then drag between their handles to connect the process. Select a shape to edit its label and supported properties in the inspector.

Build a readable process

1. Add a start event and an end event.
2. Place tasks in the order work happens. Name each task with an action, such as “Review order”.
3. Add a gateway where the process splits or joins. Label outgoing paths so readers can distinguish their conditions.
4. Use swimlanes to show responsibility. Rename and reorder lanes, then assign shapes to the appropriate lane.
5. Save and review the diagram with a teammate. Inspector properties document the process; they do not execute services or scripts.

DiagramKit provides BPMN shapes for tasks, events and gateways, including message and timer events. The notation reference is OMG BPMN 2.0.2.

Save and share

Editors and owners can change a diagram; viewers can inspect it. Save operations use the current revision. If another edit wins first, review the newer state before saving again so another person's work is preserved.

Use DiagramKit JSON for an editable backup that includes the diagram's mode, content and lane metadata. For a saved diagram, the authenticated API endpoint GET /api/flows/{id}/render?format=svg provides a visual export; png and pdf are also available. These exports use the stored diagram, so save first. See exporting and MCP integration.

This editor is a manual modeling surface. Process execution, simulation and BPMN XML import/export are outside its current scope.