The Workflow Graph View is a read-only rendering of a saved workflow. It’s useful for sharing a visual snapshot, embedding workflow diagrams in documentation, and giving stakeholders a look without handing them the editor.
Opening the View
The graph view lives at /graph/:workflowId. You can link directly to it from the workflow’s Share menu, or paste the URL into a Markdown file — Jekyll will render the image when the page is exported statically.
Unlike the Workflow Editor, the graph view:
- Does not load the Node Menu, Inspector, or the panel drawers.
- Does not allow editing — nodes can’t be added, moved, or deleted.
- Does not require authentication on localhost deployments.
This makes it lightweight (~5× smaller bundle) and safe to expose behind a read-only proxy.
Interactions
The graph view is fully static — it’s a snapshot, not an interactive canvas. Nodes can’t be dragged, connected, or selected; panning, scroll-zoom, pinch-zoom, and double-click-zoom are all disabled.
The view auto-fits the whole graph to the viewport once when it loads, so the entire workflow is visible without any interaction. Running the workflow is not possible from this view — open it in the editor first.
To pass a workflow inline (without a stored ID), supply base64-encoded workflow JSON via the ?data= query parameter. Optional ?bg= and ?padding= parameters control the background color and fit padding.
Embedding in Docs
You can embed the graph view inside another page with an iframe:
<iframe
src="https://your-nodetool-host/graph/WORKFLOW_ID"
width="100%"
height="540"
loading="lazy"
referrerpolicy="no-referrer">
</iframe>
For stored Markdown docs, take a screenshot instead so the graph is captured even when the server is offline.
Access Control
The graph view inherits the workflow’s own visibility:
- Private — requires the user to be signed in with access to the workflow.
- Shared — accessible to anyone with the link.
- Public — indexed and crawlable.
For localhost deployments, all workflows are effectively local and the view is open to anyone who can reach your server.
Next Steps
- Workflow Editor — the full editor where you author workflows
- Chain Editor — the linear alternative
- Authentication — how access is enforced