UseAPI icon

UseAPI

Interact with RunwayML through UseAPI
Join our community

Actions22

Overview

This node integrates with the Minimax API via UseAPI to perform various operations related to media assets, including images and videos. Specifically, the Retrieve Image operation fetches detailed information about a specific image stored in the Minimax service by its unique ID.

Common scenarios where this node is beneficial include:

  • Retrieving metadata or details of an image previously uploaded or created in Minimax.
  • Accessing image properties for further processing or decision-making in an automation workflow.
  • Integrating Minimax image data retrieval into larger multimedia or content pipelines.

For example, you might use this node to get the URL, dimensions, or other metadata of an image by providing its ID, then use that data downstream in your workflow to display the image or trigger additional processing.

Properties

Name Meaning
Image ID The unique identifier of the image to retrieve from Minimax. This is required to specify which image's details should be fetched.

Output

The node outputs a JSON object containing the retrieved image's details as returned by the Minimax API. This typically includes metadata such as image ID, URLs, dimensions, creation date, and possibly other descriptive fields depending on the API response.

No binary data output is indicated for this operation; the output is purely JSON metadata about the image.

Dependencies

  • Requires an active connection to the Minimax API via UseAPI.
  • Requires an API key credential configured in n8n for authenticating requests to Minimax.
  • The node makes HTTP GET requests to the endpoint: https://api.useapi.net/v1/minimax/images/{imageId}.

Troubleshooting

  • Missing or invalid Image ID: If the Image ID property is empty or incorrect, the API will likely return an error or no data. Ensure the correct image ID is provided.
  • Authentication errors: If the API key credential is missing, invalid, or expired, the request will fail with authorization errors. Verify that the API key is correctly set up in n8n credentials.
  • Network or API errors: Temporary network issues or API downtime can cause request failures. Check connectivity and API status.
  • Error messages: The node logs debug information on API request errors, including HTTP status codes and response bodies if available. Review these logs to diagnose issues.
  • Continue on Fail: If enabled, the node will output error details in JSON format instead of stopping execution, allowing workflows to handle errors gracefully.

Links and References

Discussion