Actions44
- User Actions
- Database Actions
- Collection Actions
- Document Actions
- Index Actions
- Function Actions
- Storage Actions
Overview
This node interacts with the Storage resource of the Appwrite API, specifically supporting operations related to storage buckets and files. The "Get Bucket" operation retrieves metadata and details about a specific storage bucket identified by its unique ID. This is useful when you want to inspect or verify the properties of an existing bucket before performing further file operations such as uploading or listing files.
Practical examples include:
- Fetching bucket information to confirm its existence and settings.
- Using bucket metadata to conditionally process files or manage storage organization.
- Integrating with workflows that automate storage management based on bucket attributes.
Properties
| Name | Meaning |
|---|---|
| Bucket ID | Unique identifier for the storage bucket. Required for all file and bucket operations. Use "unique()" to auto-generate when creating a new bucket. |
Output
The output JSON contains the detailed information of the requested storage bucket. This typically includes bucket metadata such as its ID, name, permissions, creation date, and other relevant attributes defined by the Appwrite Storage service.
If the node performs file download operations (not applicable for "Get Bucket"), it outputs binary data representing the file content.
Dependencies
- Requires an API key credential for authenticating with the Appwrite API.
- Needs proper configuration of the Appwrite client within n8n, including setting up credentials with access rights to the Storage service.
- Relies on the Appwrite SDK or API client internally to perform requests.
Troubleshooting
Common issues:
- Invalid or missing Bucket ID will cause the operation to fail.
- Insufficient permissions in the API key may result in authorization errors.
- Network connectivity problems can prevent communication with the Appwrite server.
Error messages:
- Errors from the Appwrite API are caught and returned with details if available.
- If the bucket does not exist, expect an error indicating "bucket not found" or similar.
- Authentication failures will prompt errors related to invalid credentials or unauthorized access.
Resolutions:
- Verify the Bucket ID is correct and exists in your Appwrite project.
- Ensure the API key has the necessary permissions for storage operations.
- Check network connectivity and endpoint URLs configured in the credentials.