Diagrams · BPMN macro
The process everyone argues about, current and on one page
With the BPMN macro your process diagram stops being a screenshot in a slide deck, six months out of date and impossible to correct. The real model file renders on the Confluence page - lanes, gateways, subprocesses and all - so the diagram people discuss is the one your modeller produced, as it is today.
Readers drill into a subprocess instead of hunting for it
A real process does not fit on one canvas, so collapsed subprocesses become doors: a reader clicks one and the page opens the diagram inside it, at any depth, with breadcrumbs to walk back out. Everyone follows the level of detail they need rather than being handed all of it at once - and you configure nothing, because it works from the file as it is.
The handover that usually goes wrong is the part people can point at
Collaboration diagrams keep their pools and lanes, so who does what stays visible on the page rather than in someone's memory. The handover between finance, legal and delivery - the step where a process usually breaks - becomes something a reader can point at and question.
Your team keeps its modelling tool and stops redrawing for the wiki
Standard BPMN XML from Camunda Modeler, bpmn.io or anything else that speaks the notation renders as-is, so nobody redraws a process in a wiki editor to publish it. The Camunda properties your automation engine cares about can be shown beside the diagram or kept out of the picture, depending on who is reading.
You publish the model itself, not last quarter's export
Point the macro at the file where it already lives - a page attachment, a URL,
Google Drive, or a credentialed S3, SFTP or database connection an admin set up once
- and your page shows the current model every time it is opened. Let it size itself
to the diagram or fix the height, and readers download the .bpmn file
to open in their own tool.
What the other BPMN apps make you migrate
Most of Confluence's BPMN apps are modellers: you draw the process in their editor,
and the model then lives in Confluence, in their format, versioned by them. That
costs you a migration and a second home for something your process team already
maintains in Camunda Modeler. This macro asks for none of it - it renders the
.bpmn file exactly where it already sits, including an S3 bucket, an
SFTP server, Google Drive or a database connection none of those apps can reach, and
hands the file back unchanged when a reader wants to open it.
BPMN is one of 31 macros in Macro Pack
One app to install, one licence to renew, one place your team learns - and 30 more formats it already reads, from spreadsheets and diagrams to API specs and documents.
See every macro in the pack