Overview
The HjhComfyUICheck node executes workflows on the HjhComfyUI platform, which appears to be a service for processing images and running custom workflows (likely related to image analysis or AI-based checks). The node sends a user-provided image along with a JSON-defined workflow to the HjhComfyUI API, optionally using additional Hjh services. It can either wait for the workflow execution to complete and return detailed results or just queue the workflow and return immediately.
This node is beneficial in scenarios where automated image analysis or validation is required within an n8n workflow, such as facial recognition, quality checks, or other AI-driven image processing tasks. For example, it could be used to verify user-submitted photos against certain criteria or to trigger downstream actions based on the analysis results.
Properties
| Name | Meaning |
|---|---|
| Use Hjh Services | Whether to use custom Hjh services specified in the workflow or default API credentials. |
| Hjh Services | JSON string defining the Hjh services to use; expects a comfyui_check field with URLs. |
| Hjh User Image | The user image data (likely base64 or JSON) to be processed by the workflow (required). |
| Hjh Workflow JSON | The JSON definition of the HjhComfyUICheck 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 the workflow completion when waiting for results. |
Output
The node outputs a JSON array with one object containing the result of the workflow execution:
When waiting for results and successful:
code: HTTP-like status code (200 for success).message: Status message ("ok").description: Additional description ("ok").checkResult: Parsed check results from the workflow output, including face attributes and counts.promptResult: Raw prompt execution details from the HjhComfyUI API.promptId: The ID of the queued prompt/workflow.
When not waiting for results:
- Returns a simple acknowledgment with empty files and checkResult fields, plus the prompt ID.
On failure or timeout:
- Returns an error object with
code(e.g., 400 or 500),message, anddescriptionexplaining the failure reason.
- Returns an error object with
The node does not output binary data.
Dependencies
- Requires access to the HjhComfyUI API endpoint(s), either provided via the "Hjh Services" property or through configured API credentials.
- Optionally requires an API key for authentication, sent as a Bearer token in the Authorization header.
- Uses HTTP requests to interact with the HjhComfyUI API (
/system_stats,/prompt,/history/{prompt_id}endpoints). - Needs proper network connectivity and valid API credentials or service URLs.
Troubleshooting
- No available service error: If none of the provided or credentialed API URLs respond to the
/system_statscheck, the node will fail. Ensure the service URLs are correct and reachable. - Failed to get prompt ID: Indicates the POST request to queue the workflow did not return a valid prompt ID. Check the workflow JSON format and API availability.
- Workflow execution failed: Can occur if the workflow returns an error status or no outputs. Review the workflow JSON and input image correctness.
- Timeout after X seconds: The node waited for the specified timeout duration without the workflow completing. Increase the timeout or check the API responsiveness.
- No face found: Specific to this node's logic, if the workflow result contains zero detected faces, it throws an error. Verify the input image and workflow configuration.
- API key issues: If authentication fails, ensure the API key is correctly set and has necessary permissions.
In all error cases, enabling node logging and checking the console output can provide more detailed diagnostics.
Links and References
- No direct external links are provided in the source code.
- For more information, consult the HjhComfyUI API documentation or support resources (not included here).