Overview

Confluence Cloud’s copy-page API is rough on third-party apps. Macros that store state outside the page body — diagram tools, exporters, formatting macros that link by page ID — typically come out the other side broken or stale. Most workflow and publishing apps hand pages to Atlassian’s API as-is and inherit those problems. Aura Workflows adds explicit handling for the apps where it matters most.

draw.io

Aura supports draw.io’s Diagram macro. Pages that contain Diagram macros can be published, republished, and reverted, and the rendered diagram on the published page stays in sync with the source diagram.

The other two draw.io macros — draw.io Boards and Embed draw.io — are not currently supported. Pages using those will still publish, but the macros may render stale or broken content on the target. Stick to the Diagram macro on pages that go through a workflow.

Aura is the only Confluence Cloud workflow app that handles draw.io publishing correctly. With every other publishing solution, draw.io macros silently drift after a few publishes — the rendered diagram on the published page goes stale or breaks entirely, even when the source diagram is fine. Aura keeps the macro and the diagram in sync through every publish, so what you see on the source is what readers get on the published page.

Caveat: reverting the source page

If you revert the source page (the working/draft copy) to an earlier version through Confluence’s version history, the draw.io macro on that restored version still points at the attachment version that was current when the older version was first saved. New attachment versions added since then sit ahead of the pointer, so the macro can render the wrong (or no) diagram until the pointer catches up. This caveat is about the source page only — published pages are not affected.

The fix is mechanical: on the source page, open the diagram in draw.io and save it once. That creates a fresh attachment version and fast-forwards the macro’s pointer. After the save the macro is consistent again and you can publish normally.

Caveat: space-level diagram overview

draw.io maintains a “diagrams in this space” overview page in every space where it’s enabled. Diagrams on published pages do not appear in the target space’s overview. They render correctly inside the published page itself — only the directory listing is incomplete.

K15T’s Scroll Apps

The Metadata macro works inside content exported through K15T’s Scroll Word Exporter and Scroll PDF Exporter. The publish-time snapshot stored on each Metadata macro travels with the page body, so the exported document shows the correct values for whichever page version you export.

Note

This is implicit support, not an integration we maintain jointly with K15T. It works because Scroll’s exporters consume Atlassian’s ADF Export API, and that’s the same surface our snapshot writes into. If K15T ever changes their export pipeline to read from a different representation, this could regress until we add explicit handling. If you spot a discrepancy in an exported document, please report it.

Aura Content Formatting Macros

All macros from the Aura Content Formatting Macros suite — Cards, Buttons, Panels, and the rest — publish cleanly. The macros render the same way on the published page as on the source, including any styling, layout, and child content.

The non-obvious property: when a Cards or Buttons macro on a page links to another page in the same space, that link remains stable across the publish. On other macro suites the link reference becomes a dead pointer back at the source page after publishing. Aura’s content formatting macros resolve through Aura Workflows’ link-rewriting layer during publish, so a Card on the published page links to the published version of the next page in the workflow, not back to the source draft.

This is the only Confluence Cloud macro suite where in-space cross-page links stay correct end-to-end through a workflow publish.