OpenKatana · Collect workflow:
OpenKatana_collect_workflow makes the OpenKatana collect_workflow tool available inside a ComfyUI workflow, allowing you to request workflow collection through the same node-based environment you use for your creative work. The node acts as a bridge: it prepares a project-scoped request, calls the OpenKatana tool, and formats the tool’s response for use in ComfyUI. This is useful for integrating an OpenKatana operation into a larger sequence without writing a separate API call yourself. The supplied source shows this request-and-response mechanism, but does not include the underlying collect_workflow implementation, so it does not establish exactly what is collected, where it is stored, or whether collection changes project files. Treat this node as an interface to the collection tool rather than as an image generator, renderer, or confirmed workflow-submission operation.
OpenKatana · Collect workflow Input Parameters:
project_id
A required STRING that supplies the project identifier used when preparing the OpenKatana tool request. It establishes the project context for the operation, so you should provide the identifier of the project you intend to work with rather than assuming a project’s display name or folder path will be accepted. The node passes this value to its argument-preparation helper before invoking the tool; the supplied code does not show how project identifiers are validated or what happens when a project cannot be found. No default value, minimum or maximum length, or list of accepted identifiers is shown in the provided interface.
arguments
A required STRING containing the arguments to be prepared for the collect_workflow call. The node combines this text with the project context through an argument-preparation helper and then passes the prepared arguments to OpenKatana. This is where the collection request’s tool-specific details must be supplied, but the provided source does not include the accepted argument structure, required keys, or parsing rules. Use the argument format documented for your installed OpenKatana collect_workflow tool; if that format is JSON, provide valid JSON with the documented field names and value types. Do not assume that settings shown for other operations, such as workflow submission endpoints or execution modes, are accepted here. No default value, length limits, or predefined options are shown in the supplied interface.
after
An optional STRING accepted by the node’s execution method, with a Python default of None when omitted. The method does not read this value, merge it into the tool arguments, or forward it to the OpenKatana invocation. Connecting an upstream STRING output to this input can establish a ComfyUI dependency, making the upstream node part of the execution path before this node runs. However, the connected text does not itself configure collection or verify that the previous operation succeeded. No string default, minimum or maximum length, or predefined options are shown in the supplied interface.
OpenKatana · Collect workflow Output Parameters:
result_json
A STRING containing the OpenKatana tool response after it has been processed by the shared response-formatting helper. This is the node’s only output and is the place to inspect the reported result of the collection request. Although the output name indicates JSON-formatted text, the supplied source does not include the formatter or the collect_workflow response schema, so particular keys, file paths, success flags, or collected artifacts cannot be guaranteed from this context. If the response is JSON, a downstream consumer must interpret its documented fields rather than treating the string as an image, video, or already-loaded ComfyUI workflow. The surrounding context includes readiness and validation information for other workflow helpers, but does not establish that those fields appear in this node’s response.
OpenKatana · Collect workflow Usage Tips:
- Confirm the argument schema for
collect_workflowin your installed OpenKatana version before configuringarguments. The provided node interface exposes a general text field rather than individual collection settings. - Use the intended OpenKatana project identifier for
project_id. Keeping project identifiers clearly associated with your creative projects helps avoid sending a correctly formed request to the wrong project context. - If the tool expects JSON arguments, validate the JSON before running the node. Check quotation marks, commas, field names, and value types; JSON validity alone does not guarantee that the tool accepts the requested settings.
- Connect an earlier node’s STRING output to
afterwhen you need an execution dependency. Do not place collection settings or success conditions in this field, because the shown execution method does not inspect its contents. - Inspect
result_jsonwith a text display or an appropriate JSON-processing node before building downstream automation. Confirm the actual response structure instead of assuming that it contains a workflow filename or a success field. - Keep workflow collection separate from workflow submission in your configuration. The supplied context shows a distinct
submit_workflowAPI, so its endpoint, execution, and payment-related settings should not be copied into this node unless the collection tool’s own documentation explicitly supports them.
OpenKatana · Collect workflow Common Errors and Solutions:
unexpected inputs: ...
- Explanation: This is an explicit error pattern in the node source. The execution method raises a
TypeErrorwhen it receives additional fields that are not recognized by its typed input definitions. The message lists the unexpected field names. - Solution: Use only the exposed inputs:
project_id,arguments, and optionalafter. If you are constructing a ComfyUI API request, remove extra top-level node inputs. Put tool-specific settings insideargumentsonly when the collection tool’s documented schema permits them.
Missing required input: project_id or arguments
- Explanation: This is a descriptive troubleshooting label rather than a quoted error from the supplied source. Both fields are required by the node interface, so omitting either can prevent ComfyUI from executing the node. An empty string may also be rejected later, depending on argument preparation or tool validation.
- Solution: Supply both required fields. Use a valid project identifier and the documented argument representation, including the documented representation of an empty argument set if the tool supports one.
Invalid or unsupported arguments
- Explanation: This is a possible failure category, not an exact message established by the supplied source. Argument preparation or the OpenKatana tool may reject incorrectly formatted text, unsupported fields, missing required details, or values of the wrong type. The helper implementations are not included, so their precise error messages are unknown.
- Solution: Compare
argumentswith the schema for your installedcollect_workflowtool. If JSON is required, first fix syntax errors, then check the accepted keys and value types. Remove settings copied from unrelated tools unless they are explicitly supported.
OpenKatana tool invocation fails
- Explanation: This is a possible failure category rather than a literal error string from the supplied code. The node delegates execution to OpenKatana, so a valid ComfyUI input configuration does not guarantee that the collection tool is available or that the request will succeed. The provided source does not show the invocation layer’s error handling.
- Solution: Inspect the available response and ComfyUI logs for the actual failure message. Confirm that your OpenKatana installation exposes
collect_workflowand that the requested project is available. Follow any specific validation or configuration guidance reported by the tool.
A connected after value does not stop collection after an earlier failure
- Explanation: The execution method accepts
afterbut does not examine its contents. Consequently, an upstream node returning an error message as ordinary text does not make this node treat that text as a failure condition. - Solution: Use
afterfor execution dependency only. If collection must depend on an earlier operation’s success, validate that operation’s response and use an appropriate conditional workflow mechanism before allowing collection to proceed.
result_json does not contain the expected fields
- Explanation: The provided source does not define the collection response schema. Expecting fields from another OpenKatana operation, or treating the returned text as a directly usable workflow object, can cause downstream processing errors even when the tool call itself completed.
- Solution: Inspect the actual output and consult the collection tool’s response documentation. Configure downstream parsing around confirmed fields, and handle reported failures separately from successful collection results.
