UseAPI icon

UseAPI

Interact with RunwayML through UseAPI
Join our community

Actions22

Overview

This node integrates with the RunwayML service via the UseAPI platform, specifically enabling the creation of videos using the "Gen-3 Turbo Create" operation. It allows users to generate short videos by providing one or more input images and a descriptive text prompt. The node supports customization of video properties such as aspect ratio, duration, random seed for reproducibility, and various camera motion effects.

Typical use cases include:

  • Creating AI-generated video content from static images and textual descriptions.
  • Experimenting with different camera motions and visual styles in generated videos.
  • Automating video generation workflows where input images and prompts are dynamically provided.

For example, a user can input a single image asset ID along with a text prompt describing the desired video scene, specify a landscape aspect ratio and 10 seconds duration, and optionally add camera zoom and pan effects to produce a dynamic video output.

Properties

Name Meaning
Image Input Select which image positions to use for video generation:
• First Image
• First and Last Images
• First, Middle, and Last Images
First Image Asset ID Asset ID of the first image (required). This is the primary image used as input for video creation.
Middle Image Asset ID Asset ID of the middle image. Required only if "First, Middle, and Last Images" option is selected.
Last Image Asset ID Asset ID of the last image. Required if "First and Last Images" or "First, Middle, and Last Images" options are selected.
Text Prompt Text description of the video content to create. This guides the AI in generating the video.
Aspect Ratio Aspect ratio of the output video:
• Landscape
• Portrait
Duration (Seconds) Length of the generated video in seconds:
• 5 Seconds
• 10 Seconds
Seed Optional numeric random seed (1 to 4294967294) for reproducible results. If set, the same inputs will produce consistent outputs.
Camera Motion Collection of camera motion settings to customize video dynamics:
• Static Camera (boolean): keep camera still
• Horizontal Motion (-10 to 10)
• Vertical Motion (-10 to 10)
• Zoom (-10 to 10)
• Roll (-10 to 10)
• Pan (-10 to 10)
• Tilt (-10 to 10)
Additional Settings Additional optional settings:
• Explore Mode (boolean): uses Explore mode (requires special plan, does not consume credits)
• Reply URL: webhook URL for completion notification
• Reply Reference: custom callback ID
• Max Jobs (1-10): max parallel jobs

Output

The node outputs JSON data representing the response from the RunwayML Gen-3 Turbo Create API endpoint. This typically includes information about the created video job, such as job ID, status, and metadata related to the video generation request.

The exact structure depends on the API response but generally contains fields like:

  • Job or task identifiers
  • Status indicators (e.g., queued, processing, completed)
  • URLs or asset IDs for accessing the generated video once ready

No binary data output is directly handled by this node; it focuses on initiating the video creation process and returning the API's JSON response.

Dependencies

  • Requires an API key credential for UseAPI with access to RunwayML endpoints.
  • The node makes HTTP requests to the UseAPI service at https://api.useapi.net/v1/runwayml/gen3turbo/create.
  • For webhook notifications, users can provide a callback URL in the "Reply URL" property.
  • Proper configuration of credentials and permissions in n8n is necessary to authenticate API calls.

Troubleshooting

  • Missing required image asset IDs: Ensure that the asset IDs for the selected image positions (first, middle, last) are provided as per the "Image Input" selection.
  • Invalid seed value: The seed must be a number between 1 and 4294967294; otherwise, the API may reject the request.
  • API authentication errors: Verify that the API key credential is correctly configured and has access rights to RunwayML services.
  • Webhook failures: If using "Reply URL," ensure the URL is reachable and properly handles incoming callbacks.
  • Exceeded max jobs: The "Max Jobs" setting limits parallel jobs; setting too high a value might cause API rejections depending on account limits.
  • Operation cancellation: Some operations require explicit confirmation; although not applicable here, always check for required confirmations in other operations.

Common error messages usually relate to invalid parameters, missing credentials, or network issues. Reviewing the error details returned in the node output helps diagnose problems.

Links and References

Discussion