Export and Sharing
Every C4 Diagram in Nodinite can be exported and shared in multiple formats. Because all exports are generated on demand from the current relational data in the database, they are always current — no risk of a stale screenshot diverging from the actual architecture.
Export Formats
| Format | Extension | URL | Best for |
|---|---|---|---|
| PNG image | .png |
/api/repository/architecture/sets/{setId}/diagrams/{id}/export.png |
Word, PowerPoint, Confluence, Teams chats |
| SVG vector | .svg |
/api/repository/architecture/sets/{setId}/diagrams/{id}/export.svg |
Print-quality, scalable embedding |
| Mermaid markup | .md |
/api/repository/architecture/sets/{setId}/diagrams/{id}/export.md |
GitHub, Azure DevOps, Notion, Mermaid Live Editor |
| Draw.io XML | .drawio |
/api/repository/architecture/sets/{setId}/diagrams/{id}/export.drawio |
Import into draw.io / diagrams.net for manual editing or branding |
All export endpoints accept a GET request with no authentication for public sharing, or pass the Nodinite session token for authenticated access, depending on your Nodinite security configuration.
Connector Message Members on Export
If a static diagram shows 2 flows or 3 flows on one visible connector, the export behaviour depends on the target format:
| Format | What designers should expect |
|---|---|
| PNG / SVG | Exports the rendered diagram for presentations, reviews, and embedding. Great for visual communication, but not for round-tripping connector message member metadata |
Mermaid .md |
Expands the visible connector into one relationship line per message member, preserving the individual member labels and protocols |
| Draw.io XML | Exports separate edges for the stored members so the diagram can be refined in draw.io, but Message Type links remain Nodinite-only metadata |
In other words, the canvas may collapse several flows for readability while export keeps them explicit where the target format supports it. Optional Message Type bindings are used inside Nodinite for navigation and traceability; they are not embedded into exported markup or image files.
Sharing a C4 Diagram
Read-Only Viewer URL
The URL /repository/architecture/sets/{setId}/diagrams/{id}/view is a stable, shareable link to the rendered Mermaid diagram. Paste it in:
- Teams or Slack messages
- Jira / ServiceNow tickets
- Email threads
- Architecture review documents
The viewer renders the latest diagram state every time it is opened. No diagram rebuilding or re-exporting required.
Raw Mermaid Source
The URL /repository/architecture/sets/{setId}/diagrams/{id}/mermaid shows the raw Mermaid C4 markup with a copy-to-clipboard button. Use this to:
- Paste into GitHub README files (
```mermaid ```block) - Insert into Confluence using the Mermaid macro
- Add to Azure DevOps wiki pages (native Mermaid support)
- Open in the Mermaid Live Editor for immediate visual editing
IsShared Flag
Each C4 diagram has an IsShared flag:
IsShared value |
Visibility |
|---|---|
false (default) |
Only the creator can see the diagram |
true |
All Repository users with Repository access can view and open the diagram |
The flag is toggled from the diagram's list page or the designer toolbar's share button ().
Embedding in External Tools
GitHub / Azure DevOps / Bitbucket
Paste the Mermaid export directly into any Markdown file:
```mermaid
C4Container
title API-Led Architecture
Person(user, "Web User", "Uses the portal")
Boundary(apis, "Experience APIs") {
Container(api, "Customer API", "ASP.NET Core", "REST API")
}
System_Ext(erp, "ERP", "Back-office system")
Rel(user, api, "Calls", "HTTPS")
Rel(api, erp, "Reads inventory", "REST")
```
GitHub, Azure DevOps wikis, and Bitbucket render Mermaid diagrams natively.
Confluence
Two options for Confluence:
- Mermaid macro — Install the Mermaid Diagrams for Confluence app, then paste the Mermaid source into the macro
- PNG/SVG embed — Use the export endpoint URL as an image source in a Confluence page. Because the URL always returns the current diagram, the Confluence page automatically shows the latest architecture
SharePoint / Teams Tab
Use the PNG or SVG export URL as an image source in:
- SharePoint modern pages (Image web part)
- Teams tabs (embed a web page pointing to the
/viewURL)
Automating Export
Because all export endpoints are standard GET requests, they can be automated:
# Download the latest PNG for use in documentation pipelines
$setId = "your-diagram-set-guid"
$diagramId = "your-diagram-guid"
$token = "your-nodinite-token"
Invoke-WebRequest `
-Uri "https://your-nodinite/api/repository/architecture/sets/$setId/diagrams/$diagramId/export.png" `
-Headers @{ "Authorization" = "Bearer $token" } `
-OutFile "architecture-$(Get-Date -Format 'yyyyMMdd').png"
This approach enables:
- Nightly exports committed to a Git repository alongside the application code
- Automated architecture documentation in CI/CD pipelines
- Version-controlled architecture diagrams without manual screenshot management
Export from the Designer
Within the C4 Designer, the Export dropdown () in the toolbar provides one-click download of the current diagram in PNG, SVG, Mermaid .md, or Draw.io XML format — no need to navigate to the export endpoint separately.