Command line

export

workflow-render export workflow.json -o workflow.svg
workflow-render export workflow.json -o workflow.png --scale 3

• The output format follows the file extension: .svg or .png.
• --scale N sets the PNG size multiplier. The default is 2. It is an error with an .svg output.
• The SVG is self-contained. Icons are inlined and fonts are embedded, so it looks the same in a browser, an <img> tag or a file preview.
• The same input always produces the same SVG, byte for byte.

Export every workflow in CI

for f in workflows/*.json; do
  npx workflow-render export "$f" -o "renders/$(basename "${f%.json}").png"
done

view

workflow-render view workflow.json
workflow-render view execution.json --port 4777

Expected output:

workflow-render viewing execution.json
  http://127.0.0.1:4777/
Press Ctrl+C to stop.

• The viewer binds to 127.0.0.1 only.
• Without --port, it picks a free port.

Executions

Give view or export an execution instead of a workflow and the canvas shows the run.

• Executed nodes take the status colour.
• Edge labels carry the item counts.
• Double-click a node to open the inspector: input, parameters and output, with Schema, Table and JSON views.
• A failed node shows its error and stack.
• Binary data is named, never fetched.

Exit codes and warnings

Warnings go to stderr, prefixed warning:. The file is still written.

workflow-render export dangling.json -o dangling.svg

Expected output:

wrote dangling.svg
warning: connection to unknown node "Ghost" dropped

Getting the JSON out of n8n