OpenKatana · Build workflow:
OpenKatana_build_workflow gives you access to OpenKatana’s workflow-building tool from inside ComfyUI, helping you assemble connected processing steps without manually wiring every node. The supplied workflow-building code includes support for tasks such as image generation, Qwen-based generation and reference editing, matting, segmentation, and frame interpolation. Its builders create graphs—organized collections of nodes and connections—using task-specific templates and check supported settings, model requirements, and certain image-size constraints. Tests also confirm that several builders use local nodes rather than automatic-download nodes, making locally supplied model components important to their operation. This node is a tool interface for requesting workflow construction; it should not be confused with running the constructed workflow or producing finished artwork.
OpenKatana · Build workflow Input Parameters:
project_id
A required STRING that supplies the project identifier used when preparing the tool request. The node passes this value to the argument-preparation helper together with the selected tool and your argument text, so you should provide the identifier for the project you intend to work with. The supplied source does not show how project identifiers are created, whether they are checked against stored projects, or how conflicts with identifiers inside the argument text are handled. No default value, character restrictions, minimum or maximum length, or list of options is specified in the provided interface.
arguments
A required STRING containing the arguments for the workflow-building tool. This is where you supply the tool-level configuration rather than adding separate ComfyUI input sockets for individual workflow settings. The node processes this text through its argument-preparation helpers before invoking the tool. The underlying builders shown in the context accept a workflow kind and settings appropriate to that kind, and reject unsupported settings rather than silently ignoring them. However, the supplied node source does not expose the complete argument schema, parsing rules, or required outer structure, so use the documented argument format for the installed build_workflow tool rather than assuming a particular JSON layout. No default text, minimum or maximum length, or fixed options are specified for this STRING input.
after
An optional STRING accepted by the node’s execution method, with a Python default of None when omitted. In the supplied implementation, this value is not referenced when preparing arguments or invoking the tool. Consequently, the visible code does not establish that it controls execution order, identifies a previous operation, or changes the generated workflow. Leave it unconnected unless your surrounding OpenKatana integration documents a specific purpose for it; do not rely on it alone to enforce a dependency between operations. No string default, minimum or maximum length, or supported options are specified.
OpenKatana · Build workflow Output Parameters:
result_json
A STRING containing the response returned through OpenKatana’s response-formatting helper after the tool is invoked. This is the node’s only output, so it is the place to inspect the tool’s reported result rather than expecting an image, latent, or separate workflow socket. The underlying workflow builders produce graph data describing node types, settings, and connections, but the supplied wrapper does not show the exact response envelope or guarantee which fields this tool returns. The context also includes a separate readiness-check result with fields such as ready and errors; those should not be assumed to appear in every build response. Treat this output as a serialized tool response, inspect its actual contents before passing it onward, and do not interpret successful workflow construction as confirmation that the workflow has already executed.
OpenKatana · Build workflow Usage Tips:
- Choose the workflow kind first, then supply only settings supported by that builder. Generation, reference editing, matting, segmentation, and interpolation do not necessarily accept the same configuration.
- For Qwen generation, supply all three model components:
model,encoder, andvae. The tests show that supplying a model alone is insufficient. Use component names that correspond to files available in your installation. - Respect the Qwen generation geometry requirements. The supplied test explicitly rejects a width of 513 and expects an error mentioning multiples; the excerpt does not establish the exact required multiple, so check the installed builder’s schema before choosing dimensions.
- For
qwen-edit, the shown builder acceptsreferencesfrom 1 to 16, with a default of 1. It creates image-loading nodes using names such asreference-1.pngandreference-2.png, so make those images available under the expected names before executing the resulting workflow. - For
qwen-edit, useresolutionvalues of 0 or multiples of 32 within the inclusive range 0–2048; the default is 1024. The excerpt does not explain what 0 means, so do not assume it disables resizing or automatically selects a size. - For
qwen-edit,stepsdefaults to 25 and accepts 1–100, whileseeddefaults to 1 and accepts 0 through 18446744073709551615. Keep the seed fixed when comparing changes under otherwise identical execution conditions. These are settings inside the tool arguments, not additional inputs on this node. - Validate a constructed workflow against your target ComfyUI installation before running it. The supplied validation code checks graph compatibility against available capabilities; building a graph alone does not establish that every required node and asset is available.
- Inspect
result_jsonbefore connecting it to another tool. Confirm what the response actually contains rather than assuming the entire string is a directly executable ComfyUI graph.
OpenKatana · Build workflow Common Errors and Solutions:
Unsupported workflow parameters: Unsupported `{kind}` parameters: {sorted(extra)}
- Explanation: A model-specific builder found settings that are not allowed for the selected workflow kind. The actual message substitutes the workflow name and a sorted list of unsupported settings.
- Solution: Remove or correct the named settings and check that your argument configuration matches the chosen workflow kind. Do not reuse every setting from a different workflow without checking compatibility.
Unknown builder parameter, such as definitely_not_a_param
- Explanation: The supplied tests confirm that the base builder raises a
ValueErrorfor an unknown setting and includes that setting’s name in the error. The full message is not shown. - Solution: Check spelling and remove settings not supported by the selected builder. Put only documented tool settings inside
arguments; arbitrary extra settings are not automatically accepted.
resolution must be 0 or a multiple of 32
- Explanation: The
qwen-editbuilder received a resolution that fails its divisibility check. For example, 1000 is not a multiple of 32. - Solution: Use 0 or a valid multiple of 32 within 0–2048, such as 512, 1024, or 1536. The shown default is 1024.
Missing Qwen component: error mentioning encoder
- Explanation: The tests show that
qwen-generationfails when onlymodelis supplied and expects an error mentioning the encoder. They also identify all three components as required, although the full error messages are not provided. - Solution: Supply valid
model,encoder, andvaesettings together. Verify that each refers to the intended locally available component.
Invalid Qwen geometry: error mentioning multiples
- Explanation: The tests show that a Qwen generation width of 513 is rejected because it does not meet the builder’s geometry requirements. The exact message and required multiple are not included in the excerpt.
- Solution: Consult the installed builder’s size requirements and choose dimensions that satisfy them. Do not assume every positive width or height is valid.
Out-of-range Qwen editing settings
- Explanation: The shown
qwen-editbuilder applies numeric bounds to references, resolution, steps, and seed. Values outside those bounds can fail argument validation; the numeric helper’s exact error wording is not supplied. - Solution: Use an integer reference count of 1–16, resolution of 0–2048 with the required multiple-of-32 constraint, steps of 1–100, and seed of 0–18446744073709551615.
unexpected inputs: ...
- Explanation: The node wrapper explicitly raises a
TypeErrorwhen it receives extra named execution fields that are not declared in its typed interface. This is different from an unsupported setting inside the workflow-building arguments. - Solution: Use only the exposed inputs:
project_id,arguments, and optionalafter. Place documented workflow settings in the tool’s argument payload instead of adding new node inputs.
Workflow readiness check reports ready: false
- Explanation: The supplied validation code returns
readyas false when it finds graph or compatibility errors and includes details in anerrorslist. This is a validation result, not a guaranteed response field from the build node. - Solution: If you run this validation step, read each listed error and correct the reported configuration or compatibility issue before execution. Check that required local nodes and assets are available, then validate again.
