Files
AdiosF6F e4e27808fa docs: document pipe architecture, new examples, and counter padding
Update project documentation to reflect the newly introduced Pipe
architecture and improve overall clarity regarding workflow orchestration.

- `README.md`: Add a new "Optional: Pipe Integration" section explaining
  when to use the pipe system, emphasizing its role in managing complex,
  multi-stage workflows with deferred execution. Clarify the distinction
  and compatibility boundaries between standard and pipe nodes.
- `README.md`: Document the `%counter<padding>` filename template variable.
- `CLAUDE.md`: Update the core architecture map to include `nodes_pipe.py`
  and list the new configuration, modification, and terminal nodes.
- `examples/`: Introduce a dedicated examples directory. Move the standard
  `example-workflow.json` into this folder and add the new
  `image_saver_pipe_workflow.json` to demonstrate advanced orchestration.
- `examples/README.md`: Add a descriptive index detailing the differences
  between the standard workflow and the advanced pipe orchestration example.
2026-05-21 21:54:11 +02:00

1.6 KiB

Examples

This directory contains example workflows to help you get started with the ComfyUI-Image-Saver nodes.

example-workflow.json

This is the standard example workflow and the recommended starting point for most users.

It demonstrates a basic setup using the Image Saver Metadata and Image Saver Simple nodes. In this example:

  • The image is saved in JPEG format with A1111-compatible metadata.
  • It shows how to use filename placeholders like %time and %seed.
  • It illustrates how resource hashes (like embeddings in the prompt) are automatically handled by the metadata engine.
  • It includes helper nodes like Input Parameters and String Literal for better workflow organization.

image_saver_pipe_workflow.json

This is an optional advanced workflow demonstrating how to use the Pipe system for orchestration.

It is designed for complex scenarios where managing multiple generation branches would otherwise result in a cluttered "noodle" of wires. By bundling metadata and saver settings into a single IMAGESAVER_PIPE connection, you can:

  • Reduce wire clutter in large-scale workflows.
  • Create base configurations early and selectively override them in different branches using the Edit Image Saver Pipe node.
  • Deferred execution of expensive metadata operations until the final save node.

This approach is particularly useful when working in tandem with other piping systems, such as the Basic Pipe from the ComfyUI-Impact-Pack.