Video Generator Tools

The Video Generator provider turns text prompts and reference images into AI-generated videos through five underlying engines: Runway, Luma AI, MiniMax, fal.ai, and Google Veo. Use these tools in a workflow when you need to produce short marketing clips, animations, or image-to-video sequences without leaving the canvas.

Overview

Operations

Configuration

runway_generate_video

luma_generate_video

minimax_generate_video

falai_generate_video

veo_generate_video

Outputs

All five tools share the same output schema.

runway_generate_video

• videoUrl (string) — URL of the generated video.
• videoFile (json) — Generated video file object.
• duration (number) — Duration of the video in seconds.
• width (number) — Width of the video in pixels.
• height (number) — Height of the video in pixels.
• provider (string) — Provider used for generation.
• model (string) — Model used for generation.
• jobId (string) — Job ID of the generation request.

luma_generate_video

• videoUrl (string) — URL of the generated video.
• videoFile (json) — Generated video file object.
• duration (number) — Duration of the video in seconds.
• width (number) — Width of the video in pixels.
• height (number) — Height of the video in pixels.
• provider (string) — Provider used for generation.
• model (string) — Model used for generation.
• jobId (string) — Job ID of the generation request.

minimax_generate_video

• videoUrl (string) — URL of the generated video.
• videoFile (json) — Generated video file object.
• duration (number) — Duration of the video in seconds.
• width (number) — Width of the video in pixels.
• height (number) — Height of the video in pixels.
• provider (string) — Provider used for generation.
• model (string) — Model used for generation.
• jobId (string) — Job ID of the generation request.

falai_generate_video

• videoUrl (string) — URL of the generated video.
• videoFile (json) — Generated video file object.
• duration (number) — Duration of the video in seconds.
• width (number) — Width of the video in pixels.
• height (number) — Height of the video in pixels.
• provider (string) — Provider used for generation.
• model (string) — Model used for generation.
• jobId (string) — Job ID of the generation request.

veo_generate_video

• videoUrl (string) — URL of the generated video.
• videoFile (json) — Generated video file object.
• duration (number) — Duration of the video in seconds.
• width (number) — Width of the video in pixels.
• height (number) — Height of the video in pixels.
• provider (string) — Provider used for generation.
• model (string) — Model used for generation.
• jobId (string) — Job ID of the generation request.

YAML Example

video_generator_1:
  type: video_generator
  name: "Video Generator"
  inputs:
    operation: "runway_generate_video"
    apiKey: "{{RUNWAY_API_KEY}}"
    prompt: "A cinematic drone shot flying over a misty mountain range at sunrise"
    duration: 5
    aspectRatio: "16:9"
  connections:
    outgoing:
      - target: next-block-id

Tips

• Each provider needs its own API key. Store the relevant secret (RUNWAY_API_KEY, LUMA_API_KEY, MINIMAX_API_KEY, FALAI_API_KEY, or GOOGLE_AI_API_KEY) as an environment variable and reference it with {{ENV_VAR}} — never paste keys inline. The apiKey param is user-only, so an LLM can never fill it.
• Only falai_generate_video requires a model value (a full fal.ai endpoint such as fal-ai/kling-video/v2.1/standard/text-to-video); the other tools fall back to sensible defaults (Runway gen4_turbo, Veo veo-3).
• For image-to-video, pass either an imageUrl or an imageFile object as the first frame. Runway additionally supports endImageUrl for first-to-last-frame interpolation, and Luma exposes a cameraMotion object for directing camera movement.
• All tools route through the shared /api/tools/video endpoint and return a videoUrl plus a jobId; set a consistent seed to reproduce a result across runs.
• The video_generator block itself is legacy and hidden from the toolbar — for fine-grained control, prefer the individual provider blocks, but these tools remain fully available via the operation IDs above.