ZAppwrite icon

ZAppwrite

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

Overview

The node integrates with the Appwrite API to manage users and their related data. Specifically, for the Delete User operation under the Users resource, it deletes a user identified by a given User ID from the Appwrite backend.

This node is beneficial in scenarios where you need to automate user lifecycle management within your applications or workflows, such as removing users who no longer have access or cleaning up test accounts. For example, after processing a user's data or upon account termination, this node can be used to programmatically delete that user from the system.

Properties

Name Meaning
User ID The unique identifier of the user to delete. This is required to specify which user will be removed from the Appwrite system.

Output

The output JSON contains a single field:

  • success: A boolean indicating whether the deletion was successful (true) or not (false).

Example output:

[
  {
    "success": true
  }
]

No binary data is output by this operation.

Dependencies

  • Requires an active connection to an Appwrite server.
  • Needs credentials including the Appwrite endpoint URL, project ID, and an API key credential with sufficient permissions to delete users.
  • The node uses the official Appwrite SDK internally to perform API calls.

Troubleshooting

  • Common issues:

    • Invalid or missing User ID: The operation requires a valid User ID; ensure this is correctly provided.
    • Insufficient permissions: The API key used must have rights to delete users; otherwise, the request will fail.
    • Network or connectivity problems: Ensure the Appwrite server URL is reachable from n8n.
  • Common error messages:

    • "Resource not found": This may occur if the specified User ID does not exist.
    • Authentication errors: Indicate invalid or expired API keys.
  • Resolution tips:

    • Double-check the User ID input.
    • Verify API key permissions and validity.
    • Confirm network connectivity to the Appwrite server.
    • Enable "Continue on Fail" in the node settings to handle errors gracefully in workflows.

Links and References

Discussion