MiniMax H3 Generate Video:
MiniMax H3 Generate Video sends a video-generation request to MiniMax and waits for the resulting task to finish. It brings video creation into your node workflow while giving you both the resulting video location and a record of the request and task response. This makes it useful when you want to generate a clip, check whether the task completed as expected, or keep the request details for later reference.
MiniMax H3 Generate Video Input Parameters:
content
The required video-generation content, supplied through a MINIMAX_H3_CONTENT connection. This is the material the node sends to MiniMax to guide the video. The provided source does not define the content type's full structure or a default value, so connect a compatible content-producing node rather than entering an assumed format. The content also affects aspect-ratio handling: content classified as frames is sent with the adaptive ratio.
resolution
Selects the requested video resolution. The node checks your choice against its supported resolution options and rejects an unsupported value before submitting the request. The default is the last entry in that options list. The provided source does not show the list itself, so its exact choices, minimum, and maximum cannot be stated here; use the options displayed by the node.
duration
Sets the requested clip length in seconds. The node converts the selected value to a whole number and checks it against its supported duration options before submitting the request. The default is 5 seconds. The provided source does not show the complete options list, so a minimum and maximum cannot be confirmed; choose from the durations displayed by the node.
ratio
Sets the requested video aspect ratio, which determines the shape of the frame. The default is 16:9. The provided source does not show the complete ratio options list. For text content, adaptive is not permitted: choose a concrete ratio instead. For content classified as frames, the node sends adaptive regardless of the ratio you selected.
MiniMax H3 Generate Video Output Parameters:
video_url
A text value containing the URL found in the final task's content. Use it as the location of the generated video when a URL is present. It can be an empty string if the final response does not contain that URL, so check status before treating it as a usable result.
task_id
A text identifier assigned when MiniMax accepts the generation request. It identifies the task the node waits for and is useful when you need to trace a particular generation attempt. If the create response contains no task ID, the node raises an error instead of producing outputs.
status
The status text reported by the final task response. Check it to understand the task's reported outcome; the provided source does not define the possible status values, so do not assume a particular success label.
task_json
A JSON-formatted text copy of the final task response. It preserves the returned task details in one output, which can help you inspect or record what MiniMax reported. It is the response data, not a guarantee that a video URL is available.
request_json
A JSON-formatted text copy of the request the node submitted. It records the selected model, content, resolution, duration, and effective ratio, along with request settings added by the node. Inspect it when you need to confirm what was actually sent, especially when frame content changed the ratio to adaptive.
MiniMax H3 Generate Video Usage Tips:
- Connect a compatible
MINIMAX_H3_CONTENTsource first. This node submits the supplied content; it does not provide a separate prompt field. - For text-based content, select a concrete ratio such as the default
16:9rather thanadaptive, which the node explicitly rejects for text-to-video. - For frame-based content, check
request_jsonif the aspect ratio matters to your workflow. The node sendsadaptivefor frames even when you selected another ratio. - Start with the default
5-second duration when testing a workflow, then select another displayed duration if you need a different clip length. Choose resolution and duration from the node's visible options. - Check
statusandvideo_urltogether before passing the URL to another step. Keeptask_idandtask_jsonwhen you need to investigate a result.
MiniMax H3 Generate Video Common Errors and Solutions:
Text-to-video requires a concrete ratio; adaptive is not allowed.
- Explanation: The supplied content is classified as text, but the selected ratio is
adaptive. - Solution: Select a concrete ratio from the node's displayed options, such as the default
16:9, and run the node again.
<model> does not support resolution <resolution>.
- Explanation: The resolution passed to the node is not in its supported resolution list. The words in angle brackets stand for the values shown in the actual error.
- Solution: Choose a resolution from this node's displayed options. If a saved workflow supplies an old value, reselect the resolution in the node.
<model> does not support duration <duration> seconds.
- Explanation: The requested duration is not in the node's supported duration list.
- Solution: Select one of the displayed duration options. The default is
5seconds.
MiniMax create response did not include task_id.
- Explanation: The create request returned no task ID, so the node cannot identify or wait for the generation task.
- Solution: Retry the request. If it happens again, check the MiniMax service response and your client configuration; the node cannot produce a completed result without a task ID.
Request-size validation error
- Explanation: The node checks the assembled request size before sending it. The provided source does not show the validator's exact error message or limit.
- Solution: Reduce the size of the connected content where possible, then retry. Consult the error details shown by your workflow for the limit that applies.
Missing video URL in the result
- Explanation: If the final task response has no content URL,
video_urlis an empty string. The provided source does not define this as a separate thrown error. - Solution: Inspect
statusandtask_jsonto see what the final response reports. Do not pass an empty URL to a downstream video step.
