Appwrite icon

Appwrite

A comprehensive node for the Appwrite API

Overview

This node integrates with the Appwrite API to manage users and other resources. Specifically, for the User - Delete operation, it deletes a user identified by their unique User ID from the Appwrite backend. This is useful in scenarios where you want to programmatically remove user accounts, such as cleaning up test users, managing user lifecycle in an application, or automating account deletions based on certain triggers.

Practical example: Automatically deleting a user after they request account removal via a form submission, ensuring compliance with data privacy regulations.

Properties

Name Meaning
User ID The unique identifier of the user to delete. This must be provided to specify which user to remove.

Output

The output JSON contains a single field indicating success:

{
  "success": true
}

This confirms that the user was successfully deleted. No additional data is returned. The node does not output binary data for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Appwrite API.
  • The node depends on the Appwrite client library internally to perform API calls.
  • Proper configuration of the Appwrite API credentials in n8n is necessary.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent User ID will likely cause an error.
    • Missing or incorrect API credentials will prevent successful authentication.
    • Network connectivity issues can cause timeouts or failures.
  • Error messages:

    • Errors thrown by the node include detailed messages from the Appwrite API response when available.
    • If the user does not exist, the API may return a "not found" error.
    • Authentication errors indicate problems with the API key or permissions.
  • Resolutions:

    • Verify the User ID is correct and exists in your Appwrite project.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Check network connectivity and firewall settings.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.

Links and References

Discussion