Integrations & Migration
Supported Integrations
LaTeX Formulas & Diagrams integrates natively with Confluence Cloud and leverages two open-source rendering libraries. This article describes what the app integrates with and - importantly - what it does not access.
Native Confluence Integration
The app is built as a native Confluence Cloud macro. This means:
Macros Stored in Confluence Page Content
- Your Mermaid code and LaTeX source are stored directly in the Confluence page content (Confluence storage format)
- There is no separate database or external storage - the macro body is part of the page
- This means your content travels with the page: copy a page and the macro content copies with it
Fully Versioned with Page History
| Feature | Detail |
|---|---|
| Page version history | Every time you publish a page, Confluence saves a new version - including your macro source |
| Restore previous versions | You can restore any previous version of a page via Confluence's built-in page history, which also restores the macro source from that version |
| Version comparison | Confluence's page diff view shows changes to macro source between versions |
Accessible via Confluence API
Because macro content is stored in the Confluence page storage format, it is accessible via the standard Confluence REST API:
- GET /wiki/rest/api/content/{id}?expand=body.storage returns the full page content including macro bodies
- Macro source (Mermaid code or LaTeX) appears inside the
<ac:plain-text-body>element of the macro markup - This allows programmatic extraction, migration, or backup of macro content using standard Confluence API tooling
Mermaid Rendering
The Diagrams macro renders visual diagrams using Mermaid, a JavaScript-based diagramming library.
Supported Diagram Types
| Diagram Type | Mermaid Header | Use Case |
|---|---|---|
| Flowchart | flowchart TD / graph TD | Process flows, decision trees |
| Sequence | sequenceDiagram | API flows, system interactions |
| Class | classDiagram | Object-oriented design |
| Entity Relationship | erDiagram | Database schemas |
| Gantt | gantt | Project timelines |
| Pie Chart | pie | Proportional data |
| Mindmap | mindmap | Topic hierarchies |
| State Machine | stateDiagram-v2 | State transitions |
| Timeline | timeline | Chronological events |
| Block Diagram | block-beta | System architecture blocks |
What Data the App Does NOT Access
It is important to understand the scope of data access:
| Data Source | Accessed? | Notes |
|---|---|---|
| Jira issues or projects | No | The app has no Jira integration and does not read or write Jira data |
| External APIs or services | No | All rendering runs entirely client-side in the browser |
| Other Confluence spaces | No | The app only processes content on the page being viewed or edited |
| User data beyond page authorship | No | The app does not read user profiles, email addresses, or account data |
| Confluence analytics or audit logs | No | The app does not access Confluence analytics or site-level logs |
| External storage or databases | No | Macro content is stored in Confluence page storage only |
All rendering is performed locally in the user's browser. No macro content, user data, or page content is transmitted to external servers.