OpenKatana · Import workflow output:
OpenKatana_import_workflow_output provides a ComfyUI interface to OpenKatana’s import_workflow_output tool, allowing you to request a workflow-output import as part of a node-based process. Its role is to connect your ComfyUI workflow to the corresponding OpenKatana operation: it prepares the tool arguments, sends the request, and returns the tool’s response as text. This makes the operation available alongside other OpenKatana tools without requiring you to write the calling code yourself. The supplied source shows the calling interface rather than the underlying import implementation, so it does not establish which output formats can be imported, how imported material is stored, or whether the operation copies files or registers references to them.
OpenKatana · Import workflow output Input Parameters:
project_id
A required STRING that supplies the project identifier to the tool-argument preparation step. It provides project context for the request, so you should use the identifier associated with the OpenKatana project you intend to work with. The supplied code does not show how project identifiers are validated, whether the project must already exist, or how this value interacts with any project information included in the argument text. No default value, permitted identifier format, length limits, or list of options is provided in the authoritative interface.
arguments
A required STRING containing the argument text used to prepare the import_workflow_output request. This is where the tool-specific request details are supplied; the node processes this text together with the project identifier before invoking the tool. The supplied source does not include the argument parser or the import tool’s argument schema, so it does not establish the required keys, accepted values, or exact text format. Use the argument structure documented for the installed OpenKatana import_workflow_output tool rather than inventing fields from other workflow examples. No default value, minimum or maximum length, or predefined options is shown.
after
An optional STRING accepted by the node’s execution method, with a Python default of None when omitted. Although the interface exposes this parameter, the visible execution body does not read it or explicitly include it in the tool request. Its effect on execution order or dependency handling therefore cannot be confirmed from the supplied code. Leave it unconnected unless your installed OpenKatana documentation explains its intended use; do not assume it selects a workflow output or guarantees that another operation has finished. No string default, length limits, or options is shown in the interface.
OpenKatana · Import workflow output Output Parameters:
result_json
A STRING containing the response produced by the OpenKatana tool call after it passes through the shared response formatter. This is the node’s only exposed output and is the place to inspect the outcome of the import request. Despite its name, the supplied code does not show the response formatter’s implementation or guarantee a particular JSON structure, field set, or success indicator. Treat it as a textual tool response and inspect its actual contents before extracting values or connecting it to a JSON-processing node. It is not exposed as a ComfyUI IMAGE, VIDEO, or other media output, so it should not be connected directly to nodes that require those data types.
OpenKatana · Import workflow output Usage Tips:
- Obtain the argument schema for import_workflow_output from your installed OpenKatana tool documentation before configuring
arguments. The supplied workflow-building examples do not define this import operation’s accepted fields. - Use the intended OpenKatana project identifier consistently. If you work with several projects, verify
project_idbefore execution to avoid submitting the request with the wrong project context. - Start with the smallest valid request supported by the tool, then inspect
result_jsonbefore adding optional tool arguments. This makes it easier to isolate an unsupported field or an incorrectly formatted value. - Connect
result_jsonto a text-display or inspection node first. Only configure downstream JSON extraction after you have confirmed the response’s actual structure. - Leave
afterunset unless its behavior is documented in your installation. The visible implementation does not establish it as a reliable way to wait for workflow completion. - Keep the node’s three exposed inputs separate from tool-specific argument fields. Additional request details belong in the documented argument structure, not in newly invented node inputs.
OpenKatana · Import workflow output Common Errors and Solutions:
unexpected inputs: ...
- Explanation: This error is explicitly raised by the node when extra execution fields are not included in its permitted typed inputs. The message lists the unexpected field names. It can occur when calling the node programmatically or using a workflow definition that does not match the installed interface.
- Solution: Use only
project_id,arguments, and the optionalafteras exposed node inputs. Put tool-specific details insideargumentsaccording to the import tool’s documented schema, and check that your workflow matches the installed node version.
Missing required input: project_id or arguments
- Explanation: Both inputs are required by the interface. Omitting either can prevent ComfyUI from executing the node; a direct Python call may instead report a missing required positional argument. The exact validation message depends on how the node is called.
- Solution: Supply both required STRING inputs. Use the intended project identifier and valid argument text; do not assume that an empty string will be accepted by the underlying tool.
Argument preparation or validation failure
- Explanation: The node prepares and processes the argument text before calling OpenKatana. An unsupported argument structure or invalid value may fail during that preparation or be rejected by the tool. The supplied code does not show the validation rules or exact error messages.
- Solution: Compare your argument text with the schema for the installed import_workflow_output tool. Correct the reported field or value, and avoid borrowing argument names from unrelated workflow-generation tools.
Tool invocation failure
- Explanation: The import request is delegated to the shared OpenKatana invocation layer. Failures in that layer or in the import operation may prevent a successful response, but the supplied source does not identify specific service errors or their wording.
- Solution: Inspect the returned response, if present, and the ComfyUI logs for the underlying message. Verify the project context, the tool’s availability, and any output reference required by its documented argument schema before retrying.
Downstream node rejects result_json
- Explanation:
result_jsonis a STRING, not directly usable image or video data. A downstream node expecting media or a different data type can reject the connection or fail when processing the value. - Solution: Inspect the response as text first. If it contains a documented reference to imported material, use the appropriate supported loading or retrieval step to obtain the data type required by your next node.
