Overview
The ComfyUI Video to Video node enables users to convert or transform videos using a ComfyUI workflow. It accepts an input image (or video frame) in various formats, processes it through a user-defined ComfyUI workflow, and outputs generated video content. This node is particularly useful for creative workflows involving AI-driven video generation or transformation, such as style transfer on videos, video enhancement, or generating new video sequences based on input frames.
Typical use cases include:
- Applying AI-based effects or transformations to videos.
- Generating new video content from a single image or video frame.
- Automating video processing pipelines with custom ComfyUI workflows.
Properties
| Name | Meaning |
|---|---|
| Workflow JSON | The ComfyUI workflow definition in JSON format that describes the video processing pipeline. |
| Input Type | The type of input image provided. Options: URL, Base64, or Binary. |
| Input Image | The URL or base64-encoded string of the input image (shown only if Input Type is URL or Base64). |
| Binary Property | The name of the binary property containing the input image data (shown only if Input Type is Binary). |
| Timeout | Maximum time in minutes to wait for the video generation process before timing out. |
Output
The node outputs an array of items where each item contains:
json: Metadata about the generated video including:
success: Boolean indicating if the operation succeeded.fileName: The filename of the generated video.fileSize: Human-readable size of the video file.fileSizeBytes: Size of the video file in bytes.contentType: MIME type of the video (e.g.,video/mp4).downloadUrl: URL where the generated video can be accessed.timestamp: ISO timestamp when the video was generated.
binary: Contains the actual video data prepared as binary data under the property
data.
This output structure allows downstream nodes to access both metadata and the raw video content for further processing or storage.
Dependencies
- Requires an API key credential for authenticating with the ComfyUI API service.
- Needs the ComfyUI API URL endpoint configured in credentials.
- Uses internal helper classes for handling different input types (
URL,Base64,Binary) and for managing workflow parsing and polling. - Relies on HTTP requests to upload images, submit workflows, poll for completion, and download resulting videos.
Troubleshooting
- Timeouts: If video generation takes longer than the specified timeout, the node will fail. Increase the timeout property if needed.
- No media outputs found: Indicates the workflow did not produce any video or image outputs. Verify the workflow JSON and ensure it generates expected outputs.
- No video outputs found: The node expects at least one video output file (
.mp4,.webp,.gif). If none are found, check the workflow configuration. - Download failures: The node retries downloading the video up to 3 times. Persistent HTTP errors (403, 404) indicate issues with the ComfyUI server or invalid URLs.
- Authorization errors: Ensure the API key credential is valid and has proper permissions.
- Invalid input data: Make sure the input image is correctly provided according to the selected input type.
Common error messages are wrapped as node API errors with descriptive messages to help identify the failure point.
Links and References
- ComfyUI Official Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes
- General info on Handling Binary Data in n8n
If you need details on other resources or operations, please provide their names.