Overview
The HjhComfyUIVideo node enables execution of HjhComfyUIVideo workflows by sending JSON workflow definitions to a compatible API service. It is designed to integrate video or image generation workflows into n8n automation, leveraging the HjhComfyUI backend services.
Typical use cases include:
- Automating video or image generation pipelines defined in HjhComfyUI.
- Integrating custom ComfyUI workflows into larger automation scenarios.
- Waiting for and retrieving results from asynchronous workflow executions.
For example, a user can provide a JSON definition of a video generation workflow, send it to the HjhComfyUI service, wait for completion, and then retrieve generated media file paths for further processing or storage.
Properties
| Name | Meaning |
|---|---|
| Use Hjh Services | Whether to use predefined Hjh services specified in the workflow or credentials for API URL. |
| Hjh Services | JSON string defining available Hjh services (comma-separated URLs). |
| Hjh Workflow JSON | The JSON representation of the HjhComfyUIVideo workflow to execute (required). |
| Wait For Result | Whether to wait for the workflow execution to complete before returning results. |
| Timeout | Maximum time in seconds to wait for workflow completion before timing out. |
Output
The node outputs a JSON array with one object containing:
code: HTTP-like status code (e.g., 200 for success).message: Status message ("ok" on success).description: Additional description, usually "ok".files: An array of file paths pointing to generated media files from the workflow.promptResult: The full raw response object from the workflow execution history.promptId: The unique identifier of the queued prompt/workflow execution.
If Wait For Result is false, the output contains an empty files array and minimal info about the queued prompt.
In case of errors, the output includes error codes and descriptive messages explaining the failure.
The node does not output binary data directly but provides file paths to generated content.
Dependencies
- Requires access to a running HjhComfyUI-compatible API endpoint that accepts workflow JSON prompts and returns execution status and results.
- Optionally uses an API key credential for authentication via Bearer token.
- Network connectivity to the specified API URL(s) is necessary.
- No other external dependencies are required.
Troubleshooting
- No available service: Occurs if none of the provided or configured API URLs respond to the
/system_statsendpoint within 1 second. Ensure the API URL is correct and the service is running. - Failed to get prompt ID: Indicates the POST request to queue the workflow did not return a valid prompt ID. Verify the workflow JSON format and API health.
- Execution timeout: Happens if the workflow does not complete within the specified timeout period. Increase the timeout or check the workflow complexity and API responsiveness.
- Workflow execution failed: Returned when the workflow status indicates an error. Check the detailed error message in the output for troubleshooting.
- No outputs found: Means the workflow completed but no result files were returned. Confirm the workflow produces outputs as expected.
To resolve issues:
- Validate the workflow JSON syntax.
- Confirm API URL and authentication details.
- Monitor API logs for errors.
- Adjust timeout settings based on workflow duration.
Links and References
- HjhComfyUI official documentation (replace with actual link if available)
- n8n Custom Node Development Guide
- ComfyUI GitHub Repository (for understanding workflow structures)
This summary is based solely on static analysis of the provided source code and property definitions.