Actions84
- Avatar Actions
- Document Actions
- Function Actions
- Messaging Actions
- Create APNS Provider
- Create Email
- Create FCM Provider
- Create Mailgun Provider
- Create MSG91 Provider
- Create Provider
- Create Push
- Create Sendgrid Provider
- Create SMS
- Create SMTP Provider
- Create Subscriber
- Create Telesign Provider
- Create Textmagic Provider
- Create Topic
- Create Twilio Provider
- Create Vonage Provider
- Delete Provider
- Delete Subscriber
- Delete Topic
- Get Message
- Get Provider
- Get Subscriber
- Get Topic
- List Message Logs
- List Messages
- List Provider Logs
- List Providers
- List Subscriber Logs
- List Subscribers
- List Targets
- List Topic Logs
- List Topics
- Update APNS Provider
- Update Email
- Update FCM Provider
- Update Mailgun Provider
- Update MSG91 Provider
- Update Provider
- Update Push
- Update Sendgrid Provider
- Update SMS
- Update SMTP Provider
- Update Telesign Provider
- Update Textmagic Provider
- Update Topic
- Update Twilio Provider
- Update Vonage Provider
- Storage Actions
- Token Actions
- Users Actions
Overview
The node integrates with the Appwrite API, enabling users to perform various operations on different resources within Appwrite. Specifically, for the Users resource and the List User Identities operation, this node fetches all identities associated with a specified user ID. This is useful in scenarios where you want to retrieve linked authentication methods or identity providers for a user, such as OAuth accounts or email/password credentials.
Practical examples include:
- Auditing which external identities a user has connected to their account.
- Synchronizing user identity data with other systems.
- Displaying linked login methods in an admin dashboard.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose identities you want to list. This is required. |
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 one identity and typically includes details such as the 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 via an API key credential.
- The node expects valid credentials including the Appwrite endpoint URL, project ID, and an API key.
- 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:
- Authentication errors indicate invalid API keys or insufficient permissions; verify your credentials.
- "Resource not found" errors may occur if the User ID does not exist.
- API rate limits or server errors from Appwrite will be propagated; check Appwrite server status and logs.