Actions7
Overview
This node interacts with VolcEngine Cloud Object Storage (TOS) to perform various file and bucket operations. Specifically, the "Check File Existence" operation allows users to verify whether a specified file exists in their TOS storage and retrieve its URL if it does. This is useful for workflows that need to confirm the presence of files before proceeding with further processing, such as conditional logic based on file availability or triggering downstream actions only when certain files are present.
Practical examples:
- Before attempting to download or process a file, check if it exists to avoid errors.
- Validate that an upload was successful by checking the existence of the uploaded file.
- Use the file URL returned to share or reference the file in subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| File Path | The path and name of the file in TOS to check for existence. |
Output
The node outputs JSON data containing information about the file's existence and its URL if available. The exact structure depends on the underlying SDK response but generally includes:
- Confirmation whether the file exists.
- The accessible URL of the file in TOS if it exists.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for VolcEngine TOS with access permissions.
- Uses the official VolcEngine TOS SDK to interact with the cloud storage service.
- Node configuration must include valid credentials with accessKey, secretKey, region, endpoint, and bucket information.
Troubleshooting
Common issues:
- Missing or invalid credentials will cause authentication failures.
- Incorrect file paths may result in false negatives (file reported as not existing).
- Network or endpoint misconfiguration can prevent connection to TOS.
Error messages:
"No credentials returned!"indicates missing or improperly configured API credentials.- Errors from the SDK related to authorization or resource not found will be thrown; enabling "Continue On Fail" allows the workflow to handle these gracefully.
Resolutions:
- Verify that the API key credential is correctly set up and has necessary permissions.
- Double-check the file path for typos or incorrect folder names.
- Confirm network connectivity and correct endpoint configuration.