OpenKatana · Create project:
The OpenKatana_create_project node lets you request the creation of a local OpenKatana project from a ComfyUI workflow. A project provides the workspace that OpenKatana’s video-production tools use to organize project state and subsequent work, helping you keep separate films or creative experiments organized. The node calls OpenKatana’s local tool interface rather than a paid or cloud service, making it suitable for preparing a project before running other OpenKatana tools. It is a project-management step, not an image-generation or video-rendering operation. Unlike the separate OpenKatanaWorkspace node, this node is not shown automatically opening Studio or installing agent setup resources.
OpenKatana · Create project Input Parameters:
project_id
A required STRING identifying the project within the configured OpenKatana workspace. The inherited default is my-film. OpenKatana’s project-path validation requires an identifier between 1 and 80 characters long, beginning with a letter or digit and containing only letters, digits, hyphens, or underscores afterward. For example, film-test_01 is valid, while spaces, slashes, and punctuation such as periods are not permitted. This identifier determines which project location the request addresses; it is not an arbitrary folder path. Use a distinct identifier for each separate production or experiment. The resolved project location must remain inside the configured workspace.
arguments
A required STRING containing the tool’s arguments in JSON form. The inherited default is {}, and the field supports multiple lines so you can read and edit longer argument objects more easily. The node processes this text together with the project identifier before invoking the create-project tool. Use a JSON object with double-quoted property names and string values where appropriate; the supplied context does not show the create-project tool’s argument schema, so additional property names, required properties, and their defaults cannot be confirmed here. No minimum or maximum string length is specified. Keeping the default empty object avoids adding unsupported properties, but does not establish that the underlying tool has no additional requirements.
after
An optional STRING connection intended to establish execution order between nodes. It uses forceInput=True, meaning it is supplied through a connection rather than a normal text-entry widget. You can connect an upstream STRING result when this operation needs to wait for another node to finish. The supplied implementation accepts this value but does not read its contents or pass them into the tool request, so it does not change the project identifier or creation settings. No default value, length limit, or list of options is specified. A connection establishes a dependency; it does not itself check whether the preceding operation succeeded.
OpenKatana · Create project Output Parameters:
result_json
A STRING containing the response produced by the OpenKatana tool bridge, intended to represent the result as JSON text. Use it to inspect the tool’s reply and determine what happened before continuing with project-dependent work. It is a text response, not an image, video, or direct project object. The provided source does not include the response formatter or the create-project return schema, so specific fields, success indicators, file paths, or error structures cannot be guaranteed. Check the actual response rather than assuming that receiving a string means creation succeeded. You can also connect this output to another OpenKatana node’s after input to establish execution order.
OpenKatana · Create project Usage Tips:
- Choose a short, recognizable
project_idsuch asmusic-video_01. Avoid spaces and folder paths; the identifier is resolved under OpenKatana’s configured workspace. - Start with
argumentsset to{}unless the installed tool’s documentation or description specifies additional creation arguments. Do not assume that the separate Workspace node’s settings are also accepted by this tool. - Inspect
result_jsonafter your first execution. Confirm the actual response before building a longer workflow that imports media or edits the project. - To make another OpenKatana operation wait for project creation, connect this node’s
result_jsonto that operation’safterinput. Remember that this controls order, not success validation. - Treat repeated execution cautiously. The inherited implementation marks the node as changed on every run because project state is shared with Studio, CLI, and MCP; the supplied code does not establish whether creating an already-existing project reopens it or produces an error.
- Use the separate OpenKatanaWorkspace node when you specifically need its documented create/reopen-and-Studio workflow. Automatic Studio setup is not demonstrated for this node.
OpenKatana · Create project Common Errors and Solutions:
Project ID must use letters, digits, hyphens or underscores
- Explanation: OpenKatana rejects identifiers that do not match its naming rules. An empty identifier, spaces, path separators, more than 80 characters, or a leading hyphen or underscore can trigger this validation error.
- Solution: Use 1–80 characters, start with a letter or digit, and use only letters, digits, hyphens, and underscores. For example, replace
My Filmwithmy-film.
Project must stay inside the configured workspace
- Explanation: The resolved project location points outside the workspace OpenKatana is allowed to use. This is a safety check; even a valid-looking identifier can fail if an existing filesystem link redirects its location elsewhere.
- Solution: Supply a project identifier rather than a path. If the identifier is valid but the error persists, check the workspace location and any existing linked project folder.
Invalid JSON in arguments — exact message may vary
- Explanation: The arguments field is expected to follow the tool’s JSON contract. Missing quotation marks, trailing commas, or incomplete brackets can prevent the request from being processed; the supplied code does not show the exact parsing error text.
- Solution: Reset the field to
{}to remove formatting mistakes, then add only documented properties. Use double quotes rather than single quotes for JSON property names and text values.
Unsupported or missing tool arguments — exact message may vary
- Explanation: Syntactically valid JSON can still fail if its contents do not match the create-project tool’s requirements. The provided context does not include those requirements or the corresponding error messages.
- Solution: Check the installed node’s description and tool signature for the supported argument contract. Remove guessed properties and supply any explicitly required ones.
Project creation fails on an existing location — exact message may vary
- Explanation: A previous run or another application may already have created the target location. The supplied code does not show how this particular tool handles existing projects or non-project folders, so reopening or overwriting must not be assumed.
- Solution: Inspect the reported response and the existing location before retrying. For a genuinely new project, choose an unused identifier; do not delete existing files simply to bypass the failure.
Filesystem permission or storage error — exact message may vary
- Explanation: Local project creation can fail if OpenKatana cannot write to its workspace or the storage device has insufficient space. The precise exception text depends on the operating system and creation implementation.
- Solution: Confirm that the workspace is writable by the process running OpenKatana, check available disk space, and retry after correcting the underlying filesystem issue.
