Actions3
- Image Actions
Overview
This node interacts with the VolcEngine Elastic Compute Service (ECS) to perform operations related to images. Specifically, the "Detect Image" operation initiates an image detection task on a specified image by its ID. This is useful in scenarios where you want to analyze or process images using VolcEngine's detection capabilities, such as identifying objects, features, or other attributes within an image.
A practical example would be automating image analysis workflows where after uploading an image, you trigger detection to extract metadata or insights, and then later retrieve the detection results via another operation.
Properties
| Name | Meaning |
|---|---|
| Image ID | The unique identifier of the image on which to perform detection. Must be provided. |
Output
The output JSON object for the "Detect Image" operation includes:
success: Boolean indicating if the request was successfully initiated.requestId: The request identifier returned by the API.imageId: The ID of the image for which detection was started.message: A message confirming that the detection task has been initiated and instructing to use another interface to query the detection results.note: Additional information noting that detection results require some processing time before they can be retrieved.
The node does not output the detection results directly but rather confirms that the detection task has been triggered.
Dependencies
- Requires an API key credential for authenticating requests to VolcEngine ECS.
- The node makes HTTP POST requests to the VolcEngine ECS API endpoint at
https://open.volcengineapi.com. - The content type for requests is
application/x-www-form-urlencoded.
Troubleshooting
- Missing or empty Image ID: The node throws an error if the "Image ID" property is missing or empty. Ensure this field is correctly filled.
- API errors: If the API returns an error, it will be propagated unless "Continue On Fail" is enabled, in which case the error message will be included in the output JSON.
- Detection results delay: Since detection tasks are asynchronous, users might expect immediate results. The node only starts the detection; users must query results separately after some time.