generate-video

Generate, edit, or extend a video using Comfy Cloud based on the user's description: $ARGUMENTS

Follow these steps exactly:

Step 0 — Route the named model family. If the user named a provider, model, or capability (e.g. "Kling", "Veo", "Sora", "Runway", "MiniMax"), check both routes before doing anything else: one search_nodes lookup with the named term (for the partner/API node), and one search_templates lookup with the family name (for an OSS template). Some families — MiniMax H3 is a current example — ship as BOTH OSS weights and a paid partner node under the same display title; others exist only as a partner node. Tell them apart by internal name (an OSS template/node uses a plain prefix like video_*; a partner/API node uses api_* and lives under a partner/ category) and, where the search results expose it, row tags.

• Family exists only as partner/API (no matching OSS template, node category starts with partner/): route directly. Try partner_generate first — see its tool description for the currently-wired model ids. Pass type: "video" plus the partner's model slug, prompt, and any optional fields (aspect_ratio/seed/duration/medias[]). On success, return the artifact URL(s) and stop — do NOT continue with the workflow steps below. If partner_generate returns "unknown model" or "not yet implemented", continue to Step 1.
• Family exists as both OSS and partner/API: do NOT auto-route to the paid path. Tell the user both options exist — OSS (no partner/API fee, but running it still spends ordinary Comfy Cloud compute credits, and it's typically slower; it's only actually free of charge when the user runs it themselves on their own local ComfyUI install) vs. paid partner/API (fast, no local hardware concern, costs the partner's per-run price on top of compute) — and ask which they want, unless they already said which one (e.g. "the free version", "local", "OSS", or named a paid partner product explicitly) or one route is genuinely infeasible right now. Once the route is chosen: partner/API continues as in the bullet above; OSS continues to Step 1 using the matching template.

Never tell a user the OSS route doesn't exist for a family that has one — that's a wrong answer, not a cautious one.

1. Use search_templates with relevant queries like "text to video", "image to video", or "video generation" to find a pre-built video workflow template. Filter by tag "video" if the text search returns too many image results. If a good template exists, use it as the base workflow instead of building from scratch.

2. If no suitable template was found, use search_models to find an appropriate video model. Common video models include: LTX-Video, Wan Video, HunyuanVideo, AnimateDiff, CogVideoX. Pick the best match based on the user's description.

3. If the user provides an input image (for image-to-video), use upload_file to upload it first. Use the returned filename in a LoadImage node.

4. Build a ComfyUI API-format workflow JSON with the appropriate video nodes. Video workflows typically use specialized loader nodes (e.g. LTXVLoader, WanVideoModelLoader), video-specific samplers, and video output nodes (e.g. VHS_VideoCombine). If using a template, modify the prompt and settings as needed.

5. Validate the workflow has inputs and outputs before submitting. Confirm the JSON contains:

   • At least one input node the user's intent flows through (CLIPTextEncode for the prompt, LoadImage for image-to-video, etc.).
   • At least one output/save node wired to the final video tensor (e.g. VHS_VideoCombine, SaveAnimatedWEBP, SaveVideo, or the partner node's own save output).

   API-backed partner nodes (Kling, Nano Banana, Gemini, Veo, etc.) often produce a video tensor but do not include a save node by default — you must add one and wire it to their output. Without it the job runs successfully but produces nothing retrievable, wasting compute. Do not skip this check.

6. Call submit_workflow with the workflow JSON. Note: video generation typically takes longer than image generation (30s-2min+).