UseAPI icon

UseAPI

Interact with RunwayML through UseAPI
Join our community

Actions22

Overview

The node enables uploading assets (files) to the RunwayML platform via the UseAPI service. It supports uploading files either from binary data available in the workflow or by fetching a file from a specified URL. Additional metadata such as duration, width, and height can be provided for audio, video, or image files.

This node is beneficial when you want to programmatically add media assets to your RunwayML account for further processing, generation, or management within automated workflows. For example, you could upload an image captured or generated earlier in the workflow, or fetch a remote video file by URL and upload it directly to RunwayML.

Properties

Name Meaning
Name The name of the file to be created on RunwayML.
Input Type The source of the file to upload. Options: Binary Data (upload from workflow binary data), URL (upload by fetching from a URL).
Binary Property (Required if Input Type is Binary Data) The name of the binary property containing the file to upload.
URL (Required if Input Type is URL) The URL of the file to upload.
Additional Fields Optional additional metadata fields:
- Duration (Seconds) Duration in seconds for audio or video files.
- Width (Pixels) Width in pixels for image or video files.
- Height (Pixels) Height in pixels for image or video files.

Output

The node outputs JSON data representing the response from the RunwayML API after uploading the asset. This typically includes details about the newly created asset such as its ID, name, type, and any metadata returned by the API.

If the upload is successful, the output JSON contains the asset information confirming the upload. If there is an error, the output may contain error details.

The node does not output binary data itself; it only sends binary data as input for upload.

Dependencies

  • Requires an API key credential for authenticating with the UseAPI service that interfaces with RunwayML.
  • The node makes HTTP requests to the UseAPI endpoint at https://api.useapi.net/v1/runwayml/assets/.
  • Proper configuration of the API key credential with access rights to upload assets on RunwayML is necessary.

Troubleshooting

  • No binary data found: If Input Type is set to Binary Data but no binary data exists on the specified property, the node will throw an error. Ensure the binary data is correctly passed into the node and the property name matches.
  • Invalid URL or inaccessible resource: When using URL input type, if the URL is invalid or the file cannot be fetched, the request will fail. Verify the URL is correct and publicly accessible.
  • Missing required parameters: The Name property is mandatory. Omitting it will cause errors.
  • Incorrect MIME type detection: The node attempts to infer the content type from the file extension when uploading from URL. Unsupported or unknown extensions default to application/octet-stream, which might cause issues if the server expects specific types.
  • API authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate. Check the credential setup.
  • Additional fields validation: Providing invalid values (e.g., negative numbers) for duration, width, or height may cause unexpected behavior or API rejection.

Links and References

Discussion