ZAppwrite icon

ZAppwrite

Use Appwrite's API from inside N8N, updated by @ZachHandley

Overview

The node integrates with Appwrite's Storage service, allowing users to manage storage buckets and files programmatically within n8n workflows. Specifically, the "Delete Bucket" operation deletes a specified storage bucket from the Appwrite backend.

This node is beneficial in scenarios where automated cleanup or management of cloud storage resources is needed, such as removing obsolete buckets after data archival or managing storage lifecycle in response to workflow events.

Example use case: Automatically deleting a storage bucket when a project is completed or no longer needed, freeing up resources without manual intervention.

Properties

Name Meaning
Bucket ID The unique identifier of the storage bucket to delete

Output

The output JSON contains a single object with a success property indicating whether the deletion was successful. For example:

[
  {
    "success": true
  }
]

This confirms that the bucket was deleted successfully. If the deletion fails, an error will be thrown unless the node is configured to continue on failure.

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Appwrite API.
  • Needs the Appwrite endpoint URL and project ID configured in the credentials.
  • Uses the official Appwrite Node.js SDK internally.
  • No additional environment variables are required beyond the API credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing Bucket ID: Ensure the Bucket ID provided exists and is correct.
    • Insufficient permissions: The API key used must have permission to delete storage buckets.
    • Network or connectivity errors: Verify the Appwrite endpoint URL and network access.
  • Error messages:

    • "Resource not found": This may occur if the specified bucket does not exist.
    • Authentication errors: Check that the API key and project ID are valid and correctly configured.
  • To resolve errors, verify all input parameters, credentials, and network connectivity. Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.

Links and References

Discussion