Actions25
- Document Actions
- Function Actions
- Storage Actions
- Users Actions
Overview
This node integrates with the Appwrite API to manage user-related data and operations. Specifically, for the "Users" resource and the "List User Identities" operation, it retrieves all identities associated with a specified user ID. This is useful in scenarios where you need to fetch authentication methods or linked identity providers for a user, such as social logins or email/password credentials.
Practical examples include:
- Auditing which identities a user has connected to their account.
- Synchronizing user identity information with other systems.
- Displaying linked login methods in a user profile management interface.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose identities you want to list. This is a required string input. |
Output
The output is a JSON array containing the list of user identities associated with the given User ID. Each item in the array represents an identity object, typically including details such as identity provider type, provider user ID, and related metadata.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to an Appwrite server.
- Needs valid credentials including the Appwrite API URL, project ID, and an API key credential configured in n8n.
- Uses the official Appwrite SDK internally to communicate with the Appwrite API.
Troubleshooting
Common issues:
- Invalid or missing User ID parameter will cause the operation to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity problems to the Appwrite server can cause timeouts or connection failures.
Error messages:
- Errors returned from the Appwrite API (e.g., "User not found") indicate that the provided User ID does not exist.
- Authentication errors suggest checking the API key and project configuration.
- If the node throws a generic error, enabling "Continue On Fail" can help capture error details in the workflow for debugging.