Eric's Workflow Toolkit_v2
Eric's Workflow Toolkit v2
- image
- result
- workflow_data
- structured_analysis
- image
You've been there: you generate something great, close the graph, and the workflow JSON is gone. The image survives - because ComfyUI's PNGs carry the workflow embedded in their metadata. Eric's Workflow Toolkit v2 is the node that digs it back out, and it's the pack's workflow-recovery utility dressed as a graph node. In extract mode it reads the embedded workflow from a file and hands you back usable data; in analyze mode it turns that data into a structured breakdown; in visualize mode it can even render the workflow as an image. Consider it the "I forgot to save" insurance policy.
The required inputs are input_filepath (the PNG in question - wire it from a loader's full_path output or paste it) and operation_mode, with the three options above. The optional section is where you tune the output: visualization_type (graph, text, or json) decides how the visualize mode presents the graph, detailed_output adds depth, output_directory defaults to workflow_output for anything written to disk, and there are toggles for whether the results get written as an XMP sidecar, embedded into the image, dumped to a text file, or logged to the database. overwrite_existing controls whether it clobbers files with the same name, and debug_logging is on by default, which means you'll see what it's doing in the console.
The four outputs tell you what it can produce: result (STRING - the human summary), workflow_data (DICT - the raw workflow structure), structured_analysis (DICT - the analyzed breakdown), and image (IMAGE - the visualization render in graph mode). If your goal is just "get my workflow back," wire workflow_data to a save/export node or read it from the result string and paste it into ComfyUI's workflow loader.
The honest caveat: this node is a Swiss-army utility written by one author, not a polished standalone product, and the pack has no community footprint to lean on - which means if something behaves oddly, you're reading the source or the console logs. It also assumes the metadata was written by this pack's save nodes (or another writer that follows ComfyUI's embedded-workflow convention). A PNG saved by a completely different tool may not have a workflow in it at all, and then extract returns nothing useful - check with the pack's Metadata Debugger if you're unsure.
This whole pack is niche, but workflow recovery is one of the few problems where a dedicated node beats the manual alternative (opening a hex editor or a third-party metadata tool). Install the pack and restart:
cd ComfyUI/custom_nodes
git clone https://github.com/EricRollei/AAA_Metadata_System
cd AAA_Metadata_System
pip install -r requirements.txt
Find it under Eric's Nodes → Workflow, set operation_mode to extract, and point it at the PNG you thought you lost. The workflow you never saved is usually still in there.
Inputs (13)
| Name | Type | Default | Description |
|---|---|---|---|
| input_filepath | STRING | — | |
| operation_mode | COMBO | extract | 3 options: extract, analyze, visualize |
| imageopt | IMAGE | — | |
| visualization_typeopt | COMBO | graph | 3 options: graph, text, json |
| detailed_outputopt | BOOLEAN | true | — |
| extract_from_tensoropt | BOOLEAN | true | — |
| output_directoryopt | STRING | workflow_output | — |
| write_to_xmpopt | BOOLEAN | true | — |
| embed_metadataopt | BOOLEAN | false | — |
| write_text_fileopt | BOOLEAN | false | — |
| write_to_databaseopt | BOOLEAN | false | — |
| overwrite_existingopt | BOOLEAN | false | — |
| debug_loggingopt | BOOLEAN | true | — |
Outputs (4)
| Name | Type | Description |
|---|---|---|
| result | STRING | — |
| workflow_data | DICT | — |
| structured_analysis | DICT | — |
| image | IMAGE | — |