Actions22
- Runway Actions
- Minimax Actions
- Midjourney Actions
Overview
The node provides integration with the RunwayML platform via the UseAPI service, enabling users to interact with RunwayML assets and perform various operations such as retrieving asset details, listing assets, uploading, deleting, and generating media content. Specifically, the Get Asset operation fetches detailed information about a single asset on RunwayML by its unique asset ID.
This node is beneficial in scenarios where automation workflows require accessing metadata or properties of specific media assets stored in RunwayML, for example:
- Retrieving an image or video asset's metadata to use in downstream processing.
- Verifying asset existence or status before triggering further actions.
- Integrating RunwayML asset data into other systems or dashboards.
Practical example: A user wants to automatically fetch details of a generated video asset by its ID after a generation job completes, to log or analyze its properties.
Properties
| Name | Meaning |
|---|---|
| Asset ID | The unique identifier of the asset to retrieve. It must be in the format user:user_id-runwayml:account_email-asset:asset_uuid. This ID specifies exactly which asset's details to fetch from RunwayML. |
Output
The output is a JSON object containing the full details of the requested asset as returned by the RunwayML API. This typically includes metadata such as asset ID, type, creation date, URLs, and any other descriptive fields provided by RunwayML for that asset.
If the asset retrieval fails, the output will contain an error object describing the failure.
The node does not output binary data for this operation; it only returns JSON metadata about the asset.
Dependencies
- Requires an active API key credential for UseAPI configured in n8n to authenticate requests to the RunwayML endpoints.
- Network access to
https://api.useapi.net/v1/runwayml/assets/{assetId}is required. - Proper formatting of the Asset ID string is necessary to successfully query the asset.
Troubleshooting
- Invalid or missing Asset ID: If the Asset ID is malformed or empty, the API request will fail. Ensure the Asset ID follows the required format and is correctly specified.
- Authentication errors: If the API key credential is missing, invalid, or expired, the node will return authorization errors. Verify the API key configuration in n8n credentials.
- Asset not found: If the asset ID does not exist on RunwayML, the API will respond with a not found error. Confirm the asset ID is correct and the asset exists.
- Network issues: Connectivity problems to the UseAPI endpoint can cause request failures. Check network settings and firewall rules.
- API rate limits: Excessive requests may trigger rate limiting by the API. Implement retry logic or reduce request frequency if needed.
Common error messages include:
"Operation cancelled: You must confirm the deletion by checking the confirmation checkbox."(not applicable here but seen in related operations)"No binary data found"(not relevant for Get Asset)- HTTP 401 Unauthorized or 403 Forbidden indicating authentication issues
- HTTP 404 Not Found indicating invalid asset ID
Resolving these usually involves verifying input parameters, credentials, and network connectivity.
Links and References
- RunwayML API Documentation (for understanding asset IDs and asset metadata)
- UseAPI Service (the intermediary API service used to access RunwayML)
- n8n documentation on Creating Custom Nodes