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 to manage tokens, specifically allowing you to update an existing token's expiry date. This is useful in scenarios where you want to extend or modify the validity period of a token used for accessing files or other resources within Appwrite.
For example, if you have a file access token that is about to expire but you want to keep it valid longer without creating a new token, you can use this operation to update its expiration date.
Properties
| Name | Meaning |
|---|---|
| Token ID | The unique identifier of the token you want to update. |
| Expire | (Optional) The new expiry date for the token in ISO 8601 format (e.g., 2024-12-31T23:59:59Z). |
Output
The output is a JSON object representing the updated token details as returned by the Appwrite API. It typically includes fields such as the token's ID, creation date, updated expiry date, and any other metadata associated with the token.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Appwrite API.
- Needs credentials including the Appwrite endpoint URL, project ID, and an API key credential with appropriate permissions.
- The node uses the official Appwrite SDK internally to perform API calls.
Troubleshooting
- Invalid Token ID: If the provided Token ID does not exist or is malformed, the node will throw an error indicating the token could not be found. Verify the Token ID is correct.
- Invalid Expiry Date Format: The expiry date must be in ISO 8601 format. Providing an incorrectly formatted date may cause the API to reject the request.
- Insufficient Permissions: Ensure the API key used has permission to update tokens; otherwise, the request will fail with an authorization error.
- Network Issues: Connectivity problems to the Appwrite server will result in errors. Check network settings and endpoint URL.