> For the complete documentation index, see [llms.txt](https://glyue.docs.sandboxbanking.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glyue.docs.sandboxbanking.com/how-to-guides/how-to-export-an-integration-diagram.md).

# How to Export an Integration Diagram

The toolbar above the [Integration Gateway Workbench](/integration-gateway-platform-reference/integration-gateway-workbench.md) canvas lets you export the current integration diagram as an image or as structured data. The toolbar displays the integration name and appears only after you load an integration on the canvas.

## Export Formats

| Action          | Output                                        | Use Case                                    |
| --------------- | --------------------------------------------- | ------------------------------------------- |
| **Export SVG**  | Vector image (`.svg`)                         | Presentations, Confluence, Figma, Inkscape  |
| **Export PNG**  | Raster image at 2× resolution (`.png`)        | Documents, slide decks                      |
| **Export JSON** | Integration data as structured JSON (`.json`) | Auditing, version control, external tooling |

All exports capture the full integration graph, not just the visible viewport.

## Export a Diagram

1. Open an integration in the Workbench to display the canvas and toolbar.
2. In the toolbar, click **Export SVG**, **Export PNG**, or **Export JSON**.
3. While the export runs, the button shows an **Exporting...** state and stays disabled. When the export completes, the file downloads automatically.

The system names exported files using the integration name:

* `integration-{name}.svg`
* `integration-{name}.png`
* `integration-{name}.json`

## Export JSON

The **Export JSON** option downloads the integration's data as a structured JSON file. Use it to capture a point-in-time copy of the integration for auditing, version control, or processing in external tooling.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://glyue.docs.sandboxbanking.com/how-to-guides/how-to-export-an-integration-diagram.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.