UseAPI icon

UseAPI

Interact with RunwayML through UseAPI
Join our community

Actions22

Overview

This node integrates with the RunwayML service via the UseAPI platform to perform a "Video to Video" transformation. It allows users to input an existing video asset and apply changes described by a text prompt, producing a new edited video output. The node supports customization of the video's aspect ratio, structural transformation intensity, duration, and additional options such as random seed for reproducibility, explore mode usage, webhook callbacks, and parallel job limits.

Common scenarios include:

  • Enhancing or creatively modifying existing videos based on descriptive prompts.
  • Generating variations of a video asset with controlled degrees of change.
  • Automating video editing workflows that require AI-driven transformations.
  • Receiving asynchronous notifications when processing completes via webhooks.

Practical example:

  • A user has a short landscape video of a cityscape and wants to transform it into a futuristic version by providing a text prompt like "turn the city into a cyberpunk neon-lit environment." They can specify the aspect ratio as landscape, set structure transformation to 7 for significant changes, and request a 15-second output video. Optionally, they provide a webhook URL to get notified when the video is ready.

Properties

Name Meaning
Video Asset ID The required identifier (assetId) of the source video asset to edit. Users can retrieve available video assets using the API endpoint GET /assets/?mediaType=video.
Text Prompt A textual description of the desired changes to apply to the input video. This guides the AI transformation process.
Aspect Ratio The output video's aspect ratio. Options: Landscape or Portrait.
Structure Transformation A numeric value (0-10) controlling how much the video's structure changes. Higher values produce greater structural modifications; lower values keep the output closer to the original input. Default is 3.
Duration (Seconds) Desired length of the resulting video in seconds. Must be at least 1 second.
Additional Options A collection of optional parameters:
• Seed: Numeric random seed (1-4294967294) for reproducible results.
• Explore Mode: Boolean flag to enable Explore mode (requires special plan, does not consume credits).
• Reply URL: Webhook URL to receive completion notification.
• Reply Reference: Custom reference string included in callback.
• Max Jobs: Maximum number of parallel jobs allowed (1-10).

Output

The node outputs JSON data representing the response from the RunwayML API after submitting the video-to-video transformation request. This typically includes metadata about the created task or job, status information, and identifiers for tracking or retrieving the generated video.

If the operation supports asynchronous processing, the output may contain references to webhook callbacks or job IDs rather than immediate video content.

Binary data output is not directly handled by this node for this operation; instead, the output JSON provides information to access or download the processed video later.

Dependencies

  • Requires an active API key credential for UseAPI with access to RunwayML services.
  • Network connectivity to the UseAPI endpoints (https://api.useapi.net/v1/runwayml/gen3turbo/video).
  • Optional webhook URL support for asynchronous notifications.
  • Proper configuration of credentials in n8n to authenticate API requests.

Troubleshooting

  • Missing or invalid Video Asset ID: Ensure the provided assetId corresponds to an existing video asset accessible via the API. Use the asset listing endpoint to verify.
  • Invalid or empty Text Prompt: The prompt must be non-empty and descriptive enough to guide the transformation.
  • API authentication errors: Verify that the API key credential is correctly configured and has permissions for RunwayML operations.
  • Operation cancelled due to missing confirmation: Some operations require explicit confirmation; ensure all required confirmations are checked.
  • Webhook failures: If using Reply URL, ensure the webhook endpoint is reachable and properly handles incoming callbacks.
  • Exceeded max jobs limit: The maxJobs parameter must be between 1 and 10; setting outside this range will cause errors.
  • Explore Mode restrictions: Enabling Explore mode requires a specific subscription plan; using it without proper access may result in authorization errors.

Common error messages usually relate to invalid parameters, authentication failures, or network issues. Reviewing the API response details included in the node's error output helps diagnose problems.

Links and References

Discussion