convert

/comfy-convert — Convert Workflow Format

The user wants to convert a ComfyUI workflow between the web UI format and the API format.

Instructions

1. Read the workflow file. The argument is: $ARGUMENTS

   • If a file path is provided, read it with the Read tool
   • If no argument is provided, ask the user for a file path or to paste the JSON

2. Detect the format. Examine the JSON structure:

   • UI format: has top-level "nodes" array and "links" array (this is what "Save" in the web UI produces)
   • API format: has string keys (node IDs like "1", "2") where each value has "class_type" and "inputs" (this is what "Save (API Format)" produces)

   Tell the user which format was detected and which format it will be converted to.

3. If converting UI format to API format:

   a. Iterate over each node in the "nodes" array. Each node has:

   • id (integer): becomes the string key in API format
   • type: becomes class_type
   • widgets_values: ordered list of widget values
   • inputs: array of input slots with name, type, and optional link
   • outputs: array of output slots

   b. For each node, call create_workflow (action:"node_info") with the node's type to get the input schema. This tells you:

   • The order and names of widget inputs (to map widgets_values correctly)
   • Which inputs are required vs optional
   • Expected types for each input

   c. Build the API node's inputs object:

   • Map widgets_values to named inputs using the order from create_workflow (action:"node_info")
   • For linked inputs (where link is not null), find the connection in the "links" array. Each link is [link_id, source_node_id, source_slot, target_node_id, target_slot, type]. Set the input value to ["{source_node_id}", source_slot]

   d. Assemble the API workflow: { "{node_id}": { "class_type": type, "inputs": {...} }, ... }

4. If converting API format to UI format: