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 user-related operations, specifically including deleting all sessions of a user. The "Delete Sessions" operation under the "User" resource allows you to invalidate or remove all active sessions for a specified user by their unique ID. This is useful in scenarios such as security enforcement (e.g., logging out a user from all devices), account management, or compliance where session revocation is required.
Practical examples:
- Automatically log out a user from all devices after a password reset.
- Revoke access for a user who has been deactivated or banned.
- Clear sessions during troubleshooting or security audits.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose sessions will be deleted. |
Output
The output JSON contains a simple success confirmation object indicating whether the deletion of sessions was successful. For example:
{
"success": true
}
No binary data is produced by 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 within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing User ID: Ensure the User ID provided exists and is correctly formatted.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or connectivity problems: Check network access to the Appwrite server.
Error messages:
- Errors returned from the Appwrite API are wrapped and surfaced by the node. They may include HTTP status codes and descriptive messages.
- If the node throws an error about missing parameters, confirm that the User ID is set and not empty.
- For permission denied errors, check the API key's scope and user privileges.