NAppwrite icon

NAppwrite

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

Actions25

Overview

This node integrates with the Appwrite API to manage user accounts programmatically within n8n workflows. Specifically, the "Delete User" operation under the "Users" resource allows you to delete a user by their unique User ID.

Common scenarios where this node is beneficial include:

  • Automating user lifecycle management, such as removing users who no longer have access.
  • Integrating user deletion into broader workflows, e.g., when a user unsubscribes or is deactivated in another system.
  • Cleaning up test or temporary user accounts automatically.

Example use case:

  • After receiving a request from a CRM or support tool indicating a user should be removed, this node deletes the corresponding user account in Appwrite without manual intervention.

Properties

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

Output

The output JSON contains a single object with a success field indicating whether the deletion was successful.

Example output:

[
  {
    "success": true
  }
]

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

Dependencies

  • Requires an active connection to an Appwrite server.
  • Needs credentials including the Appwrite API URL, project ID, and an API key credential with permissions to manage users.
  • The node depends on the official Appwrite SDK (node-appwrite) for API communication.

Troubleshooting

  • Common issues:

    • Invalid or missing User ID: Ensure the User ID provided exists and is correct.
    • Insufficient permissions: The API key used must have rights to delete users.
    • Network or connectivity problems with the Appwrite server.

  • Error messages:

    • Errors related to authentication or authorization typically indicate invalid credentials or insufficient permissions.
    • "Resource not found" errors may occur if the User ID does not exist.

  • Resolution tips:

    • Verify the User ID is correct and corresponds to an existing user.
    • Check that the API key credential has appropriate permissions.
    • Confirm network connectivity and Appwrite server availability.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.

Links and References

Discussion