ComfyUI

ComfyUI#

2026-07-09

9 min read

This plugin integrates Prism into ComfyUI.

ComfyUI is a node-based interface for building and running generative AI workflows. It is commonly used to combine models, prompts, image inputs, video tools, upscalers, control networks, and custom processing nodes into reusable graphs.

The Prism-ComfyUI integration connects these node graphs to a structured VFX and animation pipeline. ComfyUI workflows can be saved as Prism scenefile versions, project media can be imported into ComfyUI, generated images and videos can be written directly to Prism media locations, and workflows can be submitted locally or to Comfy Cloud through Prism automation.

This plugin is currently available in Early Access for Prism Pro users. In the future, it will be available to all Prism users.

Setup#

The ComfyUI plugin can be installed from the Prism Hub.

Once the plugin has been installed, the Prism integration needs to be added to the ComfyUI installation. This can be done in the popup after the plugin installation.

Alternatively, the Prism integration can be added in the Prism Settings:

Prism User Settings > DCC apps > ComfyUI > Add.

The integration installs a custom node package into the selected ComfyUI folder:

custom_nodes/prism_pipeline

On Windows, Prism searches for ComfyUI installations in this location:

%USERPROFILE%\ComfyUI-Installs\*\ComfyUI

If your ComfyUI installation is located somewhere else, select the custom ComfyUI root folder when adding the integration.

Accessing Prism in ComfyUI#

After the integration has been installed and ComfyUI has been restarted, Prism is available inside the ComfyUI interface.

The Prism sidebar tab provides access to common Prism actions:

save a new workflow version
open the Prism Project Browser
open the Prism Settings

The ComfyUI menu also contains a Prism entry with access to the Project Browser.

When a Prism Save Media node is created, it includes a Select Entity... button. This button opens the Prism entity selector and fills the node with the selected asset or shot context.

Prism and ComfyUI communicate through a local websocket context on ws://localhost:8765. The browser-side Prism extension reconnects automatically and can launch the Prism Comfy context process when needed.

Workflow Integration#

In Prism, ComfyUI workflows are handled as scenefiles with the .json extension.

Saving a ComfyUI scenefile from Prism sends a save command to the running ComfyUI instance, waits for the workflow to be written in ComfyUI's user workflow folder, and then copies the workflow into the selected Prism scenefile version.

Opening a ComfyUI scenefile copies the selected Prism workflow version into ComfyUI's workflow folder and sends a command to load it in the browser UI.

The integration automatically detects the active ComfyUI root folder from the running ComfyUI custom node. If needed, this can be overridden with the PRISM_COMFYUI_PATH environment variable.

Importing Media and Assets#

Media and products from the Prism Project Browser can be imported into ComfyUI.

Input files are uploaded to ComfyUI input storage and then routed to different node types depending on file type.

Image and media imports use a file extension based routing strategy:

standard image files: load into LoadImage
video files (for example .mp4, .mov, .webm): load into LoadVideo if available
EXR files: prefer ◎ RadianceDigitalCinemaRead, then LoadEXR/LoadExr, then fallback to LoadImage
3D product files: route to product loaders (see below)

For ◎ RadianceDigitalCinemaRead specifically, Prism writes the imported EXR path into the source_path parameter.

File transfer itself is done through ComfyUI's upload endpoint, so imported files appear in the active ComfyUI input storage.

3D products can be imported into ComfyUI when they use one of the following formats:

.gltf
.glb
.fbx
.obj

3D files are uploaded to the 3d input subfolder and then loaded through the first available compatible node in ComfyUI:

Load3D
Load3d
LoadModel

Prism Save Media Node#

The integration adds a custom ComfyUI node named Prism Save Media in the Prism category.

This node saves generated images and videos directly into the Prism project. It requests the correct Prism media path from the connected Prism instance, writes the output file to that path, and also writes a copy to ComfyUI's normal output folder so the result appears in the ComfyUI UI.

The node provides the following inputs:

asset: Asset path for asset-based outputs.
sequence: Sequence name for shot-based outputs.
shot: Shot name for shot-based outputs.
identifier: Media identifier or task name used for the output.
version: Version to write. Use next or leave version handling to Prism when auto-versioning is desired.
images (optional): Image input to save.
video (optional): Video input to save.
video_format (optional): Video container selection.
video_codec (optional): Video codec selection.

At least one media input (images or video) is required.

If multiple image frames are provided, the node writes an image sequence by appending padded frame numbers:

<base>_00001.png, <base>_00002.png, ...

If both images and video are connected, the video output uses an identifier suffix _video to avoid naming collisions with image outputs.

For asset outputs, set asset. For shot outputs, set sequence and shot. The Select Entity... button on the node can fill these fields from the Prism entity selector.

PNG prompt metadata and ComfyUI workflow metadata are preserved when ComfyUI metadata writing is enabled.

On the Prism side, output detection supports both single files and numbered image sequences. Prism detects changed or new files before showing a success dialog.

Execution Graph Automation#

The ComfyUI plugin registers Execution Graph nodes for automated workflow submission.

../../_images/comfyui_execution_graph.png

Submit Workflow (Local)#

Submits a workflow to a local ComfyUI server.

Available settings:

Path: Path to the ComfyUI workflow JSON file.
Inputs: Optional input overrides for nodes in the workflow.
Wait For Completion: Wait until the workflow has finished before continuing.
Output Dir: Optional output folder or output filepath for downloaded results.

The local submission uses the configured local ComfyUI server address. By default this is 127.0.0.1:8188.

Local submission connects to ComfyUI's websocket before queuing the workflow so fast jobs cannot miss completion events.

If Output Dir points to a file path (for example C:/tmp/result.png), Prism treats it as a file target and auto-appends index suffixes for additional outputs.

Submit Workflow (Cloud)#

Submits a workflow to Comfy Cloud.

Available settings:

Path: Path to the ComfyUI workflow JSON file.
Inputs: Optional input overrides for nodes in the workflow.
Wait For Completion: Wait until the cloud job has finished before continuing.
Output Dir: Optional output folder or output filepath for downloaded results.

Cloud submission requires a configured Comfy Cloud API key.

Both Execution Graph nodes return GeneratedFiles containing the downloaded result paths when output downloading is enabled.

For cloud submissions, absolute local file paths in input overrides are uploaded automatically before submission and replaced with cloud input references.

Settings#

The following user settings are available for the ComfyUI plugin:

comfyui > localServerAddress: Local ComfyUI server address used for local workflow submission. The default is 127.0.0.1:8188.
comfyui > cloudApiKey: Comfy Cloud API key used for cloud workflow submission.
comfyui > cloudBaseUrl: Comfy Cloud API base URL. The default is https://cloud.comfy.org.

Environment Variables#

The following environment variable can be used to override the automatic ComfyUI path detection:

PRISM_COMFYUI_PATH: Optional override for the ComfyUI root folder. When this variable is set, Prism uses it for workflow and input path resolution. When it is not set, Prism uses the root folder reported by the running ComfyUI custom node.

On Windows, Prism also uses %USERPROFILE% as part of its default path conventions. This is the standard Windows user profile variable and does not need to be set manually in most environments.

%USERPROFILE% is used for default ComfyUI install discovery and for the optional shared input folder:

%USERPROFILE%\ComfyUI-Shared\input

PRISM_SHOW_DEFAULT_SCENEFILE_PRESETS: Optional toggle for loading default ComfyUI scene presets from the plugin Presets folder. Default is 1 (enabled).