Skip to content
Nappai Documentation

Runway video Generator

Runway video Generator is a tool in Nappai that lets you create short videos from text prompts or image inputs. It talks to the Runway API, so you’ll need a Runway API key set up in Nappai’s credentials first. Once you have that, you can drop the component into a workflow, set the parameters, and let the AI do the heavy lifting.

How it Works

When you run the component, Nappai sends a request to the Runway API with the settings you chose (prompt, aspect ratio, duration, etc.). Runway processes the request, generates a video, and returns a URL or file ID that Nappai stores as a Data object. The component also exposes a Tool output that can be used by Nappai’s AI agents to call the generator directly from a conversation.

Inputs

Mapping Mode

This component has a special mode called Mapping Mode. When you enable this mode using the toggle switch, an additional input called Mapping Data is activated, and each input field offers you three different ways to provide data:

  • Fixed: You type the value directly into the field.
  • Mapped: You connect the output of another component to use its result as the value.
  • Javascript: You write Javascript code to dynamically calculate the value.

This flexibility allows you to create more dynamic and connected workflows.

Input Fields

  • Image Files: The list of image files (URL or File Id) to use for image generation.
  • Aspect Ratio: The aspect ratio of the generated video.
  • Duration (seconds): The duration of the video in seconds (5‑10 for Gen4/Gen3).
  • Generation Mode: Mode of video generation.
  • Height: Height of the generated video in pixels.
  • Video Model: The Runway ML model to use for video generation.
  • Motion Intensity: Controls the amount of motion in the video (1‑255).
  • Negative Prompt: What you don’t want in the video.
  • Prompt: A text description of the desired video. The maximum length is 512 characters.
  • Seed: Random seed for reproducible results. Leave empty for random.
  • Width: Width of the generated video in pixels.
  • Tool Name: The name of the tool that will be used when this component is connected as a tool. This name will be displayed to the agent when it selects tools to use.
  • Tool Description: A detailed description of what this tool does. This description will help the agent understand when and how to use this tool effectively.
  • Tools arguments metadata: Defines the arguments metadata for the tools.

Credential – This component requires a Runway API credential.

  1. In Nappai, go to Credentials and add a new Runway API credential.
  2. Enter your Runway ML API Key (password).
  3. Back in the component, select that credential in the Credential field.

Outputs

  • Video: A Data object containing the generated video (URL or file ID).
  • Tool: A Tool object that can be used by Nappai’s AI agents to invoke the generator programmatically.

Usage Example

  1. Add the component to your workflow.
  2. Configure the credential as described above.
  3. Set the Prompt to something like “A sunrise over a mountain range, cinematic music.”
  4. Choose a Video Model such as “Gen4” and set Duration (seconds) to 8.
  5. Enable Mapping Mode if you want to generate multiple videos from a list of prompts.
  6. Run the workflow. The component will return a video URL in the Video output that you can feed into a display component or send to a user.
  • RunwayImageGenerator – Generates still images using the Runway API.
  • RunwayTextToVideo – Another video generator that accepts only text prompts (no image inputs).

Tips and Best Practices

  • Keep prompts concise; the maximum length is 512 characters.
  • Use Seed if you need reproducible results across runs.
  • For batch processing, enable Mapping Mode and feed a list of prompts or image URLs.
  • If you’re not sure about the aspect ratio, try “16:9” for standard widescreen videos.
  • Test with short durations (5‑10 seconds) first to confirm the output before scaling up.

Security Considerations

  • The Runway API key is stored securely in Nappai’s credential store.
  • Never expose the key in your workflow or share the component’s configuration publicly.
  • Use the Credential field to reference the stored key; the key itself never appears in the component’s input list.