Actions44
- User Actions
- Database Actions
- Collection Actions
- Document Actions
- Index Actions
- Function Actions
- Storage Actions
Overview
This node integrates with the Appwrite API to manage storage buckets and files. Specifically, the "Create Bucket" operation allows users to create a new storage bucket within their Appwrite project. This is useful for organizing and controlling access to groups of files in cloud storage.
Common scenarios include:
- Setting up isolated storage areas for different projects or teams.
- Defining access permissions on buckets to control who can read or write files.
- Automating bucket creation as part of deployment or content management workflows.
For example, you might use this node to programmatically create a bucket named "project-assets" with specific roles allowed to access it, enabling secure file uploads and downloads within your application.
Properties
| Name | Meaning |
|---|---|
| Bucket ID | Unique identifier for the bucket. Use "unique()" to auto-generate an ID when creating. Required for all file operations referencing this bucket. |
| Name | The display name for the new bucket being created. |
| Permissions | JSON array of role strings defining access permissions for the bucket. Example: ["role:all"] grants access to all roles. |
Output
The output is a JSON object representing the newly created bucket's details as returned by the Appwrite API. This typically includes properties such as the bucket's ID, name, permissions, creation date, and other metadata.
No binary data is output for this operation.
Dependencies
- Requires an active connection to the Appwrite API via an API key credential configured in n8n.
- The node uses the Appwrite client library internally to communicate with the Appwrite server.
- Proper permissions on the Appwrite project are necessary to create storage buckets.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Using a non-unique or already existing Bucket ID may result in errors.
- Improperly formatted permissions JSON can cause parsing errors.
Error messages:
- Authentication errors indicate invalid or missing API keys; verify credentials in n8n.
- Validation errors about bucket ID uniqueness require using
"unique()"or a truly unique string. - JSON parse errors for permissions mean the input is not valid JSON; ensure correct syntax.
Resolving these usually involves checking credentials, ensuring unique bucket IDs, and validating JSON inputs.