UseAPI icon

UseAPI

Interact with RunwayML through UseAPI
Join our community

Actions22

Overview

This node integrates with the UseAPI service to interact with RunwayML, specifically enabling users to retrieve assets from their RunwayML account. The "Retrieve assets" operation fetches a paginated list of media assets such as videos, images, or audio files stored in RunwayML.

Common scenarios where this node is beneficial include:

  • Automating the retrieval and processing of media assets for further workflows.
  • Filtering assets by ID, name, or media type to find specific content.
  • Managing large collections of media by paginating through assets using offset and limit parameters.

Practical example:

  • A user wants to get the first 50 video assets starting from the 100th asset in their RunwayML library, filtering only those whose names contain "promo". This node can perform that query and return the filtered list for downstream automation.

Properties

Name Meaning
Offset Starting position for pagination (0-1000). Determines which asset index to start retrieving from.
Limit Maximum number of results to return. Controls how many assets are fetched per request.
Filter By Field to filter the results by. Options: None, Asset ID, Asset Name, Media Type.
Filter Value Value to filter by, applied when a filter field other than "None" is selected.
Additional Fields Collection of extra optional fields. Currently supports: Media Type filter with options All, Video, Image, Audio.

Output

The output is a JSON array where each item corresponds to an asset retrieved from RunwayML. Each asset object typically contains metadata such as:

  • id: Unique identifier of the asset.
  • name: Name of the asset.
  • mediaType: Type of media (e.g., video, image, audio).
  • Other asset-specific metadata returned by the API.

The node does not output binary data directly for this operation; it only returns JSON metadata about the assets.

Dependencies

  • Requires an API key credential for UseAPI with access to RunwayML endpoints.
  • The node makes HTTP GET requests to the UseAPI endpoint at https://api.useapi.net/v1/runwayml/assets/.
  • Proper configuration of the API key credential in n8n is necessary for authentication.

Troubleshooting

  • No assets returned or empty list:
    Check that the offset and limit values are within valid ranges and that the API key has proper permissions. Also verify if any filters applied are too restrictive.

  • Filter not working as expected:
    Ensure the filter value matches the case-insensitive substring search logic used by the node. For exact ID filtering, the filter value must exactly match the asset ID string.

  • Authentication errors:
    Confirm that the API key credential is correctly set up and has not expired or been revoked.

  • Pagination issues:
    Offset must be between 0 and 1000. Setting offset beyond available assets will result in empty responses.

  • API request failures:
    Network issues or API downtime can cause errors. Review error messages for HTTP status codes and retry accordingly.

Links and References

Discussion