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
This node integrates with the Appwrite API to manage tokens, specifically allowing retrieval of a token's details by its unique ID. It is useful in scenarios where you need to fetch metadata or information about a specific token generated within Appwrite, such as for file access or authentication purposes.
Practical examples include:
- Retrieving details of a file access token to verify its expiration or permissions.
- Fetching token information to audit or log token usage in your workflows.
Properties
| Name | Meaning |
|---|---|
| Token ID | The unique identifier of the token to retrieve. This is a required, password-type string input. |
Output
The node outputs a JSON object representing the token's details as returned by the Appwrite API. This typically includes properties such as the token's ID, associated resource (e.g., file or bucket), expiration time, and other metadata relevant to the token.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to an Appwrite server via an API key credential configured in n8n.
- The node depends on the official Appwrite SDK (
node-appwrite) to communicate with the Appwrite API. - Proper credentials including the Appwrite endpoint URL, project ID, and API key must be set up in n8n.
Troubleshooting
Common issues:
- Invalid or expired token ID: The node will fail if the provided token ID does not exist or has been deleted.
- Authentication errors: If the API key or project credentials are incorrect or missing, the node will not connect successfully.
- Network connectivity problems to the Appwrite server can cause request failures.
Error messages:
- Errors from the Appwrite API will be propagated, such as "Token not found" or "Unauthorized".
- To resolve, verify the token ID correctness, ensure valid API credentials, and check network access to the Appwrite instance.