Diagrams in other tools
Every version of a published diagram, or of a diagram shared with a link, has a page and an image that anyone can open without a key (Version links). This page says which link to use where, and how to show a diagram in a page that can’t load images from other sites, such as a Claude artifact.
Which link
{ref}is a published diagram’s ID or a share link’s token. Share on the diagram’s page in the dashboard shows both, and Copy there writes the GitHub, Google Docs, Notion or Confluence, web page and Slack or email links below for the version shown or the latest.https://zindex.ai/d/{ref}@3is version 3, which never changes.https://zindex.ai/d/{ref}follows the latest version.- Add
.pngor.svgfor the image itself.
Pin a version where the words around the picture describe it: an issue, a review, a report, a page an agent publishes. Follow the latest where the place is a living reference, such as a README or a status board. Caching and taking links down says how long each answer may be kept, and what a revoked link leaves behind.
Who can make these links, how public a share link is, and which links stop after 7 days are under Putting a diagram in a doc, issue or README.
In a Claude artifact
An artifact can’t load images from other sites, so <img src="https://zindex.ai/…"> stays blank there. Make the diagram in Zindex all the same, so every version is kept, then show one version in one of two ways. Embed one version’s PNG wherever Claude can run a command; in claude.ai chat, or when the page must follow the latest version, load it live.
Embed one version’s PNG. Where Claude can run a command (Claude Code, the desktop app), download the version’s PNG and write it into the page as a data URI, with a command rather than typed, captioned with the version’s page:
curl -sS https://zindex.ai/d/{ref}@3.png -o diagram.png
printf '<figure><img src="data:image/png;base64,%s" alt="Checkout flow, version 3"><figcaption><a href="https://zindex.ai/d/{ref}@3">Checkout flow, version 3</a></figcaption></figure>' "$(base64 < diagram.png | tr -d '\n')" > figure.html
The copy never goes stale, since the version never changes, and the caption leads readers to every version. Every viewer sees it, public links included. The copy goes wherever the page goes, so for a private diagram, embed it only in a page for people who may see it. An artifact must stay under 16 MiB with its images; a diagram’s PNG is far smaller.
Load the picture live. In claude.ai chat, where Claude can’t run a command, the page calls the Zindex connector when it opens: diagram_render with {ref}@3 as id and preview: true returns the PNG with its width and height (diagram_render). A page that should follow the latest version uses {ref} without @3, and knownRevision to refresh without fetching a picture that hasn’t changed.
Who sees the live picture: viewers signed in to Claude, in the page’s organization, who have the Zindex connector under that name, have signed in to Zindex through it, and allow the page to use it. These see the page without the picture:
- a viewer without the connector, with it under another name, or who hasn’t signed in to Zindex through it;
- a viewer who declines when the page asks;
- anyone who opens a public link signed out, or from outside the organization.
Give each live section a fallback, the version’s page link, https://zindex.ai/d/{ref}@3, which opens anywhere. Anyone who can open the page can read a share link in it, even a viewer who doesn’t see the picture.
After a link is revoked, or the diagram is made private or deleted, the live call and the caption’s page answer NOT_FOUND: the page shows its fallback link, and the person decides whether to publish or share the diagram again. An embedded copy stays in the page.
Slides, PDFs and generated reports
The same as the embedded PNG: one version’s PNG in the file, captioned with the version’s page. The file never updates, and a newer version has its own address.
GitHub issues, pull requests and comments
One version, its image linked to its page:
[](https://zindex.ai/d/{ref}@3)
The discussion is about that picture, so it shouldn’t change under it.
README and wiki
The latest version, linked to its page:
[](https://zindex.ai/d/{ref})
It shows each new version within the cache time (Caching and taking links down).
Notion and Confluence
Paste the image link, https://zindex.ai/d/{ref}@3.png (or .svg), then embed it as an image. The page keeps the link, so a link without @3 shows the latest version when the page is opened again.
Linear and Jira
Paste the version’s page link, https://zindex.ai/d/{ref}@3, and attach the version’s PNG to keep the picture in the issue itself.
Google Docs
Insert, Image, By URL with https://zindex.ai/d/{ref}@3.png, or paste the image. Docs doesn’t take SVG, and keeps a copy of the image when it is inserted, so it never updates: insert the new version when you want it.
Slack and email
The page link, https://zindex.ai/d/{ref}@3. The page shows the image, and the link unfurls with it, so it works where an SVG doesn’t.
A web page
The image, linked to its page:
<a href="https://zindex.ai/d/{ref}@3"><img src="https://zindex.ai/d/{ref}@3.png" alt="Checkout flow, version 3" width="{width}" height="{height}"></a>
Version links says where to read the image’s width and height, so the page can reserve the space before the image arrives.
Updating
Change the diagram in Zindex, never the picture: edit it, then render the new version. A rendered SVG or PNG edited by hand is in no version. Then:
- A pinned place gets the new version’s link or file, or keeps the old one on purpose.
- A place that follows the latest shows the new version by itself, within its cache time.
Name the Zindex version in each version of the page, so the page’s own history says which picture each one showed.