Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > OpenKatana > OpenKatana · Bind reference

ComfyUI Node: OpenKatana · Bind reference

Class Name

OpenKatana_bind_reference

Category
OpenKatana/Tools
Author
rk0neki (Account age: 235days)
Extension
OpenKatana
Latest Updated
2026-11-05
Github Stars
0.05K

How to Install OpenKatana

Install this extension via the ComfyUI Manager by searching for OpenKatana
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter OpenKatana in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

OpenKatana · Bind reference Description

Registers images or videos as named project references with file hashes for visual review.

OpenKatana · Bind reference:

OpenKatana_bind_reference registers imported images or videos as a named reference within an OpenKatana project, helping you organize visual guidance for a person, character, style, product, or location. It records the reference together with file hashes—digital fingerprints of the source assets—so the project can track which material was registered. References are saved in the project’s reference registry and can support later visual review of generated material. In strict review mode, generated clips imported from a Comfy job must be accepted against every bound identity reference before a timeline using them can render. Binding a reference does not generate images, apply a style, train a model, or automatically verify a likeness; it establishes a persistent reference record for your project’s workflow.

OpenKatana · Bind reference Input Parameters:

project_id

A required STRING identifying the OpenKatana project in which you want to register the reference. The underlying operation uses this project to look up imported assets and save the reference record, so the assets you reference must belong to this project. Choose the project where you intend to organize and review your generated material; an asset identifier from another project will not resolve in this project’s asset list. The supplied node interface does not specify a default value, length limit, or list of allowed project identifiers.

arguments

A required STRING carrying the arguments for the reference-binding operation as a JSON object. The underlying API requires a reference name and a list of imported asset identifiers, and also accepts a role, subject type, and description. For example, you can provide {"name":"hero_reference","asset_ids":["asset_001"],"role":"identity","subject_type":"person","description":"Approved appearance for the main character."}, replacing the example asset identifier with one actually imported into your project. The name must be a string containing 1–64 characters, and the asset list must contain at least one imported image or video; each listed asset must exist in the project and contain the media information expected by the API. Supported roles are identity, style, product, and location, with identity as the underlying API default. The underlying defaults for subject type and description are person and an empty string, respectively; the description may contain at most 500 characters. No allowed-value list for subject type is shown. These are settings inside the JSON text, not separate node sockets. The node interface itself does not specify a default value or length limit for the complete arguments string.

after

An optional STRING with a default of None in the node’s execution method. The provided implementation accepts this value but does not pass it to the argument-building or tool-invocation calls shown, so no effect on reference selection, storage, or returned data is demonstrated. No permitted values, length limits, or additional behavior are specified in the supplied source. You can leave it unconnected for reference binding; do not rely on its text to select a reference or configure the binding operation.

OpenKatana · Bind reference Output Parameters:

result_json

A STRING containing the tool response serialized as JSON. The underlying binding operation returns a reference record containing name, role, subject_type, description, assets, digest, and at. Each entry in assets contains the imported asset’s id and its sha256 file hash. The digest is a SHA-256 fingerprint calculated from the reference name, role, and asset entries, while at records the binding time as an ISO-formatted UTC timestamp. These values let you identify the registered reference and the source assets associated with it; they are not similarity scores or evidence that an identity review has passed. The node passes the operation’s return value through a response helper whose implementation is not provided, so the exact outer JSON structure cannot be established from the supplied code.

OpenKatana · Bind reference Usage Tips:

  • Import your reference images or videos into the target project first, then use their actual asset identifiers in arguments. File paths alone do not satisfy the asset lookup performed by this operation.
  • Set the role explicitly when organizing different kinds of visual guidance: use identity for identity references, style for style references, product for product references, and location for location references. Binding these records does not automatically condition a generation model.
  • Choose a clear name such as hero_identity or packaging_reference. The registry is keyed by name, so binding another reference with the same name replaces that reference record rather than creating a second entry.
  • Include multiple imported assets in the same asset list when you want them registered together under one named reference, for example several approved views of a character. Every listed identifier must resolve to an eligible imported asset.
  • Keep descriptions concise and within 500 characters. Use this text to explain what the reference represents, but do not treat it as a generation prompt or an automated acceptance rule.
  • Plan identity references carefully when using strict review mode. Generated material must subsequently be accepted through inspect_identity against every bound identity reference before a timeline using that material can render; binding alone does not complete this review.
  • Check the returned record after binding, especially its name, role, and asset identifiers. A returned digest identifies the registered reference data, but its calculation does not include the description or subject type, so it should not be treated as a fingerprint of every metadata field.

OpenKatana · Bind reference Common Errors and Solutions:

name: 1..64 characters

  • Explanation: The reference name is missing a valid string value, is empty, or contains more than 64 characters.
  • Solution: Supply a nonempty name of no more than 64 characters inside arguments, such as "name":"hero_identity".

role: one of identity, style, product, location

  • Explanation: The supplied role is not one of the four supported values. An arbitrary label such as enemy cannot be used as a role.
  • Solution: Use exactly identity, style, product, or location. Put more specific creative labels in the name or description instead.

asset_ids: at least one imported image or video

  • Explanation: The asset list is empty, so there is no source material to register as a reference.
  • Solution: Import at least one reference image or video into the project and include its identifier in the asset list, for example "asset_ids":["asset_001"].

asset_ids: imported images or videos (...)

  • Explanation: One or more listed identifiers either do not exist in the selected project or lack the media information required by the API. The actual message includes the rejected identifiers in parentheses.
  • Solution: Check that project_id identifies the correct project, then replace the rejected values with identifiers of images or videos imported into that project. Do not substitute a file path or reference name for an asset identifier.

description: up to 500 characters

  • Explanation: The description exceeds the API’s 500-character limit.
  • Solution: Shorten the description to 500 characters or fewer, or omit it to use the empty-string default.

Invalid JSON or missing required arguments

  • Explanation: The argument-processing stage may fail if arguments is not valid JSON or does not supply the required reference name and asset list. The supplied code does not establish the exact error message for these failures.
  • Solution: Use a JSON object with double-quoted property names and strings, and provide the required values. Start with {"name":"hero_reference","asset_ids":["asset_001"]}, substitute a real imported asset identifier, and avoid trailing commas.

unexpected inputs: ...

  • Explanation: The node’s execution method rejects additional fields that are not declared in its typed input configuration. Reference settings such as name and role are not separate inputs in the supplied node interface.
  • Solution: Use only the exposed sockets: project_id, arguments, and optionally after. Place the reference-binding settings inside the JSON text supplied to arguments.

OpenKatana · Bind reference Related Nodes

Go back to the extension to check out more related nodes.
OpenKatana
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.

OpenKatana · Bind reference