Do I need a powerful GPU to use this workflow?

No. The MinimaxTextToVideoNode calls the MiniMax API for generation, so heavy compute happens remotely. Your local machine only needs to run ComfyUI and maintain a network connection.

Why does the node fail or time out?

Common causes are networking or credential issues. Confirm you meet the secure environment requirements (localhost access or HTTPS for web services), your API key/endpoint are correct, and your firewall allows outbound requests to the MiniMax API.

How can I control duration, resolution, or aspect ratio?

Use any parameters the MinimaxTextToVideoNode exposes in your workflow. If a setting isn’t available in the node UI, consult the MiniMax provider docs for supported options. Some services may also respect prompt cues (e.g., 9:16) but this is not guaranteed.

How do I get cleaner, more on-style results?

Write specific prompts that include subject, action, environment, and style cues (e.g., cinematic lighting, stylized CGI). Keep motions simple for short clips, avoid overly rapid scene changes, and iterate in small steps. If the node supports it, adjust duration and other parameters conservatively.

MiniMax: Text to Video - ComfyUI Workflow

This ComfyUI tutorial walks you through a minimal, reliable text-to-video pipeline powered by the MiniMax API. The core of the workflow is the MinimaxTextToVideoNode, which sends your text prompt to MiniMax’s text-to-video service and returns a generated video clip. A MarkdownNote node is included in the graph to remind you of the provider’s secure network requirements (localhost access, HTTPS usage, and ensuring you can reach the API). Finally, a SaveVideo node writes the returned clip to disk so you can review and reuse it in your projects.

Technically, the MinimaxTextToVideoNode handles the API call and response lifecycle inside ComfyUI. You supply the prompt (and any parameters the node exposes, such as clip length or resolution if available), the node waits for the remote job to complete, and then forwards the resulting video to SaveVideo. SaveVideo stores the clip in your ComfyUI output directory using the file name settings you configure. Because inference happens on the MiniMax service, local GPU requirements are minimal—the main considerations are correct API credentials/configuration and meeting the secure networking rules noted in the MarkdownNote.

API

Use this workflow from code

Every Comfy workflow is a JSON graph. The payload below is this workflow, exactly as ComfyUI runs it — fetch it from the URL, keep it in version control, or load it in ComfyUI and run it node by node.

api_hailuo_minimax_t2v.json

Fetching workflow JSON…

Run it from TypeScript or Python with the Comfy SDK. The same code targets Comfy Cloud or a ComfyUI you host yourself — only the base URL changes.

// Install (beta)
npm i @comfyorg/sdk

// Run this workflow (TypeScript)
import { Comfy } from "@comfyorg/sdk";

const client = new Comfy({ apiKey: "comfyui-..." });
const wf = await client.workflows.fromFile("workflow_api.json");
const job = await client.run(wf);
await job.getOutputs("<output-node-id>")[0].toFile("output.png");

The SDK takes a workflow in API format: open this workflow in ComfyUI and use File → Export Workflow (API).

Comfy Cloud API access requires a plan with an API key.

SDK docs Get an API key

FAQ

Frequently Asked Questions